mirror of
https://https.git.savannah.gnu.org/git/bash.git
synced 2026-06-29 16:39:53 +02:00
do not require leading . for rl color prefix etension; fix for isearch in single-byte locales; next set of doc updates (SIGNALS); add warning for invalid job id; allow function names to be non-identifiers in posix mode
This commit is contained in:
Chet Ramey
+181
-169
@@ -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, 20 October 2024).
|
||||
Bash shell (version 5.3, 23 October 2024).
|
||||
|
||||
This is Edition 5.3, last updated 20 October 2024, of ‘The GNU Bash
|
||||
This is Edition 5.3, last updated 23 October 2024, of ‘The GNU Bash
|
||||
Reference Manual’, for ‘Bash’, Version 5.3.
|
||||
|
||||
Copyright © 1988-2024 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, 20 October 2024). The Bash home page is
|
||||
Bash shell (version 5.3, 23 October 2024). The Bash home page is
|
||||
<http://www.gnu.org/software/bash/>.
|
||||
|
||||
This is Edition 5.3, last updated 20 October 2024, of ‘The GNU Bash
|
||||
This is Edition 5.3, last updated 23 October 2024, of ‘The GNU Bash
|
||||
Reference Manual’, for ‘Bash’, Version 5.3.
|
||||
|
||||
Bash contains features that appear in other popular shells, and some
|
||||
@@ -3222,7 +3222,7 @@ Shopt Builtin::), Bash sends a ‘SIGHUP’ to all jobs when an interactive
|
||||
login shell exits.
|
||||
|
||||
If Bash is waiting for a command to complete and receives a signal
|
||||
for which a trap has been set, the trap will not be executed until the
|
||||
for which a trap has been set, it will not execute the trap until the
|
||||
command completes. If Bash is waiting for an asynchronous command via
|
||||
the ‘wait’ builtin, and it receives a signal for which a trap has been
|
||||
set, the ‘wait’ builtin will return immediately with an exit status
|
||||
@@ -3233,19 +3233,28 @@ command to complete, the shell receives keyboard-generated signals such
|
||||
as ‘SIGINT’ (usually generated by ‘^C’) that users commonly intend to
|
||||
send to that command. This happens because the shell and the command
|
||||
are in the same process group as the terminal, and ‘^C’ sends ‘SIGINT’
|
||||
to all processes in that process group. See *note Job Control::, for a
|
||||
more in-depth discussion of process groups.
|
||||
to all processes in that process group. Since Bash does not enable job
|
||||
control by default when the shell is not interactive, this scenario is
|
||||
most common in non-interactive shells.
|
||||
|
||||
When Bash is running without job control enabled and receives
|
||||
‘SIGINT’ while waiting for a foreground command, it waits until that
|
||||
foreground command terminates and then decides what to do about the
|
||||
‘SIGINT’:
|
||||
When job control is enabled, and Bash is waiting for a foreground
|
||||
command to complete, the shell does not receive keyboard-generated
|
||||
signals, because it is not in the same process group as the terminal.
|
||||
This scenario is most common in interactive shells, where Bash attempts
|
||||
to enable job control by default. See *note Job Control::, for a more
|
||||
in-depth discussion of process groups.
|
||||
|
||||
When job control is not enabled, and Bash receives ‘SIGINT’ while
|
||||
waiting for a foreground command, it waits until that foreground command
|
||||
terminates and then decides what to do about the ‘SIGINT’:
|
||||
|
||||
1. If the command terminates due to the ‘SIGINT’, Bash concludes that
|
||||
the user meant to end the entire script, and acts on the ‘SIGINT’
|
||||
(e.g., by running a ‘SIGINT’ trap or exiting itself);
|
||||
the user meant to send the ‘SIGINT’ to the shell as well, and acts
|
||||
on the ‘SIGINT’ (e.g., by running a ‘SIGINT’ trap, exiting a
|
||||
non-interactive shell, or returning to the top level to read a new
|
||||
command).
|
||||
|
||||
2. If the pipeline does not terminate due to ‘SIGINT’, the program
|
||||
2. If the command does not terminate due to ‘SIGINT’, the program
|
||||
handled the ‘SIGINT’ itself and did not treat it as a fatal signal.
|
||||
In that case, Bash does not treat ‘SIGINT’ as a fatal signal,
|
||||
either, instead assuming that the ‘SIGINT’ was used as part of the
|
||||
@@ -3255,6 +3264,14 @@ foreground command terminates and then decides what to do about the
|
||||
receives while it is waiting for the foreground command to
|
||||
complete, for compatibility.
|
||||
|
||||
When job control is enabled, Bash does not receive keyboard-generated
|
||||
signals such as ‘SIGINT’ while it is waiting for a foreground command.
|
||||
An interactive shell does not pay attention to the ‘SIGINT’, even if the
|
||||
foreground command terminates as a result, other than noting its exit
|
||||
status. If the shell is not interactive, and the foreground command
|
||||
terminates due to the ‘SIGINT’, Bash pretends it received the ‘SIGINT’
|
||||
itself (scenario 1 above), for compatibility.
|
||||
|
||||
|
||||
File: bash.info, Node: Shell Scripts, Prev: Executing Commands, Up: Basic Shell Features
|
||||
|
||||
@@ -7610,116 +7627,111 @@ startup files.
|
||||
10. Redirection operators do not perform word splitting on the word in
|
||||
a redirection.
|
||||
|
||||
11. 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 in a non-interactive shell is a fatal syntax error.
|
||||
|
||||
12. Function names may not be the same as one of the POSIX special
|
||||
11. Function names may not be the same as one of the POSIX special
|
||||
builtins.
|
||||
|
||||
13. Tilde expansion is only performed on assignments preceding a
|
||||
12. Tilde expansion is only performed on assignments preceding a
|
||||
command name, rather than on all assignment statements on the line.
|
||||
|
||||
14. While variable indirection is available, it may not be applied to
|
||||
13. While variable indirection is available, it may not be applied to
|
||||
the ‘#’ and ‘?’ special parameters.
|
||||
|
||||
15. Expanding the ‘*’ special parameter in a pattern context where the
|
||||
14. Expanding the ‘*’ special parameter in a pattern context where the
|
||||
expansion is double-quoted does not treat the ‘$*’ as if it were
|
||||
double-quoted.
|
||||
|
||||
16. A double quote character (‘"’) is treated specially when it
|
||||
15. 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.
|
||||
|
||||
17. Command substitutions don't set the ‘?’ special parameter. The
|
||||
16. 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
|
||||
command, but that does not happen until after all of the
|
||||
assignments and redirections.
|
||||
|
||||
18. Literal tildes that appear as the first character in elements of
|
||||
17. Literal tildes that appear as the first character in elements of
|
||||
the ‘PATH’ variable are not expanded as described above under *note
|
||||
Tilde Expansion::.
|
||||
|
||||
19. Command lookup finds POSIX special builtins before shell
|
||||
18. Command lookup finds POSIX special builtins before shell
|
||||
functions, including output printed by the ‘type’ and ‘command’
|
||||
builtins.
|
||||
|
||||
20. 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.
|
||||
|
||||
21. When a command in the hash table no longer exists, Bash will
|
||||
20. When a command in the hash table no longer exists, Bash will
|
||||
re-search ‘$PATH’ to find the new location. This is also available
|
||||
with ‘shopt -s checkhash’.
|
||||
|
||||
22. Bash will not insert a command without the execute bit set into
|
||||
21. Bash will not insert a command without the execute bit set into
|
||||
the command hash table, even if it returns it as a (last-ditch)
|
||||
result from a ‘$PATH’ search.
|
||||
|
||||
23. The message printed by the job control code and builtins when a
|
||||
22. The message printed by the job control code and builtins when a
|
||||
job exits with a non-zero status is 'Done(status)'.
|
||||
|
||||
24. The message printed by the job control code and builtins when a
|
||||
23. The message printed by the job control code and builtins when a
|
||||
job is stopped is 'Stopped(SIGNAME)', where SIGNAME is, for
|
||||
example, ‘SIGTSTP’.
|
||||
|
||||
25. If the shell is interactive, Bash does not perform job
|
||||
24. 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.
|
||||
|
||||
26. If the shell is interactive, Bash waits until the next prompt
|
||||
25. 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.
|
||||
|
||||
27. Bash permanently removes jobs from the jobs table after notifying
|
||||
26. 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
|
||||
27. The ‘vi’ editing mode will invoke the ‘vi’ editor directly when
|
||||
the ‘v’ command is run, instead of checking ‘$VISUAL’ and
|
||||
‘$EDITOR’.
|
||||
|
||||
29. Prompt expansion enables the POSIX ‘PS1’ and ‘PS2’ expansions of
|
||||
28. Prompt expansion enables the POSIX ‘PS1’ and ‘PS2’ expansions of
|
||||
‘!’ to the history number and ‘!!’ to ‘!’, and Bash performs
|
||||
parameter expansion on the values of ‘PS1’ and ‘PS2’ regardless of
|
||||
the setting of the ‘promptvars’ option.
|
||||
|
||||
30. The default history file is ‘~/.sh_history’ (this is the default
|
||||
29. The default history file is ‘~/.sh_history’ (this is the default
|
||||
value the shell assigns to ‘$HISTFILE’).
|
||||
|
||||
31. The ‘!’ character does not introduce history expansion within a
|
||||
30. The ‘!’ character does not introduce history expansion within a
|
||||
double-quoted string, even if the ‘histexpand’ option is enabled.
|
||||
|
||||
32. When printing shell function definitions (e.g., by ‘type’), Bash
|
||||
does not print the ‘function’ keyword.
|
||||
31. When printing shell function definitions (e.g., by ‘type’), Bash
|
||||
does not print the ‘function’ keyword unless necessary.
|
||||
|
||||
33. Non-interactive shells exit if a syntax error in an arithmetic
|
||||
32. Non-interactive shells exit if a syntax error in an arithmetic
|
||||
expansion results in an invalid expression.
|
||||
|
||||
34. Non-interactive shells exit if a parameter expansion error occurs.
|
||||
33. Non-interactive shells exit if a parameter expansion error occurs.
|
||||
|
||||
35. If a POSIX special builtin returns an error status, a
|
||||
34. 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.
|
||||
|
||||
36. A non-interactive shell exits with an error status if a variable
|
||||
35. 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.
|
||||
|
||||
37. A non-interactive shell exits with an error status if a variable
|
||||
36. 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,
|
||||
@@ -7727,155 +7739,155 @@ startup files.
|
||||
perform any further processing of the command in which the error
|
||||
occurred").
|
||||
|
||||
38. A non-interactive shell exits with an error status if the
|
||||
37. 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.
|
||||
|
||||
39. Non-interactive shells exit if FILENAME in ‘.’ FILENAME is not
|
||||
38. Non-interactive shells exit if FILENAME in ‘.’ FILENAME is not
|
||||
found.
|
||||
|
||||
40. Non-interactive shells exit if there is a syntax error in a script
|
||||
39. 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.
|
||||
|
||||
41. Non-interactive shells exit if the ‘export’, ‘readonly’ or ‘unset’
|
||||
40. Non-interactive shells exit if the ‘export’, ‘readonly’ or ‘unset’
|
||||
builtin commands get an argument that is not a valid identifier,
|
||||
and they are not operating on shell functions. These errors force
|
||||
an exit because these are special builtins.
|
||||
|
||||
42. Assignment statements preceding POSIX special builtins persist in
|
||||
41. Assignment statements preceding POSIX special builtins persist in
|
||||
the shell environment after the builtin completes.
|
||||
|
||||
43. The ‘command’ builtin does not prevent builtins that take
|
||||
42. The ‘command’ builtin does not prevent builtins that take
|
||||
assignment statements as arguments from expanding them as
|
||||
assignment statements; when not in POSIX mode, declaration commands
|
||||
lose their assignment statement expansion properties when preceded
|
||||
by ‘command’.
|
||||
|
||||
44. Enabling POSIX mode has the effect of setting the
|
||||
43. 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.
|
||||
|
||||
45. Enabling POSIX mode has the effect of setting the ‘shift_verbose’
|
||||
44. 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.
|
||||
|
||||
46. Enabling POSIX mode has the effect of setting the
|
||||
45. Enabling POSIX mode has the effect of setting the
|
||||
‘interactive_comments’ option (*note Comments::).
|
||||
|
||||
47. The ‘.’ and ‘source’ builtins do not search the current directory
|
||||
46. The ‘.’ and ‘source’ builtins do not search the current directory
|
||||
for the filename argument if it is not found by searching ‘PATH’.
|
||||
|
||||
48. When the ‘alias’ builtin displays alias definitions, it does not
|
||||
47. When the ‘alias’ builtin displays alias definitions, it does not
|
||||
display them with a leading ‘alias ’ unless the ‘-p’ option is
|
||||
supplied.
|
||||
|
||||
49. The ‘bg’ builtin uses the required format to describe each job
|
||||
48. 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.
|
||||
|
||||
50. When the ‘cd’ builtin is invoked in logical mode, and the pathname
|
||||
49. 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.
|
||||
|
||||
51. When the ‘cd’ builtin cannot change a directory because the length
|
||||
50. 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.
|
||||
|
||||
52. When the ‘xpg_echo’ option is enabled, Bash does not attempt to
|
||||
51. When the ‘xpg_echo’ option is enabled, Bash does not attempt to
|
||||
interpret any arguments to ‘echo’ as options. ‘echo’ displays each
|
||||
argument after converting escape sequences.
|
||||
|
||||
53. The ‘export’ and ‘readonly’ builtin commands display their output
|
||||
52. The ‘export’ and ‘readonly’ builtin commands display their output
|
||||
in the format required by POSIX.
|
||||
|
||||
54. When listing the history, the ‘fc’ builtin does not include an
|
||||
53. When listing the history, the ‘fc’ builtin does not include an
|
||||
indication of whether or not a history entry has been modified.
|
||||
|
||||
55. The default editor used by ‘fc’ is ‘ed’.
|
||||
54. The default editor used by ‘fc’ is ‘ed’.
|
||||
|
||||
56. ‘fc’ treats extra arguments as an error instead of ignoring them.
|
||||
55. ‘fc’ treats extra arguments as an error instead of ignoring them.
|
||||
|
||||
57. If there are too many arguments supplied to ‘fc -s’, ‘fc’ prints
|
||||
56. If there are too many arguments supplied to ‘fc -s’, ‘fc’ prints
|
||||
an error message and returns failure.
|
||||
|
||||
58. The output of ‘kill -l’ prints all the signal names on a single
|
||||
57. The output of ‘kill -l’ prints all the signal names on a single
|
||||
line, separated by spaces, without the ‘SIG’ prefix.
|
||||
|
||||
59. The ‘kill’ builtin does not accept signal names with a ‘SIG’
|
||||
58. The ‘kill’ builtin does not accept signal names with a ‘SIG’
|
||||
prefix.
|
||||
|
||||
60. The ‘printf’ builtin uses ‘double’ (via ‘strtod’) to convert
|
||||
59. 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.
|
||||
|
||||
61. The ‘pwd’ builtin verifies that the value it prints is the same as
|
||||
60. 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.
|
||||
|
||||
62. The ‘read’ builtin may be interrupted by a signal for which a trap
|
||||
61. 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.
|
||||
|
||||
63. When the ‘set’ builtin is invoked without options, it does not
|
||||
62. When the ‘set’ builtin is invoked without options, it does not
|
||||
display shell function names and definitions.
|
||||
|
||||
64. When the ‘set’ builtin is invoked without options, it displays
|
||||
63. 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.
|
||||
|
||||
65. The ‘test’ builtin compares strings using the current locale when
|
||||
64. The ‘test’ builtin compares strings using the current locale when
|
||||
evaluating the ‘<’ and ‘>’ binary operators.
|
||||
|
||||
66. The ‘test’ builtin's ‘-t’ unary primary requires an argument.
|
||||
65. 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.
|
||||
|
||||
67. The ‘trap’ builtin displays signal names without the leading
|
||||
66. The ‘trap’ builtin displays signal names without the leading
|
||||
‘SIG’.
|
||||
|
||||
68. The ‘trap’ builtin doesn't check the first argument for a possible
|
||||
67. 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.
|
||||
|
||||
69. ‘trap -p’ without arguments displays signals whose dispositions
|
||||
68. ‘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.
|
||||
|
||||
70. The ‘type’ and ‘command’ builtins will not report a non-executable
|
||||
69. 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’.
|
||||
|
||||
71. The ‘ulimit’ builtin uses a block size of 512 bytes for the ‘-c’
|
||||
70. The ‘ulimit’ builtin uses a block size of 512 bytes for the ‘-c’
|
||||
and ‘-f’ options.
|
||||
|
||||
72. The ‘unset’ builtin with the ‘-v’ option specified returns a fatal
|
||||
71. The ‘unset’ builtin with the ‘-v’ option specified returns a fatal
|
||||
error if it attempts to unset a ‘readonly’ or ‘non-unsettable’
|
||||
variable, which causes a non-interactive shell to exit.
|
||||
|
||||
73. When asked to unset a variable that appears in an assignment
|
||||
72. 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.
|
||||
|
||||
74. The arrival of ‘SIGCHLD’ when a trap is set on ‘SIGCHLD’ does not
|
||||
73. 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.
|
||||
|
||||
75. Bash removes an exited background process's status from the list
|
||||
74. Bash removes an exited background process's status from the list
|
||||
of such statuses after the ‘wait’ builtin returns it.
|
||||
|
||||
There is other POSIX behavior that Bash does not implement by default
|
||||
@@ -8768,9 +8780,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
|
||||
@@ -13489,88 +13501,88 @@ Node: Command Execution Environment133995
|
||||
Node: Environment137443
|
||||
Node: Exit Status139346
|
||||
Node: Signals141404
|
||||
Node: Shell Scripts145302
|
||||
Node: Shell Builtin Commands148600
|
||||
Node: Bourne Shell Builtins150711
|
||||
Node: Bash Builtins177261
|
||||
Node: Modifying Shell Behavior213709
|
||||
Node: The Set Builtin214051
|
||||
Node: The Shopt Builtin225987
|
||||
Node: Special Builtins243039
|
||||
Node: Shell Variables244028
|
||||
Node: Bourne Shell Variables244462
|
||||
Node: Bash Variables246970
|
||||
Node: Bash Features285279
|
||||
Node: Invoking Bash286293
|
||||
Node: Bash Startup Files292719
|
||||
Node: Interactive Shells298011
|
||||
Node: What is an Interactive Shell?298419
|
||||
Node: Is this Shell Interactive?299081
|
||||
Node: Interactive Shell Behavior299905
|
||||
Node: Bash Conditional Expressions303666
|
||||
Node: Shell Arithmetic308885
|
||||
Node: Aliases312214
|
||||
Node: Arrays315349
|
||||
Node: The Directory Stack322412
|
||||
Node: Directory Stack Builtins323209
|
||||
Node: Controlling the Prompt327654
|
||||
Node: The Restricted Shell330538
|
||||
Node: Bash POSIX Mode333420
|
||||
Node: Shell Compatibility Mode351749
|
||||
Node: Job Control360756
|
||||
Node: Job Control Basics361213
|
||||
Node: Job Control Builtins367491
|
||||
Node: Job Control Variables374173
|
||||
Node: Command Line Editing375404
|
||||
Node: Introduction and Notation377107
|
||||
Node: Readline Interaction379459
|
||||
Node: Readline Bare Essentials380647
|
||||
Node: Readline Movement Commands382455
|
||||
Node: Readline Killing Commands383451
|
||||
Node: Readline Arguments385474
|
||||
Node: Searching386531
|
||||
Node: Readline Init File388792
|
||||
Node: Readline Init File Syntax390096
|
||||
Node: Conditional Init Constructs416844
|
||||
Node: Sample Init File421229
|
||||
Node: Bindable Readline Commands424350
|
||||
Node: Commands For Moving425888
|
||||
Node: Commands For History428115
|
||||
Node: Commands For Text433368
|
||||
Node: Commands For Killing437493
|
||||
Node: Numeric Arguments440281
|
||||
Node: Commands For Completion441433
|
||||
Node: Keyboard Macros445933
|
||||
Node: Miscellaneous Commands446634
|
||||
Node: Readline vi Mode453187
|
||||
Node: Programmable Completion454164
|
||||
Node: Programmable Completion Builtins462210
|
||||
Node: A Programmable Completion Example473875
|
||||
Node: Using History Interactively479220
|
||||
Node: Bash History Facilities479901
|
||||
Node: Bash History Builtins483636
|
||||
Node: History Interaction490107
|
||||
Node: Event Designators495061
|
||||
Node: Word Designators496639
|
||||
Node: Modifiers498947
|
||||
Node: Installing Bash500888
|
||||
Node: Basic Installation502004
|
||||
Node: Compilers and Options505880
|
||||
Node: Compiling For Multiple Architectures506630
|
||||
Node: Installation Names508383
|
||||
Node: Specifying the System Type510617
|
||||
Node: Sharing Defaults511363
|
||||
Node: Operation Controls512077
|
||||
Node: Optional Features513096
|
||||
Node: Reporting Bugs525476
|
||||
Node: Major Differences From The Bourne Shell526834
|
||||
Node: GNU Free Documentation License548254
|
||||
Node: Indexes573431
|
||||
Node: Builtin Index573882
|
||||
Node: Reserved Word Index580980
|
||||
Node: Variable Index583425
|
||||
Node: Function Index600838
|
||||
Node: Concept Index614694
|
||||
Node: Shell Scripts146333
|
||||
Node: Shell Builtin Commands149631
|
||||
Node: Bourne Shell Builtins151742
|
||||
Node: Bash Builtins178292
|
||||
Node: Modifying Shell Behavior214740
|
||||
Node: The Set Builtin215082
|
||||
Node: The Shopt Builtin227018
|
||||
Node: Special Builtins244070
|
||||
Node: Shell Variables245059
|
||||
Node: Bourne Shell Variables245493
|
||||
Node: Bash Variables248001
|
||||
Node: Bash Features286310
|
||||
Node: Invoking Bash287324
|
||||
Node: Bash Startup Files293750
|
||||
Node: Interactive Shells299042
|
||||
Node: What is an Interactive Shell?299450
|
||||
Node: Is this Shell Interactive?300112
|
||||
Node: Interactive Shell Behavior300936
|
||||
Node: Bash Conditional Expressions304697
|
||||
Node: Shell Arithmetic309916
|
||||
Node: Aliases313245
|
||||
Node: Arrays316380
|
||||
Node: The Directory Stack323443
|
||||
Node: Directory Stack Builtins324240
|
||||
Node: Controlling the Prompt328685
|
||||
Node: The Restricted Shell331569
|
||||
Node: Bash POSIX Mode334451
|
||||
Node: Shell Compatibility Mode352513
|
||||
Node: Job Control361520
|
||||
Node: Job Control Basics361977
|
||||
Node: Job Control Builtins368255
|
||||
Node: Job Control Variables374937
|
||||
Node: Command Line Editing376168
|
||||
Node: Introduction and Notation377871
|
||||
Node: Readline Interaction380223
|
||||
Node: Readline Bare Essentials381411
|
||||
Node: Readline Movement Commands383219
|
||||
Node: Readline Killing Commands384215
|
||||
Node: Readline Arguments386238
|
||||
Node: Searching387295
|
||||
Node: Readline Init File389556
|
||||
Node: Readline Init File Syntax390860
|
||||
Node: Conditional Init Constructs417607
|
||||
Node: Sample Init File421992
|
||||
Node: Bindable Readline Commands425113
|
||||
Node: Commands For Moving426651
|
||||
Node: Commands For History428878
|
||||
Node: Commands For Text434131
|
||||
Node: Commands For Killing438256
|
||||
Node: Numeric Arguments441044
|
||||
Node: Commands For Completion442196
|
||||
Node: Keyboard Macros446696
|
||||
Node: Miscellaneous Commands447397
|
||||
Node: Readline vi Mode453950
|
||||
Node: Programmable Completion454927
|
||||
Node: Programmable Completion Builtins462973
|
||||
Node: A Programmable Completion Example474638
|
||||
Node: Using History Interactively479983
|
||||
Node: Bash History Facilities480664
|
||||
Node: Bash History Builtins484399
|
||||
Node: History Interaction490870
|
||||
Node: Event Designators495824
|
||||
Node: Word Designators497402
|
||||
Node: Modifiers499710
|
||||
Node: Installing Bash501651
|
||||
Node: Basic Installation502767
|
||||
Node: Compilers and Options506643
|
||||
Node: Compiling For Multiple Architectures507393
|
||||
Node: Installation Names509146
|
||||
Node: Specifying the System Type511380
|
||||
Node: Sharing Defaults512126
|
||||
Node: Operation Controls512840
|
||||
Node: Optional Features513859
|
||||
Node: Reporting Bugs526239
|
||||
Node: Major Differences From The Bourne Shell527597
|
||||
Node: GNU Free Documentation License549017
|
||||
Node: Indexes574194
|
||||
Node: Builtin Index574645
|
||||
Node: Reserved Word Index581743
|
||||
Node: Variable Index584188
|
||||
Node: Function Index601601
|
||||
Node: Concept Index615457
|
||||
|
||||
End Tag Table
|
||||
|
||||
|
||||
Reference in New Issue
Block a user