diff options
Diffstat (limited to 'POSIX')
| -rw-r--r-- | POSIX | 139 |
1 files changed, 72 insertions, 67 deletions
@@ -22,9 +22,7 @@ The following list is what's changed when 'POSIX mode' is in effect: is stopped is 'Stopped(SIGNAME)', where SIGNAME is, for example, 'SIGTSTP'. - 4. The 'bg' builtin uses the required format to describe each job - placed in the background, which does not include an indication of - whether the job is the current or previous job. + 4. Alias expansion is always enabled, even in non-interactive shells. 5. Reserved words appearing in a context where reserved words are recognized do not undergo alias expansion. @@ -40,166 +38,173 @@ The following list is what's changed when 'POSIX mode' is in effect: 8. Tilde expansion is only performed on assignments preceding a command name, rather than on all assignment statements on the line. - 9. The 'command' builtin does not prevent builtins that take - assignment statements as arguments from expanding them as - assignment statements; when not in POSIX mode, assignment builtins - lose their assignment statement expansion properties when preceded - by 'command'. - - 10. The default history file is '~/.sh_history' (this is the default + 9. The default history file is '~/.sh_history' (this is the default value of '$HISTFILE'). - 11. The output of 'kill -l' prints all the signal names on a single - line, separated by spaces, without the 'SIG' prefix. - - 12. The 'kill' builtin does not accept signal names with a 'SIG' - prefix. - - 13. Non-interactive shells exit if FILENAME in '.' FILENAME is not - found. - - 14. Non-interactive shells exit if a syntax error in an arithmetic - expansion results in an invalid expression. - - 15. Non-interactive shells exit on word expansion errors. - - 16. Non-interactive shells exit if there is a syntax error in a script - read with the '.' or 'source' builtins, or in a string processed by - the 'eval' builtin. - - 17. Redirection operators do not perform filename expansion on the + 10. Redirection operators do not perform filename expansion on the word in the redirection unless the shell is interactive. - 18. Redirection operators do not perform word splitting on the word in + 11. Redirection operators do not perform word splitting on the word in the redirection. - 19. Function names must be valid shell 'name's. That is, they may not + 12. Function names must be valid shell 'name's. That is, they may not contain characters other than letters, digits, and underscores, and may not start with a digit. Declaring a function with an invalid name causes a fatal syntax error in non-interactive shells. - 20. Function names may not be the same as one of the POSIX special + 13. Function names may not be the same as one of the POSIX special builtins. - 21. POSIX special builtins are found before shell functions during + 14. POSIX special builtins are found before shell functions during command lookup. - 22. Literal tildes that appear as the first character in elements of + 15. Literal tildes that appear as the first character in elements of the 'PATH' variable are not expanded as described above under *note Tilde Expansion::. - 23. The 'time' reserved word may be used by itself as a command. When + 16. The 'time' reserved word may be used by itself as a command. When used in this way, it displays timing statistics for the shell and its completed children. The 'TIMEFORMAT' variable controls the format of the timing information. - 24. When parsing and expanding a ${...} expansion that appears within + 17. When parsing and expanding a ${...} expansion that appears within double quotes, single quotes are no longer special and cannot be used to quote a closing brace or other special character, unless the operator is one of those defined to perform pattern removal. In this case, they do not have to appear as matched pairs. - 25. The parser does not recognize 'time' as a reserved word if the + 18. The parser does not recognize 'time' as a reserved word if the next token begins with a '-'. - 26. If a POSIX special builtin returns an error status, a + 19. The '!' character does not introduce history expansion within a + double-quoted string, even if the 'histexpand' option is enabled. + + 20. If a POSIX special builtin returns an error status, a non-interactive shell exits. The fatal errors are those listed in the POSIX standard, and include things like passing incorrect options, redirection errors, variable assignment errors for assignments preceding the command name, and so on. - 27. A non-interactive shell exits with an error status if a variable + 21. A non-interactive shell exits with an error status if a variable assignment error occurs when no command name follows the assignment statements. A variable assignment error occurs, for example, when trying to assign a value to a readonly variable. - 28. A non-interactive shell exits with an error status if a variable + 22. A non-interactive shell exits with an error status if a variable assignment error occurs in an assignment statement preceding a special builtin, but not with any other simple command. - 29. A non-interactive shell exits with an error status if the + 23. A non-interactive shell exits with an error status if the iteration variable in a 'for' statement or the selection variable in a 'select' statement is a readonly variable. - 30. Process substitution is not available. + 24. Non-interactive shells exit if FILENAME in '.' FILENAME is not + found. - 31. While variable indirection is available, it may not be applied to + 25. Non-interactive shells exit if a syntax error in an arithmetic + expansion results in an invalid expression. + + 26. Non-interactive shells exit on word expansion errors. + + 27. Non-interactive shells exit if there is a syntax error in a script + read with the '.' or 'source' builtins, or in a string processed by + the 'eval' builtin. + + 28. Process substitution is not available. + + 29. While variable indirection is available, it may not be applied to the '#' and '?' special parameters. - 32. Assignment statements preceding POSIX special builtins persist in + 30. Assignment statements preceding POSIX special builtins persist in the shell environment after the builtin completes. - 33. Assignment statements preceding shell function calls persist in + 31. Assignment statements preceding shell function calls persist in the shell environment after the function returns, as if a POSIX special builtin command had been executed. - 34. The 'export' and 'readonly' builtin commands display their output + 32. The 'command' builtin does not prevent builtins that take + assignment statements as arguments from expanding them as + assignment statements; when not in POSIX mode, assignment builtins + lose their assignment statement expansion properties when preceded + by 'command'. + + 33. The 'bg' builtin uses the required format to describe each job + placed in the background, which does not include an indication of + whether the job is the current or previous job. + + 34. The output of 'kill -l' prints all the signal names on a single + line, separated by spaces, without the 'SIG' prefix. + + 35. The 'kill' builtin does not accept signal names with a 'SIG' + prefix. + + 36. The 'export' and 'readonly' builtin commands display their output in the format required by POSIX. - 35. The 'trap' builtin displays signal names without the leading + 37. The 'trap' builtin displays signal names without the leading 'SIG'. - 36. The 'trap' builtin doesn't check the first argument for a possible + 38. The 'trap' builtin doesn't check the first argument for a possible signal specification and revert the signal handling to the original disposition if it is, unless that argument consists solely of digits and is a valid signal number. If users want to reset the handler for a given signal to the original disposition, they should use '-' as the first argument. - 37. The '.' and 'source' builtins do not search the current directory + 39. The '.' and 'source' builtins do not search the current directory for the filename argument if it is not found by searching 'PATH'. - 38. Subshells spawned to execute command substitutions inherit the - value of the '-e' option from the parent shell. When not in POSIX - mode, Bash clears the '-e' option in such subshells. - - 39. Alias expansion is always enabled, even in non-interactive shells. + 40. Enabling POSIX mode has the effect of setting the + 'inherit_errexit' option, so subshells spawned to execute command + substitutions inherit the value of the '-e' option from the parent + shell. When the 'inherit_errexit' option is not enabled, Bash + clears the '-e' option in such subshells. - 40. When the 'alias' builtin displays alias definitions, it does not + 41. When the 'alias' builtin displays alias definitions, it does not display them with a leading 'alias ' unless the '-p' option is supplied. - 41. When the 'set' builtin is invoked without options, it does not + 42. When the 'set' builtin is invoked without options, it does not display shell function names and definitions. - 42. When the 'set' builtin is invoked without options, it displays + 43. When the 'set' builtin is invoked without options, it displays variable values without quotes, unless they contain shell metacharacters, even if the result contains nonprinting characters. - 43. When the 'cd' builtin is invoked in LOGICAL mode, and the pathname + 44. When the 'cd' builtin is invoked in LOGICAL mode, and the pathname constructed from '$PWD' and the directory name supplied as an argument does not refer to an existing directory, 'cd' will fail instead of falling back to PHYSICAL mode. - 44. The 'pwd' builtin verifies that the value it prints is the same as + 45. The 'pwd' builtin verifies that the value it prints is the same as the current directory, even if it is not asked to check the file system with the '-P' option. - 45. When listing the history, the 'fc' builtin does not include an + 46. When listing the history, the 'fc' builtin does not include an indication of whether or not a history entry has been modified. - 46. The default editor used by 'fc' is 'ed'. + 47. The default editor used by 'fc' is 'ed'. - 47. The 'type' and 'command' builtins will not report a non-executable + 48. The 'type' and 'command' builtins will not report a non-executable file as having been found, though the shell will attempt to execute such a file if it is the only so-named file found in '$PATH'. - 48. The 'vi' editing mode will invoke the 'vi' editor directly when + 49. The 'vi' editing mode will invoke the 'vi' editor directly when the 'v' command is run, instead of checking '$VISUAL' and '$EDITOR'. - 49. When the 'xpg_echo' option is enabled, Bash does not attempt to + 50. When the 'xpg_echo' option is enabled, Bash does not attempt to interpret any arguments to 'echo' as options. Each argument is displayed, after escape characters are converted. - 50. The 'ulimit' builtin uses a block size of 512 bytes for the '-c' + 51. The 'ulimit' builtin uses a block size of 512 bytes for the '-c' and '-f' options. - 51. The arrival of 'SIGCHLD' when a trap is set on 'SIGCHLD' does not + 52. The arrival of 'SIGCHLD' when a trap is set on 'SIGCHLD' does not interrupt the 'wait' builtin and cause it to return immediately. The trap command is run once for each child that exits. - 52. The 'read' builtin may be interrupted by a signal for which a trap + 53. The 'read' builtin may be interrupted by a signal for which a trap has been set. If Bash receives a trapped signal while executing 'read', the trap handler executes and 'read' returns an exit status greater than 128. |