next set of documentation fixes: update formatting, make filename formatting consistent, typeset the name readline consistently

This commit is contained in:
Chet Ramey
2024-10-18 12:19:48 -04:00
parent 3ed028ccec
commit 261c6e8cc6
63 changed files with 21845 additions and 20671 deletions
+263 -254
View File
@@ -2,9 +2,9 @@ This is bashref.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, 14 October 2024).
Bash shell (version 5.3, 15 October 2024).
This is Edition 5.3, last updated 14 October 2024, of The GNU Bash
This is Edition 5.3, last updated 15 October 2024, of The GNU Bash
Reference Manual, for Bash, Version 5.3.
Copyright © 1988-2024 Free Software Foundation, Inc.
@@ -27,10 +27,10 @@ Bash Features
*************
This text is a brief description of the features that are present in the
Bash shell (version 5.3, 14 October 2024). The Bash home page is
Bash shell (version 5.3, 15 October 2024). The Bash home page is
<http://www.gnu.org/software/bash/>.
This is Edition 5.3, last updated 14 October 2024, of The GNU Bash
This is Edition 5.3, last updated 15 October 2024, of The GNU Bash
Reference Manual, for Bash, Version 5.3.
Bash contains features that appear in other popular shells, and some
@@ -2620,7 +2620,7 @@ set of filenames that are tested: when dotglob is enabled, the set of
filenames includes all files beginning with ., but the filenames .
and .. must be matched by a pattern or sub-pattern that begins with a
dot; when it is disabled, the set does not include any filenames
beginning with "." unless the pattern or sub-pattern begins with a ..
beginning with . unless the pattern or sub-pattern begins with a ..
If the globskipdots shell option is enabled, the filenames . and
.. never appear in the set. As above, . only has a special meaning
when matching filenames.
@@ -2674,7 +2674,7 @@ redirection refers to the standard input (file descriptor 0). If the
first character of the redirection operator is >, the redirection
refers to the standard output (file descriptor 1).
The \fIword\fP following the redirection operator in the following
The WORD following the redirection operator in the following
descriptions, unless otherwise noted, is subjected to brace expansion,
tilde expansion, parameter and variable expansion, command substitution,
arithmetic expansion, quote removal, filename expansion, and word
@@ -3408,18 +3408,19 @@ standard.
greater than or equal to 1.
cd
cd [-L|[-P [-e]]] [-@] [DIRECTORY]
cd [-L] [-@] [DIRECTORY]
cd -P [-e] [-@] [DIRECTORY]
Change the current working directory to DIRECTORY. If DIRECTORY is
not supplied, the value of the HOME shell variable is used as
DIRECTORY. If the shell variable CDPATH exists, cd uses it as
a search path: cd searches each directory name in CDPATH for
DIRECTORY, with alternative directory names in CDPATH separated
by a colon (:). A null directory name in CDPATH means the same
thing as the current directory. If DIRECTORY begins with a slash,
CDPATH is not used.
DIRECTORY. If the shell variable CDPATH exists, and DIRECTORY
does not begin with a slash, cd uses it as a search path: cd
searches each directory name in CDPATH for DIRECTORY, with
alternative directory names in CDPATH separated by a colon (:).
A null directory name in CDPATH means the same thing as the
current directory.
The -P option means to not follow symbolic links: symbolic links
The -P option means not to follow symbolic links: symbolic links
are resolved while cd is traversing DIRECTORY and before
processing an instance of .. in DIRECTORY.
@@ -3427,13 +3428,16 @@ standard.
DIRECTORY are resolved after cd processes an instance of .. in
DIRECTORY.
If .. appears in DIRECTORY, it is processed by removing the
If .. appears in DIRECTORY, cd processes it by removing the
immediately preceding pathname component, back to a slash or the
beginning of DIRECTORY.
beginning of DIRECTORY, and verifying that the portion of DIRECTORY
it has processed to that point is still a valid directory name
after removing the pathname component. If it is not a valid
directory name, cd returns a non-zero status.
If the -e option is supplied with -P and the current working
directory cannot be successfully determined after a successful
directory change, cd will return a non-zero status.
If the -e option is supplied with -P and cd cannot
successfully determine the current working directory after a
successful directory change, it will return a non-zero status.
On systems that support it, the -@ option presents the extended
attributes associated with a file as a directory.
@@ -5365,9 +5369,9 @@ This builtin allows you to change additional optional shell behavior.
completion.
noexpand_translation
If set, Bash encloses the translated results of $"..."
quoting in single quotes instead of double quotes. If the
string is not translated, this has no effect.
If set, Bash encloses the translated results of $"..." quoting
in single quotes instead of double quotes. If the string is
not translated, this has no effect.
nullglob
If set, filename expansion patterns which match no files
@@ -5841,7 +5845,7 @@ Variables::).
EPOCHREALTIME
Each time this parameter is referenced, it expands to the number of
seconds since the Unix Epoch as a floating point value with
seconds since the Unix Epoch as a floating-point value with
micro-second granularity (see the documentation for the C library
function time for the definition of Epoch). Assignments to
EPOCHREALTIME are ignored. If EPOCHREALTIME is unset, it loses
@@ -5913,12 +5917,15 @@ Variables::).
value of this variable specifies the sort criteria and sort order
for the results of filename expansion. If this variable is unset
or set to the null string, filename expansion uses the historical
behavior of sorting by name. If set, a valid value begins with an
optional +, which is ignored, or -, which reverses the sort
order from ascending to descending, followed by a sort specifier.
The valid sort specifiers are name, numeric, size, mtime,
atime, ctime, and blocks, which sort the files on name, names
in numeric rather than lexicographic order, file size, modification
behavior of sorting by name, in ascending lexicographic order as
determined by the LC_COLLATE shell variable.
If set, a valid value begins with an optional +, which is
ignored, or -, which reverses the sort order from ascending to
descending, followed by a sort specifier. The valid sort
specifiers are name, numeric, size, mtime, atime,
ctime, and blocks, which sort the files on name, names in
numeric rather than lexicographic order, file size, modification
time, access time, inode change time, and number of blocks,
respectively. If any of the non-name keys compare as equal (e.g.,
if two files are the same size), sorting uses the name as a
@@ -5928,14 +5935,14 @@ Variables::).
order by modification time (newest first).
The numeric specifier treats names consisting solely of digits as
numbers and sorts them using the numeric value (so "2" will sort
numbers and sorts them using their numeric value (so "2" will sort
before "10", for example). When using numeric, names containing
non-digits sort after all the all-digit names and are sorted by
name using the traditional behavior.
A sort specifier of nosort disables sorting completely; the
results are returned in the order they are read from the file
system, and any leading - is ignored.
A sort specifier of nosort disables sorting completely; Bash
returns the results in the order they are read from the file
system, ignoring any leading -.
If the sort specifier is missing, it defaults to NAME, so a value
of + is equivalent to the null string, and a value of - sorts
@@ -5952,17 +5959,16 @@ Variables::).
histchars
Up to three characters which control history expansion, quick
substitution, and tokenization (*note History Interaction::). The
first character is the “history expansion” character, that is, the
character which signifies the start of a history expansion,
normally !. The second character is the character which
signifies "quick substitution" when seen as the first character on
a line, normally ^. The optional third character is the
character which indicates that the remainder of the line is a
comment when found as the first character of a word, usually #.
The history comment character causes history substitution to be
skipped for the remaining words on the line. It does not
necessarily cause the shell parser to treat the rest of the line as
a comment.
first character is the “history expansion” character, the character
which begins a history expansion, normally !. The second
character is the character which signifies "quick substitution"
when seen as the first character on a line, normally ^. The
optional third character is the character which indicates that the
remainder of the line is a comment when found as the first
character of a word, usually #. The history comment character
disables history substitution for the remaining words on the line.
It does not necessarily cause the shell parser to treat the rest of
the line as a comment.
HISTCMD
The history number, or index in the history list, of the current
@@ -6578,7 +6584,7 @@ conforming to the POSIX standard as well.
When invoked as an interactive login shell, or as a non-interactive
shell with the --login option, it first attempts to read and execute
commands from /etc/profile and ~/.profile, in that order. The
--noprofile option may be used to inhibit this behavior.
--noprofile option will inhibit this behavior.
When invoked as an interactive shell with the name sh, Bash looks
for the variable ENV, expands its value if it is defined, and uses the
@@ -6589,8 +6595,8 @@ other startup files, the --rcfile option has no effect.
A non-interactive shell invoked with the name sh does not attempt
to read any other startup files.
When invoked as sh, Bash enters POSIX mode after the startup files
are read.
When invoked as sh, Bash enters POSIX mode after reading the
startup files.
Invoked in POSIX mode
.....................
@@ -6610,10 +6616,10 @@ and rarely-seen remote shell daemon, usually rshd, or the secure shell
daemon sshd. If Bash determines it is being run non-interactively in
this fashion, it reads and executes commands from ~/.bashrc, if that
file exists and is readable. It will not do this if invoked as sh.
The --norc option may be used to inhibit this behavior, and the
--rcfile option will make Bash use a different file instead of
~/.bashrc, but neither rshd nor sshd generally invoke the shell
with those options or allow them to be specified.
The --norc option will inhibit this behavior, and the --rcfile
option will make Bash use a different file instead of ~/.bashrc, but
neither rshd nor sshd generally invoke the shell with those options
or allow them to be specified.
Invoked with unequal effective and real UID/GIDs
................................................
@@ -6787,10 +6793,10 @@ numeric, and file attribute comparisons.
expressions. If the operating system on which Bash is running provides
these special files, Bash will use them; otherwise it will emulate them
internally with this behavior: If the FILE argument to one of the
primaries is of the form /dev/fd/N, then file descriptor N is checked.
If the FILE argument to one of the primaries is one of /dev/stdin,
/dev/stdout, or /dev/stderr, file descriptor 0, 1, or 2,
respectively, is checked.
primaries is of the form /dev/fd/N, then Bash checks file descriptor
N. If the FILE argument to one of the primaries is one of /dev/stdin,
/dev/stdout, or /dev/stderr, Bash checks file descriptor 0, 1, or 2,
respectively.
When used with [[, the < and > operators sort lexicographically
using the current locale. The test command uses ASCII ordering.
@@ -6997,9 +7003,9 @@ levels are listed in order of decreasing precedence.
Shell variables are allowed as operands; parameter expansion is
performed before the expression is evaluated. Within an expression,
shell variables may also be referenced by name without using the
parameter expansion syntax. This means you can use .Q x , where \fIx\fP
is a shell variable name, in an arithmetic expression, and the shell
will evaluate its value as an expression and use the result. A shell
parameter expansion syntax. This means you can use X, where X is a
shell variable name, in an arithmetic expression, and the shell will
evaluate its value as an expression and use the result. A shell
variable that is null or unset evaluates to 0 when referenced by name in
an expression.
@@ -7663,6 +7669,9 @@ startup files.
27. Bash permanently removes jobs from the jobs table after notifying
the user of their termination via the wait or jobs builtins.
It removes the job from the jobs list after notifying the user of
its termination, but the status is still available via wait, as
long as wait is supplied a PID argument.
28. The vi editing mode will invoke the vi editor directly when
the v command is run, instead of checking $VISUAL and
@@ -7855,7 +7864,7 @@ startup files.
The trap command is run once for each child that exits.
75. Bash removes an exited background process's status from the list
of such statuses after the wait builtin is used to obtain it.
of such statuses after the wait builtin returns it.
There is other POSIX behavior that Bash does not implement by default
even when in POSIX mode. Specifically:
@@ -7998,13 +8007,13 @@ required for bash-5.1 and later versions.
like a[@]. Bash-5.2 will unset an element with key @
(associative arrays) or remove all the elements without
unsetting the array (indexed arrays).
• Arithmetic commands ( ((...)) ) and the expressions in an
• Arithmetic commands ( ((...)) ) and the expressions in an
arithmetic for statement can be expanded more than once.
• Expressions used as arguments to arithmetic operators in the
[[ conditional command can be expanded more than once.
• The expressions in substring parameter brace expansion can be
expanded more than once.
• The expressions in the $(( ... )) word expansion can be
• The expressions in the $(( ... )) word expansion can be
expanded more than once.
• Arithmetic expressions used as indexed array subscripts can be
expanded more than once.
@@ -8142,7 +8151,7 @@ about changes 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 foreground
command in a list completes, before executing the next command in the
list. If the -b option to the set builtin is enabled, Bash reports
such changes immediately (*note The Set Builtin::). Bash executes any
status changes immediately (*note The Set Builtin::). Bash executes any
trap on SIGCHLD for each child process that terminates.
When a job terminates and Bash notifies the user about it, Bash
@@ -8378,27 +8387,26 @@ File: bashref.info, Node: Introduction and Notation, Next: Readline Interactio
8.1 Introduction to Line Editing
================================
The following paragraphs describe the notation used to represent
keystrokes.
The following paragraphs use Emacs style to describe the notation used
to represent keystrokes.
The text C-k is read as 'Control-K' and describes the character
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 (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.
key is pressed (a “meta character”), then both are released. The Meta
key is labeled <ALT> or <Option> 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. One of
the <ALT> keys may also 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.
On some keyboards, the Meta key modifier produces 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, you can generally achieve the latter effect by typing <ESC>
@@ -8643,7 +8651,7 @@ keybindings. Any user can customize programs that use Readline by
putting commands in an “inputrc” file, conventionally in their home
directory. The name of this file is taken from the value of the shell
variable INPUTRC. If that variable is unset, the default is
~/.inputrc. If that file does not exist or cannot be read, readline
~/.inputrc. If that file does not exist or cannot be read, Readline
looks for /etc/inputrc. The bind builtin command can also be used
to set Readline keybindings and variables. *Note Bash Builtins::.
@@ -8748,9 +8756,9 @@ Variable Settings
different color. The color definitions are taken from the
value of the LS_COLORS environment variable. If there is a
color definition in LS_COLORS for the custom suffix
readline-colored-completion-prefix, Readline uses this color
for the common prefix instead of its default. The default is
off.
.readline-colored-completion-prefix, Readline uses this
color for the common prefix instead of its default. The
default is off.
colored-stats
If set to on, Readline displays possible completions using
@@ -8783,7 +8791,7 @@ Variable Settings
completion-prefix-display-length
The maximum length in characters of the common prefix of a
list of possible completions that is displayed without
modification. When set to a value greater than zero, readline
modification. When set to a value greater than zero, Readline
replaces common prefixes longer than this value with an
ellipsis when displaying possible completions.
@@ -8882,7 +8890,7 @@ Variable Settings
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 ESCC (adding the meta prefix). If
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,
@@ -9043,7 +9051,7 @@ Variable Settings
If set to on, this alters the default completion behavior
when inserting a single match into the line. It's only active
when performing completion in the middle of a word. If
enabled, readline does not insert characters from the
enabled, Readline does not insert characters from the
completion that match characters after point in the word being
completed, so portions of the word following the cursor are
not duplicated. For instance, if this is enabled, attempting
@@ -9417,9 +9425,10 @@ sequence are unbound by default.
position, and “mark” refers to a cursor position saved by the set-mark
command. The text between the point and mark is referred to as the
“region”. Readline has the concept of an _active region_: when the
region is active, Readline redisplay uses the value of the
active-region-start-color variable to denote the region. Several
commands set the region to active; those are noted below.
region is active, Readline redisplay highlights the region using the
value of the active-region-start-color variable. The
enable-active-region variable turns this on and off. Several commands
set the region to active; those are noted below.

File: bashref.info, Node: Commands For Moving, Next: Commands For History, Up: Bindable Readline Commands
@@ -10005,7 +10014,7 @@ File: bashref.info, Node: Miscellaneous Commands, Prev: Keyboard Macros, Up:
default.
execute-named-command (M-x)
Read a bindable readline command name from the input and execute
Read a bindable Readline command name from the input and execute
the function to which it's bound, as if the key sequence to which
it was bound appeared in the input. If this function is supplied
with a numeric argument, it passes that argument to the function it
@@ -10094,7 +10103,7 @@ File: bashref.info, Node: Programmable Completion, Next: Programmable Completi
When the user attempts word completion for an argument to a command for
which a completion specification (a “compspec”) has been defined using
the complete builtin (*note Programmable Completion Builtins::),
\fBreadline\fP invokes the programmable completion facilities.
Readline invokes the programmable completion facilities.
First, Bash identifies the command name. If a compspec has been
defined for that command, the compspec is used to generate the list of
@@ -10495,7 +10504,7 @@ happening.
other supplied options should apply to "empty" command completion;
and the -I option indicates that other supplied options should
apply to completion on the initial word on the line. These are
determined in the same way as the \fBcomplete\fP builtin.
determined in the same way as the complete builtin.
If multiple options are supplied, the -D option takes precedence
over -E, and both take precedence over -I
@@ -11255,7 +11264,7 @@ you want the object files and executables to go and run the configure
script from the source directory (*note Basic Installation::). You may
need to supply the --srcdir=PATH argument to tell configure where
the source files are. configure automatically checks for the source
code in the directory that configure is in and in '..'.
code in the directory that configure is in and in ...
If you have to use a make that does not support the VPATH
variable, you can compile Bash for one architecture at a time in the
@@ -12646,7 +12655,7 @@ D.1 Index of Shell Builtin Commands
* .: Bourne Shell Builtins.
(line 17)
* [: Bourne Shell Builtins.
(line 333)
(line 337)
* alias: Bash Builtins. (line 11)
* bg: Job Control Builtins.
(line 7)
@@ -12665,7 +12674,7 @@ D.1 Index of Shell Builtin Commands
* compopt: Programmable Completion Builtins.
(line 257)
* continue: Bourne Shell Builtins.
(line 102)
(line 106)
* declare: Bash Builtins. (line 179)
* dirs: Directory Stack Builtins.
(line 7)
@@ -12674,23 +12683,23 @@ D.1 Index of Shell Builtin Commands
* echo: Bash Builtins. (line 284)
* enable: Bash Builtins. (line 337)
* eval: Bourne Shell Builtins.
(line 111)
(line 115)
* exec: Bourne Shell Builtins.
(line 119)
(line 123)
* exit: Bourne Shell Builtins.
(line 141)
(line 145)
* export: Bourne Shell Builtins.
(line 148)
(line 152)
* false: Bourne Shell Builtins.
(line 170)
(line 174)
* fc: Bash History Builtins.
(line 10)
* fg: Job Control Builtins.
(line 17)
* getopts: Bourne Shell Builtins.
(line 175)
(line 179)
* hash: Bourne Shell Builtins.
(line 226)
(line 230)
* help: Bash Builtins. (line 374)
* history: Bash History Builtins.
(line 59)
@@ -12708,36 +12717,36 @@ D.1 Index of Shell Builtin Commands
* pushd: Directory Stack Builtins.
(line 70)
* pwd: Bourne Shell Builtins.
(line 258)
(line 262)
* read: Bash Builtins. (line 548)
* readarray: Bash Builtins. (line 659)
* readonly: Bourne Shell Builtins.
(line 270)
(line 274)
* return: Bourne Shell Builtins.
(line 295)
(line 299)
* set: The Set Builtin. (line 11)
* shift: Bourne Shell Builtins.
(line 320)
(line 324)
* shopt: The Shopt Builtin. (line 9)
* source: Bash Builtins. (line 668)
* suspend: Job Control Builtins.
(line 139)
* test: Bourne Shell Builtins.
(line 333)
(line 337)
* times: Bourne Shell Builtins.
(line 433)
(line 437)
* trap: Bourne Shell Builtins.
(line 439)
(line 443)
* true: Bourne Shell Builtins.
(line 505)
(line 509)
* type: Bash Builtins. (line 673)
* typeset: Bash Builtins. (line 710)
* ulimit: Bash Builtins. (line 716)
* umask: Bourne Shell Builtins.
(line 510)
(line 514)
* unalias: Bash Builtins. (line 824)
* unset: Bourne Shell Builtins.
(line 528)
(line 532)
* wait: Job Control Builtins.
(line 86)
@@ -12908,57 +12917,57 @@ D.3 Parameter and Variable Index
* FUNCNEST: Bash Variables. (line 363)
* GLOBIGNORE: Bash Variables. (line 368)
* GLOBSORT: Bash Variables. (line 375)
* GROUPS: Bash Variables. (line 410)
* histchars: Bash Variables. (line 416)
* HISTCMD: Bash Variables. (line 431)
* HISTCONTROL: Bash Variables. (line 437)
* HISTFILE: Bash Variables. (line 455)
* HISTFILESIZE: Bash Variables. (line 461)
* HISTIGNORE: Bash Variables. (line 472)
* GROUPS: Bash Variables. (line 413)
* histchars: Bash Variables. (line 419)
* HISTCMD: Bash Variables. (line 433)
* HISTCONTROL: Bash Variables. (line 439)
* HISTFILE: Bash Variables. (line 457)
* HISTFILESIZE: Bash Variables. (line 463)
* HISTIGNORE: Bash Variables. (line 474)
* history-preserve-point: Readline Init File Syntax.
(line 232)
* history-size: Readline Init File Syntax.
(line 238)
* HISTSIZE: Bash Variables. (line 496)
* HISTTIMEFORMAT: Bash Variables. (line 503)
* HISTSIZE: Bash Variables. (line 498)
* HISTTIMEFORMAT: Bash Variables. (line 505)
* HOME: Bourne Shell Variables.
(line 13)
* horizontal-scroll-mode: Readline Init File Syntax.
(line 248)
* HOSTFILE: Bash Variables. (line 512)
* HOSTNAME: Bash Variables. (line 523)
* HOSTTYPE: Bash Variables. (line 526)
* HOSTFILE: Bash Variables. (line 514)
* HOSTNAME: Bash Variables. (line 525)
* HOSTTYPE: Bash Variables. (line 528)
* IFS: Bourne Shell Variables.
(line 18)
* IGNOREEOF: Bash Variables. (line 529)
* IGNOREEOF: Bash Variables. (line 531)
* input-meta: Readline Init File Syntax.
(line 256)
* INPUTRC: Bash Variables. (line 538)
* INSIDE_EMACS: Bash Variables. (line 542)
* INPUTRC: Bash Variables. (line 540)
* INSIDE_EMACS: Bash Variables. (line 544)
* isearch-terminators: Readline Init File Syntax.
(line 267)
* keymap: Readline Init File Syntax.
(line 274)
* LANG: Creating Internationalized Scripts.
(line 51)
* LANG <1>: Bash Variables. (line 548)
* LC_ALL: Bash Variables. (line 552)
* LC_COLLATE: Bash Variables. (line 556)
* LC_CTYPE: Bash Variables. (line 563)
* LANG <1>: Bash Variables. (line 550)
* LC_ALL: Bash Variables. (line 554)
* LC_COLLATE: Bash Variables. (line 558)
* LC_CTYPE: Bash Variables. (line 565)
* LC_MESSAGES: Creating Internationalized Scripts.
(line 51)
* LC_MESSAGES <1>: Bash Variables. (line 568)
* LC_NUMERIC: Bash Variables. (line 572)
* LC_TIME: Bash Variables. (line 576)
* LINENO: Bash Variables. (line 580)
* LINES: Bash Variables. (line 587)
* MACHTYPE: Bash Variables. (line 593)
* LC_MESSAGES <1>: Bash Variables. (line 570)
* LC_NUMERIC: Bash Variables. (line 574)
* LC_TIME: Bash Variables. (line 578)
* LINENO: Bash Variables. (line 582)
* LINES: Bash Variables. (line 589)
* MACHTYPE: Bash Variables. (line 595)
* MAIL: Bourne Shell Variables.
(line 24)
* MAILCHECK: Bash Variables. (line 597)
* MAILCHECK: Bash Variables. (line 599)
* MAILPATH: Bourne Shell Variables.
(line 29)
* MAPFILE: Bash Variables. (line 605)
* MAPFILE: Bash Variables. (line 607)
* mark-modified-lines: Readline Init File Syntax.
(line 304)
* mark-symlinked-directories: Readline Init File Syntax.
@@ -12969,46 +12978,46 @@ D.3 Parameter and Variable Index
(line 321)
* meta-flag: Readline Init File Syntax.
(line 256)
* OLDPWD: Bash Variables. (line 609)
* OLDPWD: Bash Variables. (line 611)
* OPTARG: Bourne Shell Variables.
(line 36)
* OPTERR: Bash Variables. (line 612)
* OPTERR: Bash Variables. (line 614)
* OPTIND: Bourne Shell Variables.
(line 40)
* OSTYPE: Bash Variables. (line 617)
* OSTYPE: Bash Variables. (line 619)
* output-meta: Readline Init File Syntax.
(line 326)
* page-completions: Readline Init File Syntax.
(line 335)
* PATH: Bourne Shell Variables.
(line 44)
* PIPESTATUS: Bash Variables. (line 620)
* POSIXLY_CORRECT: Bash Variables. (line 626)
* PPID: Bash Variables. (line 636)
* PROMPT_COMMAND: Bash Variables. (line 640)
* PROMPT_DIRTRIM: Bash Variables. (line 646)
* PS0: Bash Variables. (line 652)
* PIPESTATUS: Bash Variables. (line 622)
* POSIXLY_CORRECT: Bash Variables. (line 628)
* PPID: Bash Variables. (line 638)
* PROMPT_COMMAND: Bash Variables. (line 642)
* PROMPT_DIRTRIM: Bash Variables. (line 648)
* PS0: Bash Variables. (line 654)
* PS1: Bourne Shell Variables.
(line 53)
* PS2: Bourne Shell Variables.
(line 58)
* PS3: Bash Variables. (line 657)
* PS4: Bash Variables. (line 662)
* PWD: Bash Variables. (line 670)
* RANDOM: Bash Variables. (line 673)
* READLINE_ARGUMENT: Bash Variables. (line 681)
* READLINE_LINE: Bash Variables. (line 685)
* READLINE_MARK: Bash Variables. (line 689)
* READLINE_POINT: Bash Variables. (line 695)
* REPLY: Bash Variables. (line 699)
* PS3: Bash Variables. (line 659)
* PS4: Bash Variables. (line 664)
* PWD: Bash Variables. (line 672)
* RANDOM: Bash Variables. (line 675)
* READLINE_ARGUMENT: Bash Variables. (line 683)
* READLINE_LINE: Bash Variables. (line 687)
* READLINE_MARK: Bash Variables. (line 691)
* READLINE_POINT: Bash Variables. (line 697)
* REPLY: Bash Variables. (line 701)
* revert-all-at-newline: Readline Init File Syntax.
(line 348)
* search-ignore-case: Readline Init File Syntax.
(line 355)
* SECONDS: Bash Variables. (line 703)
* SHELL: Bash Variables. (line 713)
* SHELLOPTS: Bash Variables. (line 718)
* SHLVL: Bash Variables. (line 727)
* SECONDS: Bash Variables. (line 705)
* SHELL: Bash Variables. (line 715)
* SHELLOPTS: Bash Variables. (line 720)
* SHLVL: Bash Variables. (line 729)
* show-all-if-ambiguous: Readline Init File Syntax.
(line 360)
* show-all-if-unmodified: Readline Init File Syntax.
@@ -13017,15 +13026,15 @@ D.3 Parameter and Variable Index
(line 375)
* skip-completed-text: Readline Init File Syntax.
(line 381)
* SRANDOM: Bash Variables. (line 732)
* SRANDOM: Bash Variables. (line 734)
* TEXTDOMAIN: Creating Internationalized Scripts.
(line 51)
* TEXTDOMAINDIR: Creating Internationalized Scripts.
(line 51)
* TIMEFORMAT: Bash Variables. (line 741)
* TMOUT: Bash Variables. (line 780)
* TMPDIR: Bash Variables. (line 792)
* UID: Bash Variables. (line 796)
* TIMEFORMAT: Bash Variables. (line 743)
* TMOUT: Bash Variables. (line 782)
* TMPDIR: Bash Variables. (line 794)
* UID: Bash Variables. (line 798)
* vi-cmd-mode-string: Readline Init File Syntax.
(line 394)
* vi-ins-mode-string: Readline Init File Syntax.
@@ -13459,97 +13468,97 @@ Node: Process Substitution106061
Node: Word Splitting107180
Node: Filename Expansion109280
Node: Pattern Matching112551
Node: Quote Removal117888
Node: Redirections118195
Node: Executing Commands128413
Node: Simple Command Expansion129083
Node: Command Search and Execution131194
Node: Command Execution Environment133641
Node: Environment137092
Node: Exit Status138998
Node: Signals141059
Node: Shell Scripts144960
Node: Shell Builtin Commands148261
Node: Bourne Shell Builtins150375
Node: Bash Builtins176679
Node: Modifying Shell Behavior213130
Node: The Set Builtin213475
Node: The Shopt Builtin225414
Node: Special Builtins242469
Node: Shell Variables243461
Node: Bourne Shell Variables243898
Node: Bash Variables246409
Node: Bash Features284669
Node: Invoking Bash285686
Node: Bash Startup Files292115
Node: Interactive Shells297431
Node: What is an Interactive Shell?297842
Node: Is this Shell Interactive?298507
Node: Interactive Shell Behavior299334
Node: Bash Conditional Expressions303098
Node: Shell Arithmetic308318
Node: Aliases311660
Node: Arrays314798
Node: The Directory Stack321864
Node: Directory Stack Builtins322664
Node: Controlling the Prompt327112
Node: The Restricted Shell329999
Node: Bash POSIX Mode332884
Node: Shell Compatibility Mode351028
Node: Job Control360042
Node: Job Control Basics360502
Node: Job Control Builtins366781
Node: Job Control Variables373466
Node: Command Line Editing374700
Node: Introduction and Notation376406
Node: Readline Interaction378759
Node: Readline Bare Essentials379950
Node: Readline Movement Commands381761
Node: Readline Killing Commands382760
Node: Readline Arguments384786
Node: Searching385846
Node: Readline Init File388110
Node: Readline Init File Syntax389417
Node: Conditional Init Constructs416166
Node: Sample Init File420554
Node: Bindable Readline Commands423678
Node: Commands For Moving425153
Node: Commands For History427383
Node: Commands For Text432639
Node: Commands For Killing436767
Node: Numeric Arguments439558
Node: Commands For Completion440713
Node: Keyboard Macros445216
Node: Miscellaneous Commands445920
Node: Readline vi Mode452476
Node: Programmable Completion453456
Node: Programmable Completion Builtins461511
Node: A Programmable Completion Example473179
Node: Using History Interactively478527
Node: Bash History Facilities479211
Node: Bash History Builtins482949
Node: History Interaction489423
Node: Event Designators494380
Node: Word Designators495961
Node: Modifiers498272
Node: Installing Bash500216
Node: Basic Installation501335
Node: Compilers and Options505214
Node: Compiling For Multiple Architectures505967
Node: Installation Names507719
Node: Specifying the System Type509956
Node: Sharing Defaults510705
Node: Operation Controls511422
Node: Optional Features512444
Node: Reporting Bugs524827
Node: Major Differences From The Bourne Shell526188
Node: GNU Free Documentation License547611
Node: Indexes572791
Node: Builtin Index573245
Node: Reserved Word Index580346
Node: Variable Index582794
Node: Function Index600210
Node: Concept Index614069
Node: Quote Removal117891
Node: Redirections118198
Node: Executing Commands128410
Node: Simple Command Expansion129080
Node: Command Search and Execution131191
Node: Command Execution Environment133638
Node: Environment137089
Node: Exit Status138995
Node: Signals141056
Node: Shell Scripts144957
Node: Shell Builtin Commands148258
Node: Bourne Shell Builtins150372
Node: Bash Builtins176925
Node: Modifying Shell Behavior213376
Node: The Set Builtin213721
Node: The Shopt Builtin225660
Node: Special Builtins242715
Node: Shell Variables243707
Node: Bourne Shell Variables244144
Node: Bash Variables246655
Node: Bash Features284967
Node: Invoking Bash285984
Node: Bash Startup Files292413
Node: Interactive Shells297708
Node: What is an Interactive Shell?298119
Node: Is this Shell Interactive?298784
Node: Interactive Shell Behavior299611
Node: Bash Conditional Expressions303375
Node: Shell Arithmetic308597
Node: Aliases311929
Node: Arrays315067
Node: The Directory Stack322133
Node: Directory Stack Builtins322933
Node: Controlling the Prompt327381
Node: The Restricted Shell330268
Node: Bash POSIX Mode333153
Node: Shell Compatibility Mode351485
Node: Job Control360495
Node: Job Control Basics360955
Node: Job Control Builtins367236
Node: Job Control Variables373921
Node: Command Line Editing375155
Node: Introduction and Notation376861
Node: Readline Interaction379216
Node: Readline Bare Essentials380407
Node: Readline Movement Commands382218
Node: Readline Killing Commands383217
Node: Readline Arguments385243
Node: Searching386303
Node: Readline Init File388567
Node: Readline Init File Syntax389874
Node: Conditional Init Constructs416625
Node: Sample Init File421013
Node: Bindable Readline Commands424137
Node: Commands For Moving425678
Node: Commands For History427908
Node: Commands For Text433164
Node: Commands For Killing437292
Node: Numeric Arguments440083
Node: Commands For Completion441238
Node: Keyboard Macros445741
Node: Miscellaneous Commands446445
Node: Readline vi Mode453001
Node: Programmable Completion453981
Node: Programmable Completion Builtins462030
Node: A Programmable Completion Example473698
Node: Using History Interactively479046
Node: Bash History Facilities479730
Node: Bash History Builtins483468
Node: History Interaction489942
Node: Event Designators494899
Node: Word Designators496480
Node: Modifiers498791
Node: Installing Bash500735
Node: Basic Installation501854
Node: Compilers and Options505733
Node: Compiling For Multiple Architectures506486
Node: Installation Names508242
Node: Specifying the System Type510479
Node: Sharing Defaults511228
Node: Operation Controls511945
Node: Optional Features512967
Node: Reporting Bugs525350
Node: Major Differences From The Bourne Shell526711
Node: GNU Free Documentation License548134
Node: Indexes573314
Node: Builtin Index573768
Node: Reserved Word Index580869
Node: Variable Index583317
Node: Function Index600733
Node: Concept Index614592

End Tag Table