Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-08-31 | use the posix phrasing to improve the description of "shift"; | Jason McIntyre | |
nudge from luka krmpotic | |||
2022-03-31 | man pages: add missing commas between subordinate and main clauses | Christian Weisgerber | |
jmc@ dislikes a comma before "then" in a conditional, so leave those untouched. ok jmc@ | |||
2021-05-04 | shell scripts should use getopts instead of getopt | Christian Weisgerber | |
Add a prominent deprecation notice to getopt.1. Add examples of the getopts idiom to sh.1 and ksh.1. Requested by and ok espie@, ok jmc@ | |||
2019-05-22 | mention that using vi command line editing mode requires enabling it; | Ingo Schwarze | |
omission reported by Rudolf Sykora <rsykora at disroot dot org> on misc@; tweak and OK jmc@ | |||
2018-12-16 | Tweak the syntax displays to show that the list of words | Ingo Schwarze | |
in "for name in [word ...]; do list; done" can be empty. In sh(1), clarify what happens in that case. In ksh(1), clarify how it can happen that the list is never executed. OK jmc@ tb@ | |||
2018-11-30 | in getopts, when a option is followed by a colon the parameter is mandatory | solene | |
ok guenther@ deraadt@ | |||
2018-09-28 | Contrary to the sh manual, it is possible to modify the PWD variable | Todd C. Miller | |
(and this is allowed by POSIX). OK deraadt@ kn@ | |||
2018-03-31 | Fix spacing in brace command list grammar. | anton | |
Initial diff by me, later improved by schwarze@; also ok jmc@ | |||
2018-03-16 | improve markup quality in the cases found by the new "--" style message | Ingo Schwarze | |
2017-12-30 | backslash also escapes newlines when quoted; | Jason McIntyre | |
from kshe | |||
2017-12-15 | oops - previous should have been a list item; | Jason McIntyre | |
2017-12-12 | Document change in the default shell prompts. | Theo Buehler | |
Discussed with and ok jmc | |||
2017-06-01 | The fact is simple: Subshells have the same PPID as the current shell. | Theo Buehler | |
What is not so simple is squinting hard enough to conclude that POSIX actually says that. I'm still not sure how to do that. Problem with the shell manual pointed out by "Choose a display name". ok otto, halex, jmc | |||
2017-05-26 | document behaviour when CDPATH unset; | Jason McIntyre | |
requested by a mail on misc, via otto; ok otto | |||
2017-03-16 | document the "type" built-in, marked as xsi by posix; | Jason McIntyre | |
2017-03-16 | document the ulimit built-in, which is now marked xsi by posix; | Jason McIntyre | |
noted by scott cheloha | |||
2017-03-16 | document the "hash" built-in, moved to (posix) base in issue 7; | Jason McIntyre | |
2016-11-14 | Remove an escaped blank space and insert an No macro to keep \&; at a | Theo Buehler | |
distance from 'Ar command'. This is schwarze's correct version of an initial incorrect diff from me. | |||
2016-11-12 | Fix lexicographic order of shell built-ins: trap comes before true. | Theo Buehler | |
2016-08-12 | rework initial text a little, to read better; | Jason McIntyre | |
2016-07-28 | remove note about command substitution and double quotes: it is probable | Jason McIntyre | |
that i misunderstood something when i wrote it; found by guenther and naddy | |||
2016-07-18 | rework the first sentence of this page; | Jason McIntyre | |
with help from otto | |||
2016-05-04 | Correct the description of the != operator in arithmetic expansion; | Ingo Schwarze | |
from Andras Farkas <deepbluemistake at gmail dot com>. | |||
2016-05-04 | line editing correction; from andras farkas | Jason McIntyre | |
2016-03-21 | More ksh POSIX compliance fixes by Martijn Dekker: | tb | |
This simple patch makes the 'command' builtin POSIX-compliant and consistent with other current shells. It fixes two things: a) 'command -v' does not find shell reserved words (a.k.a. keywords). For instance, 'command -v select' outputs nothing but should output 'select'. b) 'command -pv' always outputs the path of an external command, even if 'command -p' would execute a builtin. For instance, 'command -p kill' executes the 'kill' builtin, as expected, but 'command -pv kill' outputs '/bin/kill'. The '-v' option is supposed to reflect what would actually be executed, so 'command -pv kill' should output 'kill'. The -p option sets the PATH to a default system value before doing the search, but that has no bearing on the fact that builtins take precedence over external commands. The patch fixes both issues for 'command' without affecting the behaviour of the ksh-specific builtin 'whence', which is handled by the same C function. Regression test added to obsd-regress.t. Issues found and fixed by Martijn Dekker, ok millert@ | |||
2015-10-12 | indent the builtin text a little, for naddy; | Jason McIntyre | |
2015-09-14 | Avoid .Ns right after .Pf, it's pointless. | Ingo Schwarze | |
In some cases, do additional cleanup in the immediate vicinity. | |||
2015-05-04 | lightly document the posix option and POSIXLY_CORRECT; will sketch out | Jason McIntyre | |
in more detail once i get my head round them... | |||
2015-04-30 | reapply the rules of english to the option keywords: i was persuaded to undo it | Jason McIntyre | |
because the option names are case sensitive, but it just looks awful. so expect just a little more from the reader... | |||
2015-03-31 | both rpe and zhuk pointed out some problems with my if/elf template. | Jason McIntyre | |
zhuk suggested using "condition" rather than command, and this commit reworks the loop/conditional section to do that; ok zhuk rpe | |||
2015-03-30 | on zhuk's advice, don;t talk about null: posix uses null and empty | Jason McIntyre | |
interchangeably, but we've stuck with empty; while here, sneak in an otherwsie -> otherwise | |||
2015-03-27 | clarity fix from zhuk; | Jason McIntyre | |
2015-03-26 | a little wording tweak; | Jason McIntyre | |
2015-03-26 | various fixes from rpe; | Jason McIntyre | |
2015-03-26 | from zhuk: in the for loop, show "in word ..." as optional; | Jason McIntyre | |
2015-03-26 | from zhuk: sequential and asynchronous lists may take only one item; | Jason McIntyre | |
2015-03-26 | rework the section on when different types of command are processed; | Jason McIntyre | |
zhuk pointed out the flaws in my original text, and has found many more since; | |||
2015-03-19 | Fix IFS description. May be polished further when all consequences of | Vadim Zhukov | |
following "null is the same as empty" from POSIX are investigated. okay jmc@ | |||
2015-03-19 | Make it clear that it's the line who shouldn't be empty, and not the | Vadim Zhukov | |
command history. This version comes from jmc@ together with his okay. | |||
2015-03-18 | remove ambiguity from the COMMANDS section, after discussion with zhuk; | Jason McIntyre | |
2015-03-18 | from zhuk: a little more info on <> | Jason McIntyre | |
2015-03-18 | improve the description of here documents; prompted by zhuk | Jason McIntyre | |
2015-03-18 | rework the redirection text after some feedback from zhuk; | Jason McIntyre | |
2015-03-17 | revert a previous word change - the original seems more accurate; | Jason McIntyre | |
2015-03-17 | Escape certain characters for slightly more correct (and prettier) output. | Anthony J. Bentley | |
ok jmc@ | |||
2015-03-17 | from zhuk: provide some Sx | Jason McIntyre | |
2015-03-17 | from zhuk: shell does not wait for command to complete if job run in background | Jason McIntyre | |
2015-03-16 | from zhuk: be clear that "#" is a variable | Jason McIntyre | |
2015-03-15 | from zhuk: two grammar fixes; | Jason McIntyre | |
2015-03-15 | from zhuk: clarify "set --"; | Jason McIntyre | |