pmodules/bash
0
0
Fork 0
mirror of https://https.git.savannah.gnu.org/git/bash.git synced 2026-08-04 01:08:19 +02:00
Code Issues Packages Projects Releases Wiki Activity

wait -n' notifies on a job it returns; in posix mode, wait' defers notification on a reaped pid unless the shell is interactive, as posix now specifies

Browse Source
This commit is contained in:
Chet Ramey
2024-09-11 15:54:24 -04:00
parent 5576c26da8
commit bc5ddc8698
17 changed files with 988 additions and 783 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/bash.info
+325 -274
View File
@@ -1,9 +1,9 @@
This is bash.info, produced by makeinfo version 7.1 from bashref.texi.
This text is a brief description of the features that are present in the
Bash shell (version 5.3, 16 August 2024).
Bash shell (version 5.3, 5 September 2024).
This is Edition 5.3, last updated 16 August 2024, of ‘The GNU Bash
This is Edition 5.3, last updated 5 September 2024, of ‘The GNU Bash
Reference Manual’, for ‘Bash’, Version 5.3.
Copyright © 1988-2023 Free Software Foundation, Inc.
@@ -26,10 +26,10 @@ Bash Features
*************
This text is a brief description of the features that are present in the
Bash shell (version 5.3, 16 August 2024). The Bash home page is
Bash shell (version 5.3, 5 September 2024). The Bash home page is
<http://www.gnu.org/software/bash/>.
This is Edition 5.3, last updated 16 August 2024, of ‘The GNU Bash
This is Edition 5.3, last updated 5 September 2024, of ‘The GNU Bash
Reference Manual’, for ‘Bash’, Version 5.3.
Bash contains features that appear in other popular shells, and some
@@ -903,11 +903,11 @@ File: bash.info, Node: Conditional Constructs, Next: Command Grouping, Prev:
Each clause must be terminated with ‘;;’, ‘;&’, or ‘;;&’. The WORD
undergoes tilde expansion, parameter expansion, command
substitution, arithmetic expansion, and quote removal (*note Shell
Parameter Expansion::) before matching is attempted. Each PATTERN
undergoes tilde expansion, parameter expansion, command
substitution, arithmetic expansion, process substitution, and quote
removal.
substitution, process substitution, arithmetic expansion, and quote
removal (*note Shell Parameter Expansion::) before the shell
attempts to match the pattern. Each PATTERN undergoes tilde
expansion, parameter expansion, command substitution, arithmetic
expansion, process substitution, and quote removal.
There may be an arbitrary number of ‘case’ clauses, each terminated
by a ‘;;’, ‘;&’, or ‘;;&’. The first pattern that matches
@@ -1555,10 +1555,10 @@ only be referenced; assignment to them is not allowed.
‘*’
($*) Expands to the positional parameters, starting from one. When
the expansion is not within double quotes, each positional
parameter expands to a separate word. In contexts where it is
performed, those words are subject to further word splitting and
filename expansion. When the expansion occurs within double
quotes, it expands to a single word with the value of each
parameter expands to a separate word. In contexts where these
expansions are performed, those words are subject to further word
splitting and filename expansion. When the expansion occurs within
double quotes, it expands to a single word with the value of each
parameter separated by the first character of the ‘IFS’ special
variable. That is, ‘"$*"’ is equivalent to ‘"$1C$2C..."’, where C
is the first character of the value of the ‘IFS’ variable. If
@@ -1587,7 +1587,7 @@ only be referenced; assignment to them is not allowed.
‘?’
($?) Expands to the exit status of the most recently executed
foreground command.
command.
‘-’
($-, a hyphen.) Expands to the current option flags as specified
@@ -7356,102 +7356,113 @@ startup files.
is stopped is 'Stopped(SIGNAME)', where SIGNAME is, for example,
‘SIGTSTP’.
6. Alias expansion is always enabled, even in non-interactive shells.
6. If the shell is interactive, Bash does not perform job
notifications between executing commands in lists separated by ‘;’
or newline. Non-interactive shells print status messages after a
foreground job in a list completes.
7. Reserved words appearing in a context where reserved words are
7. If the shell is interactive, Bash waits until the next prompt
before printing the status of a background job that changes status
or a foreground job that terminates due to a signal.
Non-interactive shells print status messages after a foreground job
completes.
8. Alias expansion is always enabled, even in non-interactive shells.
9. Reserved words appearing in a context where reserved words are
recognized do not undergo alias expansion.
8. Alias expansion is performed when initially parsing a command
10. Alias expansion is performed when initially parsing a command
substitution. The default mode generally defers it, when enabled,
until the command substitution is executed. This means that
command substitution will not expand aliases that are defined after
the command substitution is initially parsed (e.g., as part of a
function definition).
9. The POSIX ‘PS1’ and ‘PS2’ expansions of ‘!’ to the history number
11. The POSIX ‘PS1’ and ‘PS2’ expansions of ‘!’ to the history number
and ‘!!’ to ‘!’ are enabled, and parameter expansion is performed
on the values of ‘PS1’ and ‘PS2’ regardless of the setting of the
‘promptvars’ option.
10. The POSIX startup files are executed (‘$ENV’) rather than the
12. The POSIX startup files are executed (‘$ENV’) rather than the
normal Bash files.
11. Tilde expansion is only performed on assignments preceding a
13. Tilde expansion is only performed on assignments preceding a
command name, rather than on all assignment statements on the line.
12. The default history file is ‘~/.sh_history’ (this is the default
14. The default history file is ‘~/.sh_history’ (this is the default
value the shell assigns to ‘$HISTFILE’).
13. Redirection operators do not perform filename expansion on the
15. Redirection operators do not perform filename expansion on the
word in the redirection unless the shell is interactive.
14. Redirection operators do not perform word splitting on the word in
16. Redirection operators do not perform word splitting on the word in
the redirection.
15. Function names must be valid shell ‘name’s. That is, they may not
17. 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.
16. Function names may not be the same as one of the POSIX special
18. Function names may not be the same as one of the POSIX special
builtins.
17. Even if a shell function whose name contains a slash was defined
19. Even if a shell function whose name contains a slash was defined
before entering POSIX mode, the shell will not execute a function
whose name contains one or more slashes.
18. POSIX special builtins are found before shell functions during
20. POSIX special builtins are found before shell functions during
command lookup, including output printed by the ‘type’ and
‘command’ builtins.
19. When printing shell function definitions (e.g., by ‘type’), Bash
21. When printing shell function definitions (e.g., by ‘type’), Bash
does not print the ‘function’ keyword.
20. Literal tildes that appear as the first character in elements of
22. Literal tildes that appear as the first character in elements of
the ‘PATH’ variable are not expanded as described above under *note
Tilde Expansion::.
21. The ‘time’ reserved word may be used by itself as a command. When
23. 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.
22. When parsing and expanding a ${...} expansion that appears within
24. 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.
23. The parser does not recognize ‘time’ as a reserved word if the
25. The parser does not recognize ‘time’ as a reserved word if the
next token begins with a ‘-’.
24. The ‘!’ character does not introduce history expansion within a
26. The ‘!’ character does not introduce history expansion within a
double-quoted string, even if the ‘histexpand’ option is enabled.
25. If a POSIX special builtin returns an error status, a
27. 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.
26. The ‘unset’ builtin with the ‘-v’ option specified returns a fatal
28. The ‘unset’ builtin with the ‘-v’ option specified returns a fatal
error if it attempts to unset a ‘readonly’ or ‘non-unsettable’
variable, or encounters a variable name argument that is an invalid
identifier, which causes a non-interactive shell to exit.
27. When asked to unset a variable that appears in an assignment
29. When asked to unset a variable that appears in an assignment
statement preceding the command, the ‘unset’ builtin attempts to
unset a variable of the same name in the current or previous scope
as well. This implements the required "if an assigned variable is
further modified by the utility, the modifications made by the
utility shall persist" behavior.
28. A non-interactive shell exits with an error status if a variable
30. 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.
29. A non-interactive shell exits with an error status if a variable
31. 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. For any
other simple command, the shell aborts execution of that command,
@@ -7459,166 +7470,166 @@ startup files.
perform any further processing of the command in which the error
occurred").
30. A non-interactive shell exits with an error status if the
32. 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 or has an invalid
name.
31. Non-interactive shells exit if FILENAME in ‘.’ FILENAME is not
33. Non-interactive shells exit if FILENAME in ‘.’ FILENAME is not
found.
32. Non-interactive shells exit if a syntax error in an arithmetic
34. Non-interactive shells exit if a syntax error in an arithmetic
expansion results in an invalid expression.
33. Non-interactive shells exit if a parameter expansion error occurs.
35. Non-interactive shells exit if a parameter expansion error occurs.
34. Non-interactive shells exit if there is a syntax error in a script
36. 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.
35. While variable indirection is available, it may not be applied to
37. While variable indirection is available, it may not be applied to
the ‘#’ and ‘?’ special parameters.
36. Expanding the ‘*’ special parameter in a pattern context where the
38. Expanding the ‘*’ special parameter in a pattern context where the
expansion is double-quoted does not treat the ‘$*’ as if it were
double-quoted.
37. Assignment statements preceding POSIX special builtins persist in
39. Assignment statements preceding POSIX special builtins persist in
the shell environment after the builtin completes.
38. The ‘command’ builtin does not prevent builtins that take
40. 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’.
39. The ‘bg’ builtin uses the required format to describe each job
41. 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.
40. The output of ‘kill -l’ prints all the signal names on a single
42. The output of ‘kill -l’ prints all the signal names on a single
line, separated by spaces, without the ‘SIG’ prefix.
41. The ‘kill’ builtin does not accept signal names with a ‘SIG’
43. The ‘kill’ builtin does not accept signal names with a ‘SIG’
prefix.
42. The ‘export’ and ‘readonly’ builtin commands display their output
44. The ‘export’ and ‘readonly’ builtin commands display their output
in the format required by POSIX.
43. If the ‘export’ and ‘readonly’ builtin commands get an argument
45. If the ‘export’ and ‘readonly’ builtin commands get an argument
that is not a valid identifier, and they are not operating on shell
functions, they return an error. This will cause a non-interactive
shell to exit because these are special builtins.
44. The ‘trap’ builtin displays signal names without the leading
46. The ‘trap’ builtin displays signal names without the leading
‘SIG’.
45. The ‘trap’ builtin doesn't check the first argument for a possible
47. 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.
46. ‘trap -p’ without arguments displays signals whose dispositions
48. ‘trap -p’ without arguments displays signals whose dispositions
are set to SIG_DFL and those that were ignored when the shell
started, not just trapped signals.
47. The ‘.’ and ‘source’ builtins do not search the current directory
49. The ‘.’ and ‘source’ builtins do not search the current directory
for the filename argument if it is not found by searching ‘PATH’.
48. Enabling POSIX mode has the effect of setting the
50. 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.
49. Enabling POSIX mode has the effect of setting the ‘shift_verbose’
51. Enabling POSIX mode has the effect of setting the ‘shift_verbose’
option, so numeric arguments to ‘shift’ that exceed the number of
positional parameters will result in an error message.
50. When the ‘alias’ builtin displays alias definitions, it does not
52. When the ‘alias’ builtin displays alias definitions, it does not
display them with a leading ‘alias ’ unless the ‘-p’ option is
supplied.
51. When the ‘set’ builtin is invoked without options, it does not
53. When the ‘set’ builtin is invoked without options, it does not
display shell function names and definitions.
52. When the ‘set’ builtin is invoked without options, it displays
54. 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.
53. When the ‘cd’ builtin is invoked in logical mode, and the pathname
55. 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.
54. When the ‘cd’ builtin cannot change a directory because the length
56. When the ‘cd’ builtin cannot change a directory because the length
of the pathname constructed from ‘$PWD’ and the directory name
supplied as an argument exceeds ‘PATH_MAX’ when canonicalized, ‘cd’
will attempt to use the supplied directory name.
55. The ‘pwd’ builtin verifies that the value it prints is the same as
57. 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.
56. When listing the history, the ‘fc’ builtin does not include an
58. When listing the history, the ‘fc’ builtin does not include an
indication of whether or not a history entry has been modified.
57. The default editor used by ‘fc’ is ‘ed’.
59. The default editor used by ‘fc’ is ‘ed’.
58. ‘fc’ treats extra arguments as an error instead of ignoring them.
60. ‘fc’ treats extra arguments as an error instead of ignoring them.
59. If there are too many arguments supplied to ‘fc -s’, ‘fc’ prints
61. If there are too many arguments supplied to ‘fc -s’, ‘fc’ prints
an error message and returns failure.
60. The ‘type’ and ‘command’ builtins will not report a non-executable
62. 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’.
61. The ‘vi’ editing mode will invoke the ‘vi’ editor directly when
63. The ‘vi’ editing mode will invoke the ‘vi’ editor directly when
the ‘v’ command is run, instead of checking ‘$VISUAL’ and
‘$EDITOR’.
62. When the ‘xpg_echo’ option is enabled, Bash does not attempt to
64. 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.
63. The ‘ulimit’ builtin uses a block size of 512 bytes for the ‘-c’
65. The ‘ulimit’ builtin uses a block size of 512 bytes for the ‘-c’
and ‘-f’ options.
64. The arrival of ‘SIGCHLD’ when a trap is set on ‘SIGCHLD’ does not
66. 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.
65. The ‘read’ builtin may be interrupted by a signal for which a trap
67. 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.
66. The ‘printf’ builtin uses ‘double’ (via ‘strtod’) to convert
68. The ‘printf’ builtin uses ‘double’ (via ‘strtod’) to convert
arguments corresponding to floating point conversion specifiers,
instead of ‘long double’ if it's available. The ‘L’ length
modifier forces ‘printf’ to use ‘long double’ if it's available.
67. Bash removes an exited background process's status from the list
69. Bash removes an exited background process's status from the list
of such statuses after the ‘wait’ builtin is used to obtain it.
68. A double quote character (‘"’) is treated specially when it
70. A double quote character (‘"’) is treated specially when it
appears in a backquoted command substitution in the body of a
here-document that undergoes expansion. That means, for example,
that a backslash preceding a double quote character will escape it
and the backslash will be removed.
69. The ‘test’ builtin compares strings using the current locale when
71. The ‘test’ builtin compares strings using the current locale when
processing the ‘<’ and ‘>’ binary operators.
70. The ‘test’ builtin's ‘-t’ unary primary requires an argument.
72. The ‘test’ builtin's ‘-t’ unary primary requires an argument.
Historical versions of ‘test’ made the argument optional in certain
cases, and Bash attempts to accommodate those for backwards
compatibility.
71. Command substitutions don't set the ‘?’ special parameter. The
73. Command substitutions don't set the ‘?’ special parameter. The
exit status of a simple command without a command word is still the
exit status of the last command substitution that occurred while
evaluating the variable assignments and redirections in that
@@ -7804,6 +7815,9 @@ required for bash-5.1 and later versions.
as bindable command names, and displays any key sequences
bound to those commands, instead of treating the arguments as
key sequences to bind.
• Interactive shells will notify the user of completed jobs
while sourcing a script. Newer versions defer notification
until script execution completes.

File: bash.info, Node: Job Control, Next: Command Line Editing, Prev: Bash Features, Up: Top
@@ -7896,10 +7910,12 @@ equivalent to ‘bg %1’
The shell learns immediately whenever a job changes state. Normally,
Bash waits until it is about to print a prompt before reporting changes
in a job's status so as to not interrupt any other output. If the ‘-b’
option to the ‘set’ builtin is enabled, Bash reports such changes
immediately (*note The Set Builtin::). Any trap on ‘SIGCHLD’ is
executed for each child process that exits.
in a job's status so as to not interrupt any other output, though it
will notify of changes in a job's status after a command in a list
completes, before executing the next command. If the ‘-b’ option to the
‘set’ builtin is enabled, Bash reports such changes immediately (*note
The Set Builtin::). Any trap on ‘SIGCHLD’ is executed for each child
process that exits.
If an attempt to exit Bash is made while jobs are stopped, (or
running, if the ‘checkjobs’ option is enabled - see *note The Shopt
@@ -8120,20 +8136,29 @@ produced when the <k> key is pressed while the Control key is depressed.
The text ‘M-k’ is read as 'Meta-K' and describes the character
produced when the Meta key (if you have one) is depressed, and the <k>
key is pressed. The Meta key is labeled <ALT> on many keyboards. On
keyboards with two keys labeled <ALT> (usually to either side of the
space bar), the <ALT> on the left side is generally set to work as a
Meta key. The <ALT> key on the right may also be configured to work as
a Meta key or may be configured as some other modifier, such as a
Compose key for typing accented characters.
key is pressed (a “meta character”). The Meta key is labeled <ALT> on
many keyboards. On keyboards with two keys labeled <ALT> (usually to
either side of the space bar), the <ALT> on the left side is generally
set to work as a Meta key. The <ALT> key on the right may also be
configured to work as a Meta key or may be configured as some other
modifier, such as a Compose key for typing accented characters.
On some keyboards, the Meta key modifier produces meta characters
with the eighth bit (0200) set (you can use the ‘enable-meta-key’
variable to control whether or not it does this, if the keyboard allows
it). On many others, the terminal or terminal emulator converts the
metafied key to a key sequence beginning with <ESC> as described in the
next paragraph.
If you do not have a Meta or <ALT> key, or another key working as a
Meta key, the identical keystroke can be generated by typing <ESC>
_first_, and then typing <k>. Either process is known as “metafying”
the <k> key.
Meta key, you can generally achieve the latter effect by typing <ESC>
_first_, and then typing <k>. The <ESC> character is known as the “meta
prefix”).
Either process is known as “metafying” the <k> key.
The text ‘M-C-k’ is read as 'Meta-Control-k' and describes the
character produced by “metafying” ‘C-k’.
character produced by metafying ‘C-k’.
In addition, several keys have their own names. Specifically, <DEL>,
<ESC>, <LFD>, <SPC>, <RET>, and <TAB> all stand for themselves when seen
@@ -8522,14 +8547,16 @@ Variable Settings
limit is ‘100’.
‘convert-meta’
If set to ‘on’, Readline will convert characters with the
eighth bit set to an ASCII key sequence by stripping the
If set to ‘on’, Readline will convert characters it reads with
the eighth bit set to an ASCII key sequence by stripping the
eighth bit and prefixing an <ESC> character, converting them
to a meta-prefixed key sequence. The default value is ‘on’,
but will be set to ‘off’ if the locale is one that contains
eight-bit characters. This variable is dependent on the
‘LC_CTYPE’ locale category, and may change if the locale is
changed.
but Readline will set it to ‘off’ if the locale contains
characters whose encodings may include bytes with the eighth
bit set. This variable is dependent on the ‘LC_CTYPE’ locale
category, and may change if the locale is changed. This
variable also affects key bindings; see the description of
‘force-meta-prefix’ below.
‘disable-completion’
If set to ‘On’, Readline will inhibit word completion.
@@ -8587,13 +8614,30 @@ Variable Settings
‘enable-meta-key’
When set to ‘on’, Readline will try to enable any meta
modifier key the terminal claims to support when it is called.
On many terminals, the meta key is used to send eight-bit
characters. The default is ‘on’.
On many terminals, the Meta key is used to send eight-bit
characters; this variable checks for the terminal capability
that indicates the terminal can enable and disable a mode that
sets the eighth bit of a character (0200) if the Meta key is
held down when the character is typed (a meta character). The
default is ‘on’.
‘expand-tilde’
If set to ‘on’, tilde expansion is performed when Readline
attempts word completion. The default is ‘off’.
‘force-meta-prefix’
If set to ‘on’, Readline modifies its behavior when binding
key sequences containing ‘\M-’ or ‘Meta-’ (see ‘Key Bindings’
in *note Readline Init File Syntax::) by converting a key
sequence of the form ‘\M-’C or ‘Meta-’C to the two-character
sequence ‘ESC’C (adding the meta prefix). If
‘force-meta-prefix’ is set to ‘off’ (the default), Readline
uses the value of the ‘convert-meta’ variable to determine
whether to perform this conversion: if ‘convert-meta’ is ‘on’,
Readline performs the conversion described above; if it is
‘off’, Readline converts C to a meta character by setting the
eighth bit (0200). The default is ‘off’.
‘history-preserve-point’
If set to ‘on’, the history code attempts to place the point
(the current cursor position) at the same location on each
@@ -8623,10 +8667,11 @@ Variable Settings
not clear the eighth bit in the characters it reads),
regardless of what the terminal claims it can support. The
default value is ‘off’, but Readline will set it to ‘on’ if
the locale contains eight-bit characters. The name
‘meta-flag’ is a synonym for this variable. This variable is
dependent on the ‘LC_CTYPE’ locale category, and may change if
the locale is changed.
the locale contains characters whose encodings may include
bytes with the eighth bit set. The name ‘meta-flag’ is a
synonym for this variable. This variable is dependent on the
‘LC_CTYPE’ locale category, and may change if the locale is
changed.
‘isearch-terminators’
The string of characters that should terminate an incremental
@@ -8691,9 +8736,10 @@ Variable Settings
If set to ‘on’, Readline will display characters with the
eighth bit set directly rather than as a meta-prefixed escape
sequence. The default is ‘off’, but Readline will set it to
‘on’ if the locale contains eight-bit characters. This
variable is dependent on the ‘LC_CTYPE’ locale category, and
may change if the locale is changed.
‘on’ if the locale contains characters whose encodings may
include bytes with the eighth bit set. This variable is
dependent on the ‘LC_CTYPE’ locale category, and may change if
the locale is changed.
‘page-completions’
If set to ‘on’, Readline uses an internal ‘more’-like pager to
@@ -8839,7 +8885,10 @@ Key Bindings
‘\C-’
control prefix
‘\M-’
meta prefix
adding the meta prefix or converting the following character
to a meta character, as described above under
‘force-meta-prefix’ (see ‘Variable Settings’ in *note Readline
Init File Syntax::).
‘\e’
an escape character
‘\\’
@@ -12474,29 +12523,31 @@ D.3 Parameter and Variable Index
* COPROC: Bash Variables. (line 278)
* DIRSTACK: Bash Variables. (line 282)
* disable-completion: Readline Init File Syntax.
(line 151)
(line 153)
* echo-control-characters: Readline Init File Syntax.
(line 156)
(line 158)
* editing-mode: Readline Init File Syntax.
(line 161)
(line 163)
* EMACS: Bash Variables. (line 292)
* emacs-mode-string: Readline Init File Syntax.
(line 167)
(line 169)
* enable-active-region: Readline Init File Syntax.
(line 177)
(line 179)
* enable-bracketed-paste: Readline Init File Syntax.
(line 190)
(line 192)
* enable-keypad: Readline Init File Syntax.
(line 199)
(line 201)
* ENV: Bash Variables. (line 297)
* EPOCHREALTIME: Bash Variables. (line 302)
* EPOCHSECONDS: Bash Variables. (line 310)
* EUID: Bash Variables. (line 317)
* EXECIGNORE: Bash Variables. (line 321)
* expand-tilde: Readline Init File Syntax.
(line 210)
(line 216)
* FCEDIT: Bash Variables. (line 334)
* FIGNORE: Bash Variables. (line 338)
* force-meta-prefix: Readline Init File Syntax.
(line 220)
* FUNCNAME: Bash Variables. (line 344)
* FUNCNEST: Bash Variables. (line 361)
* GLOBIGNORE: Bash Variables. (line 366)
@@ -12509,15 +12560,15 @@ D.3 Parameter and Variable Index
* HISTFILESIZE: Bash Variables. (line 456)
* HISTIGNORE: Bash Variables. (line 467)
* history-preserve-point: Readline Init File Syntax.
(line 214)
(line 233)
* history-size: Readline Init File Syntax.
(line 220)
(line 239)
* HISTSIZE: Bash Variables. (line 489)
* HISTTIMEFORMAT: Bash Variables. (line 496)
* HOME: Bourne Shell Variables.
(line 13)
* horizontal-scroll-mode: Readline Init File Syntax.
(line 229)
(line 248)
* HOSTFILE: Bash Variables. (line 505)
* HOSTNAME: Bash Variables. (line 516)
* HOSTTYPE: Bash Variables. (line 519)
@@ -12525,13 +12576,13 @@ D.3 Parameter and Variable Index
(line 18)
* IGNOREEOF: Bash Variables. (line 522)
* input-meta: Readline Init File Syntax.
(line 238)
(line 257)
* INPUTRC: Bash Variables. (line 532)
* INSIDE_EMACS: Bash Variables. (line 536)
* isearch-terminators: Readline Init File Syntax.
(line 248)
(line 268)
* keymap: Readline Init File Syntax.
(line 255)
(line 275)
* LANG: Creating Internationalized Scripts.
(line 51)
* LANG <1>: Bash Variables. (line 542)
@@ -12553,15 +12604,15 @@ D.3 Parameter and Variable Index
(line 27)
* MAPFILE: Bash Variables. (line 597)
* mark-modified-lines: Readline Init File Syntax.
(line 285)
(line 305)
* mark-symlinked-directories: Readline Init File Syntax.
(line 290)
(line 310)
* match-hidden-files: Readline Init File Syntax.
(line 295)
(line 315)
* menu-complete-display-prefix: Readline Init File Syntax.
(line 302)
(line 322)
* meta-flag: Readline Init File Syntax.
(line 238)
(line 257)
* OLDPWD: Bash Variables. (line 601)
* OPTARG: Bourne Shell Variables.
(line 34)
@@ -12570,9 +12621,9 @@ D.3 Parameter and Variable Index
(line 38)
* OSTYPE: Bash Variables. (line 608)
* output-meta: Readline Init File Syntax.
(line 307)
(line 327)
* page-completions: Readline Init File Syntax.
(line 315)
(line 336)
* PATH: Bourne Shell Variables.
(line 42)
* PIPESTATUS: Bash Variables. (line 611)
@@ -12595,21 +12646,21 @@ D.3 Parameter and Variable Index
* READLINE_POINT: Bash Variables. (line 684)
* REPLY: Bash Variables. (line 688)
* revert-all-at-newline: Readline Init File Syntax.
(line 325)
(line 346)
* search-ignore-case: Readline Init File Syntax.
(line 332)
(line 353)
* SECONDS: Bash Variables. (line 691)
* SHELL: Bash Variables. (line 701)
* SHELLOPTS: Bash Variables. (line 706)
* SHLVL: Bash Variables. (line 715)
* show-all-if-ambiguous: Readline Init File Syntax.
(line 337)
* show-all-if-unmodified: Readline Init File Syntax.
(line 343)
* show-mode-in-prompt: Readline Init File Syntax.
(line 352)
* skip-completed-text: Readline Init File Syntax.
(line 358)
* show-all-if-unmodified: Readline Init File Syntax.
(line 364)
* show-mode-in-prompt: Readline Init File Syntax.
(line 373)
* skip-completed-text: Readline Init File Syntax.
(line 379)
* SRANDOM: Bash Variables. (line 720)
* TEXTDOMAIN: Creating Internationalized Scripts.
(line 51)
@@ -12620,11 +12671,11 @@ D.3 Parameter and Variable Index
* TMPDIR: Bash Variables. (line 779)
* UID: Bash Variables. (line 783)
* vi-cmd-mode-string: Readline Init File Syntax.
(line 371)
(line 392)
* vi-ins-mode-string: Readline Init File Syntax.
(line 382)
(line 403)
* visible-stats: Readline Init File Syntax.
(line 393)
(line 414)

File: bash.info, Node: Function Index, Next: Concept Index, Prev: Variable Index, Up: Indexes
@@ -13010,138 +13061,138 @@ D.5 Concept Index

Tag Table:
Node: Top897
Node: Introduction2834
Node: What is Bash?3047
Node: What is a shell?4188
Node: Definitions6767
Node: Basic Shell Features9943
Node: Shell Syntax11163
Node: Shell Operation12190
Node: Quoting13488
Node: Escape Character14801
Node: Single Quotes15299
Node: Double Quotes15648
Node: ANSI-C Quoting16991
Node: Locale Translation18376
Node: Creating Internationalized Scripts19720
Node: Comments23918
Node: Shell Commands24553
Node: Reserved Words25492
Node: Simple Commands26357
Node: Pipelines27016
Node: Lists30079
Node: Compound Commands31951
Node: Looping Constructs32960
Node: Conditional Constructs35504
Node: Command Grouping50325
Node: Coprocesses51812
Node: GNU Parallel54508
Node: Shell Functions55426
Node: Shell Parameters63532
Node: Positional Parameters68065
Node: Special Parameters69000
Node: Shell Expansions72306
Node: Brace Expansion74495
Node: Tilde Expansion77158
Node: Shell Parameter Expansion79924
Node: Command Substitution99031
Node: Arithmetic Expansion102564
Node: Process Substitution103529
Node: Word Splitting104666
Node: Filename Expansion106807
Node: Pattern Matching109903
Node: Quote Removal115136
Node: Redirections115440
Node: Executing Commands125249
Node: Simple Command Expansion125916
Node: Command Search and Execution128027
Node: Command Execution Environment130435
Node: Environment133744
Node: Exit Status135448
Node: Signals137233
Node: Shell Scripts140847
Node: Shell Builtin Commands143939
Node: Bourne Shell Builtins146050
Node: Bash Builtins170820
Node: Modifying Shell Behavior205919
Node: The Set Builtin206261
Node: The Shopt Builtin217844
Node: Special Builtins234806
Node: Shell Variables235795
Node: Bourne Shell Variables236229
Node: Bash Variables238422
Node: Bash Features275617
Node: Invoking Bash276631
Node: Bash Startup Files283030
Node: Interactive Shells288333
Node: What is an Interactive Shell?288741
Node: Is this Shell Interactive?289407
Node: Interactive Shell Behavior290231
Node: Bash Conditional Expressions293985
Node: Shell Arithmetic299159
Node: Aliases302241
Node: Arrays305196
Node: The Directory Stack311995
Node: Directory Stack Builtins312792
Node: Controlling the Prompt317241
Node: The Restricted Shell320379
Node: Bash POSIX Mode323166
Node: Shell Compatibility Mode340677
Node: Job Control349444
Node: Job Control Basics349901
Node: Job Control Builtins355075
Node: Job Control Variables361019
Node: Command Line Editing362196
Node: Introduction and Notation363900
Node: Readline Interaction365544
Node: Readline Bare Essentials366732
Node: Readline Movement Commands368550
Node: Readline Killing Commands369547
Node: Readline Arguments371525
Node: Searching372582
Node: Readline Init File374811
Node: Readline Init File Syntax376093
Node: Conditional Init Constructs401031
Node: Sample Init File405396
Node: Bindable Readline Commands408517
Node: Commands For Moving409742
Node: Commands For History411969
Node: Commands For Text417174
Node: Commands For Killing421308
Node: Numeric Arguments424109
Node: Commands For Completion425261
Node: Keyboard Macros429577
Node: Miscellaneous Commands430278
Node: Readline vi Mode436932
Node: Programmable Completion437884
Node: Programmable Completion Builtins445841
Node: A Programmable Completion Example457407
Node: Using History Interactively462752
Node: Bash History Facilities463433
Node: Bash History Builtins466545
Node: History Interaction471788
Node: Event Designators476113
Node: Word Designators477696
Node: Modifiers479848
Node: Installing Bash481757
Node: Basic Installation482891
Node: Compilers and Options486770
Node: Compiling For Multiple Architectures487520
Node: Installation Names489269
Node: Specifying the System Type491503
Node: Sharing Defaults492249
Node: Operation Controls492963
Node: Optional Features493982
Node: Reporting Bugs505784
Node: Major Differences From The Bourne Shell507133
Node: GNU Free Documentation License526868
Node: Indexes552045
Node: Builtin Index552496
Node: Reserved Word Index559594
Node: Variable Index562039
Node: Function Index579170
Node: Concept Index593026
Node: Top901
Node: Introduction2842
Node: What is Bash?3055
Node: What is a shell?4196
Node: Definitions6775
Node: Basic Shell Features9951
Node: Shell Syntax11171
Node: Shell Operation12198
Node: Quoting13496
Node: Escape Character14809
Node: Single Quotes15307
Node: Double Quotes15656
Node: ANSI-C Quoting16999
Node: Locale Translation18384
Node: Creating Internationalized Scripts19728
Node: Comments23926
Node: Shell Commands24561
Node: Reserved Words25500
Node: Simple Commands26365
Node: Pipelines27024
Node: Lists30087
Node: Compound Commands31959
Node: Looping Constructs32968
Node: Conditional Constructs35512
Node: Command Grouping50373
Node: Coprocesses51860
Node: GNU Parallel54556
Node: Shell Functions55474
Node: Shell Parameters63580
Node: Positional Parameters68113
Node: Special Parameters69048
Node: Shell Expansions72358
Node: Brace Expansion74547
Node: Tilde Expansion77210
Node: Shell Parameter Expansion79976
Node: Command Substitution99083
Node: Arithmetic Expansion102616
Node: Process Substitution103581
Node: Word Splitting104718
Node: Filename Expansion106859
Node: Pattern Matching109955
Node: Quote Removal115188
Node: Redirections115492
Node: Executing Commands125301
Node: Simple Command Expansion125968
Node: Command Search and Execution128079
Node: Command Execution Environment130487
Node: Environment133796
Node: Exit Status135500
Node: Signals137285
Node: Shell Scripts140899
Node: Shell Builtin Commands143991
Node: Bourne Shell Builtins146102
Node: Bash Builtins170872
Node: Modifying Shell Behavior205971
Node: The Set Builtin206313
Node: The Shopt Builtin217896
Node: Special Builtins234858
Node: Shell Variables235847
Node: Bourne Shell Variables236281
Node: Bash Variables238474
Node: Bash Features275669
Node: Invoking Bash276683
Node: Bash Startup Files283082
Node: Interactive Shells288385
Node: What is an Interactive Shell?288793
Node: Is this Shell Interactive?289459
Node: Interactive Shell Behavior290283
Node: Bash Conditional Expressions294037
Node: Shell Arithmetic299211
Node: Aliases302293
Node: Arrays305248
Node: The Directory Stack312047
Node: Directory Stack Builtins312844
Node: Controlling the Prompt317293
Node: The Restricted Shell320431
Node: Bash POSIX Mode323218
Node: Shell Compatibility Mode341267
Node: Job Control350218
Node: Job Control Basics350675
Node: Job Control Builtins355972
Node: Job Control Variables361916
Node: Command Line Editing363093
Node: Introduction and Notation364797
Node: Readline Interaction366892
Node: Readline Bare Essentials368080
Node: Readline Movement Commands369898
Node: Readline Killing Commands370895
Node: Readline Arguments372873
Node: Searching373930
Node: Readline Init File376159
Node: Readline Init File Syntax377441
Node: Conditional Init Constructs403981
Node: Sample Init File408346
Node: Bindable Readline Commands411467
Node: Commands For Moving412692
Node: Commands For History414919
Node: Commands For Text420124
Node: Commands For Killing424258
Node: Numeric Arguments427059
Node: Commands For Completion428211
Node: Keyboard Macros432527
Node: Miscellaneous Commands433228
Node: Readline vi Mode439882
Node: Programmable Completion440834
Node: Programmable Completion Builtins448791
Node: A Programmable Completion Example460357
Node: Using History Interactively465702
Node: Bash History Facilities466383
Node: Bash History Builtins469495
Node: History Interaction474738
Node: Event Designators479063
Node: Word Designators480646
Node: Modifiers482798
Node: Installing Bash484707
Node: Basic Installation485841
Node: Compilers and Options489720
Node: Compiling For Multiple Architectures490470
Node: Installation Names492219
Node: Specifying the System Type494453
Node: Sharing Defaults495199
Node: Operation Controls495913
Node: Optional Features496932
Node: Reporting Bugs508734
Node: Major Differences From The Bourne Shell510083
Node: GNU Free Documentation License529818
Node: Indexes554995
Node: Builtin Index555446
Node: Reserved Word Index562544
Node: Variable Index564989
Node: Function Index582261
Node: Concept Index596117

End Tag Table