-This is the Bash FAQ, version 4.01, for Bash version 4.0.
+This is the Bash FAQ, version 4.13, for Bash version 4.3.
This document contains a set of frequently-asked questions concerning
Bash, the GNU Bourne-Again Shell. Bash is a freely-available command
Section B: The latest version
-B1) What's new in version 4.0?
-B2) Are there any user-visible incompatibilities between bash-4.0,
- bash-3.2, and bash-2.05b?
+B1) What's new in version 4.3?
+B2) Are there any user-visible incompatibilities between bash-4.3 and
+ previous bash versions?
Section C: Differences from other Unix shells
E13) Why does filename completion misbehave if a colon appears in the filename?
E14) Why does quoting the pattern argument to the regular expression matching
conditional operator (=~) cause matching to stop working?
+E15) Tell me more about the shell compatibility level.
Section F: Things to watch out for on certain Unix versions
A2) What's the latest version?
-The latest version is 4.0, first made available on 20 February, 2009.
+The latest version is 4.3, first made available on xx December, 2013.
A3) Where can I get it?
Bash is the GNU project's shell, and so is available from the
master GNU archive site, ftp.gnu.org, and its mirrors. The
latest version is also available for FTP from ftp.cwru.edu.
-The following URLs tell how to get version 4.0:
+The following URLs tell how to get version 4.3:
-ftp://ftp.gnu.org/pub/gnu/bash/bash-4.0.tar.gz
-ftp://ftp.cwru.edu/pub/bash/bash-4.0.tar.gz
+ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz
+ftp://ftp.cwru.edu/pub/bash/bash-4.3.tar.gz
Formatted versions of the documentation are available with the URLs:
-ftp://ftp.gnu.org/pub/gnu/bash/bash-doc-4.0.tar.gz
-ftp://ftp.cwru.edu/pub/bash/bash-doc-4.0.tar.gz
+ftp://ftp.gnu.org/pub/gnu/bash/bash-doc-4.3.tar.gz
+ftp://ftp.cwru.edu/pub/bash/bash-doc-4.3.tar.gz
Any patches for the current version are available with the URL:
-ftp://ftp.cwru.edu/pub/bash/bash-4.0-patches/
+ftp://ftp.cwru.edu/pub/bash/bash-4.3-patches/
A4) On what machines will bash run?
Cygnus originally ported bash-1.14.7, and that port was part of their
early GNU-Win32 (the original name) releases. Cygnus has also done
-ports of bash-2.05b and bash-3.2 to the CYGWIN environment, and both
+ports of bash-3.2 and bash-4.0 to the CYGWIN environment, and both
are available as part of their current release.
Bash-2.05b and later versions should require no local Cygnus changes to
Bash-3.0 compiles and runs with no modifications under Microsoft's Services
for Unix (SFU), once known as Interix. I do not anticipate any problems
-with building bash-4.0, but will gladly accept any patches that are needed.
+with building bash-4.2 and later, but will gladly accept any patches that
+are needed.
A6) How can I build bash with gcc?
Section B: The latest version
-B1) What's new in version 4.0?
+B1) What's new in version 4.3?
-Bash-4.0 is the fourth major release of bash. There are numerous new features,
-some experimental. Depending on community reception, the experimental
-features will evolve.
+Bash-4.3 is the third revision to the fourth major release of bash.
-Bash-4.0 contains the following new features (see the manual page for
-complete descriptions and the CHANGES and NEWS files in the bash-4.0
+Bash-4.3 contains the following new features (see the manual page for
+complete descriptions and the CHANGES and NEWS files in the bash-4.3
distribution):
+o The `helptopic' completion action now maps to all the help topics, not just
+ the shell builtins.
+
+o The `help' builtin no longer does prefix substring matching first, so
+ `help read' does not match `readonly', but will do it if exact string
+ matching fails.
+
+o The shell can be compiled to not display a message about processes that
+ terminate due to SIGTERM.
+
+o Non-interactive shells now react to the setting of checkwinsize and set
+ LINES and COLUMNS after a foreground job exits.
+
+o There is a new shell option, `globasciiranges', which, when set to on,
+ forces globbing range comparisons to use character ordering as if they
+ were run in the C locale.
+
+o There is a new shell option, `direxpand', which makes filename completion
+ expand variables in directory names in the way bash-4.1 did.
+
+o In Posix mode, the `command' builtin does not change whether or not a
+ builtin it shadows is treated as an assignment builtin.
+
+o The `return' and `exit' builtins accept negative exit status arguments.
+
+o The word completion code checks whether or not a filename containing a
+ shell variable expands to a directory name and appends `/' to the word
+ as appropriate. The same code expands shell variables in command names
+ when performing command completion.
+
+o In Posix mode, it is now an error to attempt to define a shell function
+ with the same name as a Posix special builtin.
+
+o When compiled for strict Posix conformance, history expansion is disabled
+ by default.
+
+o The history expansion character (!) does not cause history expansion when
+ followed by the closing quote in a double-quoted string.
+
+o `complete' and its siblings compgen/compopt now takes a new `-o noquote'
+ option to inhibit quoting of the completions.
+
+o Setting HISTSIZE to a value less than zero causes the history list to be
+ unlimited (setting it 0 zero disables the history list).
+
+o Setting HISTFILESIZE to a value less than zero causes the history file size
+ to be unlimited (setting it to 0 causes the history file to be truncated
+ to zero size).
+
+o The `read' builtin now skips NUL bytes in the input.
+
+o There is a new `bind -X' option to print all key sequences bound to Unix
+ commands.
+
+o When in Posix mode, `read' is interruptible by a trapped signal. After
+ running the trap handler, read returns 128+signal and throws away any
+ partially-read input.
+
+o The command completion code skips whitespace and assignment statements
+ before looking for the command name word to be completed.
+
+o The build process has a new mechanism for constructing separate help files
+ that better reflects the current set of compilation options.
+
+o The -nt and -ot options to test now work with files with nanosecond
+ timestamp resolution.
+
+o The shell saves the command history in any shell for which history is
+ enabled and HISTFILE is set, not just interactive shells.
+
+o The shell has `nameref' variables and new -n(/+n) options to declare and
+ unset to use them, and a `test -R' option to test for them.
+
+o The shell now allows assigning, referencing, and unsetting elements of
+ indexed arrays using negative subscripts (a[-1]=2, echo ${a[-1]}) which
+ count back from the last element of the array.
+
+o The {x}<word redirection feature now allows words like {array[ind]} and
+ can use variables with special meanings to the shell (e.g., BASH_XTRACEFD).
+
+o There is a new CHILD_MAX special shell variable; its value controls the
+ number of exited child statues the shell remembers.
+
+o There is a new configuration option (--enable-direxpand-default) that
+ causes the `direxpand' shell option to be enabled by default.
+
+o Bash does not do anything special to ensure that the file descriptor
+ assigned to X in {x}<foo remains open after the block containing it
+ completes.
+
+o The `wait' builtin has a new `-n' option to wait for the next child to
+ change status.
+
+o The `printf' %(...)T format specifier now uses the current time if no
+ argument is supplied.
+
+o There is a new variable, BASH_COMPAT, that controls the current shell
+ compatibility level.
+
+o The `popd' builtin now treats additional arguments as errors.
+
+o The brace expansion code now treats a failed sequence expansion as a
+ simple string and will continue to expand brace terms in the remainder
+ of the word.
+
+o Shells started to run process substitutions now run any trap set on EXIT.
+
+o The fc builtin now interprets -0 as the current command line.
+
+o Completing directory names containing shell variables now adds a trailing
+ slash if the expanded result is a directory.
+
+A short feature history dating back to Bash-2.0:
+
+Bash-4.2 contained the following new features:
+
+o `exec -a foo' now sets $0 to `foo' in an executable shell script without a
+ leading #!.
+
+o Subshells begun to execute command substitutions or run shell functions or
+ builtins in subshells do not reset trap strings until a new trap is
+ specified. This allows $(trap) to display the caller's traps and the
+ trap strings to persist until a new trap is set.
+
+o `trap -p' will now show signals ignored at shell startup, though their
+ disposition still cannot be modified.
+
+o $'...', echo, and printf understand \uXXXX and \UXXXXXXXX escape sequences.
+
+o declare/typeset has a new `-g' option, which creates variables in the
+ global scope even when run in a shell function.
+
+o test/[/[[ have a new -v variable unary operator, which returns success if
+ `variable' has been set.
+
+o Posix parsing changes to allow `! time command' and multiple consecutive
+ instances of `!' (which toggle) and `time' (which have no cumulative
+ effect).
+
+o Posix change to allow `time' as a command by itself to print the elapsed
+ user, system, and real times for the shell and its children.
+
+o $((...)) is always parsed as an arithmetic expansion first, instead of as
+ a potential nested command substitution, as Posix requires.
+
+o A new FUNCNEST variable to allow the user to control the maximum shell
+ function nesting (recursive execution) level.
+
+o The mapfile builtin now supplies a third argument to the callback command:
+ the line about to be assigned to the supplied array index.
+
+o The printf builtin has as new %(fmt)T specifier, which allows time values
+ to use strftime-like formatting.
+
+o There is a new `compat41' shell option.
+
+o The cd builtin has a new Posix-mandated `-e' option.
+
+o Negative subscripts to indexed arrays, previously errors, now are treated
+ as offsets from the maximum assigned index + 1.
+
+o Negative length specifications in the ${var:offset:length} expansion,
+ previously errors, are now treated as offsets from the end of the variable.
+
+o Parsing change to allow `time -p --'.
+
+o Posix-mode parsing change to not recognize `time' as a keyword if the
+ following token begins with a `-'. This means no more Posix-mode
+ `time -p'. Posix interpretation 267.
+
+o There is a new `lastpipe' shell option that runs the last command of a
+ pipeline in the current shell context. The lastpipe option has no
+ effect if job control is enabled.
+
+o History expansion no longer expands the `$!' variable expansion.
+
+o Posix mode shells no longer exit if a variable assignment error occurs
+ with an assignment preceding a command that is not a special builtin.
+
+o Non-interactive mode shells exit if -u is enabled an an attempt is made
+ to use an unset variable with the % or # expansions, the `//', `^', or
+ `,' expansions, or the parameter length expansion.
+
+o Posix-mode shells use the argument passed to `.' as-is if a $PATH search
+ fails, effectively searching the current directory. Posix-2008 change.
+
+A short feature history dating back to Bash-2.0:
+
+Bash-4.1 contained the following new features:
+
+o Here-documents within $(...) command substitutions may once more be
+ delimited by the closing right paren, instead of requiring a newline.
+
+o Bash's file status checks (executable, readable, etc.) now take file
+ system ACLs into account on file systems that support them.
+
+o Bash now passes environment variables with names that are not valid
+ shell variable names through into the environment passed to child
+ processes.
+
+o The `execute-unix-command' readline function now attempts to clear and
+ reuse the current line rather than move to a new one after the command
+ executes.
+
+o `printf -v' can now assign values to array indices.
+
+o New `complete -E' and `compopt -E' options that work on the "empty"
+ completion: completion attempted on an empty command line.
+
+o New complete/compgen/compopt -D option to define a `default' completion:
+ a completion to be invoked on command for which no completion has been
+ defined. If this function returns 124, programmable completion is
+ attempted again, allowing a user to dynamically build a set of completions
+ as completion is attempted by having the default completion function
+ install individual completion functions each time it is invoked.
+
+o When displaying associative arrays, subscripts are now quoted.
+
+o Changes to dabbrev-expand to make it more `emacs-like': no space appended
+ after matches, completions are not sorted, and most recent history entries
+ are presented first.
+
+o The [[ and (( commands are now subject to the setting of `set -e' and the
+ ERR trap.
+
+o The source/. builtin now removes NUL bytes from the file before attempting
+ to parse commands.
+
+o There is a new configuration option (in config-top.h) that forces bash to
+ forward all history entries to syslog.
+
+o A new variable $BASHOPTS to export shell options settable using `shopt' to
+ child processes.
+
+o There is a new confgure option that forces the extglob option to be
+ enabled by default.
+
+o New variable $BASH_XTRACEFD; when set to an integer bash will write xtrace
+ output to that file descriptor.
+
+o If the optional left-hand-side of a redirection is of the form {var}, the
+ shell assigns the file descriptor used to $var or uses $var as the file
+ descriptor to move or close, depending on the redirection operator.
+
+o The < and > operators to the [[ conditional command now do string
+ comparison according to the current locale.
+
+o Programmable completion now uses the completion for `b' instead of `a'
+ when completion is attempted on a line like: a $(b c.
+
+o Force extglob on temporarily when parsing the pattern argument to
+ the == and != operators to the [[ command, for compatibility.
+
+o Changed the behavior of interrupting the wait builtin when a SIGCHLD is
+ received and a trap on SIGCHLD is set to be Posix-mode only.
+
+o The read builtin has a new `-N nchars' option, which reads exactly NCHARS
+ characters, ignoring delimiters like newline.
+
+o The mapfile/readarray builtin no longer stores the commands it invokes via
+ callbacks in the history list.
+
+o There is a new `compat40' shopt option.
+
+o The < and > operators to [[ do string comparisons using the current locale
+ only if the compatibility level is greater than 40 (set to 41 by default).
+
+o New bindable readline function: menu-complete-backward.
+
+o In the readline vi-mode insertion keymap, C-n is now bound to menu-complete
+ by default, and C-p to menu-complete-backward.
+
+o When in readline vi command mode, repeatedly hitting ESC now does nothing,
+ even when ESC introduces a bound key sequence. This is closer to how
+ historical vi behaves.
+
+o New bindable readline function: skip-csi-sequence. Can be used as a
+ default to consume key sequences generated by keys like Home and End
+ without having to bind all keys.
+
+o New bindable readline variable: skip-completed-text, active when
+ completing in the middle of a word. If enabled, it means that characters
+ in the completion that match characters in the remainder of the word are
+ "skipped" rather than inserted into the line.
+
+o The pre-readline-6.0 version of menu completion is available as
+ "old-menu-complete" for users who do not like the readline-6.0 version.
+
+o New bindable readline variable: echo-control-characters. If enabled, and
+ the tty ECHOCTL bit is set, controls the echoing of characters
+ corresponding to keyboard-generated signals.
+
+o New bindable readline variable: enable-meta-key. Controls whether or not
+ readline sends the smm/rmm sequences if the terminal indicates it has a
+ meta key that enables eight-bit characters.
+
+Bash-4.0 contained the following new features:
+
o When using substring expansion on the positional parameters, a starting
index of 0 now causes $0 to be prefixed to the list.
which kill words backward and forward, but use the same word boundaries
as shell-forward-word and shell-backward-word.
-A short feature history dating from Bash-2.0:
-
Bash-3.2 contained the following new features:
o Bash-3.2 now checks shell scripts for NUL characters rather than non-printing
lots of code now smaller and faster
test suite greatly expanded
-B2) Are there any user-visible incompatibilities between bash-4.0, bash-3.2,
- and bash-2.05b?
+B2) Are there any user-visible incompatibilities between bash-4.3 and
+ previous bash versions?
-There are a few incompatibilities between version 4.0 and version 3.2.
-They are detailed in the file COMPAT in the bash distribution. That file
-is not meant to be all-encompassing; send mail to bash-maintainers@gnu.org
-if if you find something that's not mentioned there.
+There are a few incompatibilities between version 4.3 and previous
+versions. They are detailed in the file COMPAT in the bash distribution.
+That file is not meant to be all-encompassing; send mail to
+bash-maintainers@gnu.org (or bug-bash@gnu.org if you would like
+community discussion) if you find something that's not mentioned there.
Section C: Differences from other Unix shells
HISTFILESIZE, HISTCONTROL, HISTIGNORE, GLOBIGNORE, GROUPS,
PROMPT_COMMAND, FCEDIT, FIGNORE, IGNOREEOF, INPUTRC,
SHELLOPTS, OPTERR, HOSTFILE, TMOUT, FUNCNAME, histchars,
- auto_resume, PROMPT_DIRTRIM
+ auto_resume, PROMPT_DIRTRIM, BASHOPTS, BASH_XTRACEFD
DEBUG trap
ERR trap
variable arrays with new compound assignment syntax
auto-export of variables in initial environment
command search finds functions before builtins
bash return builtin will exit a file sourced with `.'
- builtins: cd -/-L/-P, exec -l/-c/-a, echo -e/-E, hash -d/-l/-p/-t.
+ builtins: cd -/-L/-P/-@, exec -l/-c/-a, echo -e/-E, hash -d/-l/-p/-t.
export -n/-f/-p/name=value, pwd -L/-P,
- read -e/-p/-a/-t/-n/-d/-s/-u/-i,
+ read -e/-p/-a/-t/-n/-d/-s/-u/-i/-N,
readonly -a/-f/name=value, trap -l, set +o,
set -b/-m/-o option/-h/-p/-B/-C/-H/-P,
- unset -f/-v, ulimit -i/-m/-p/-q/-u/-x,
+ unset -f/-n/-v, ulimit -i/-m/-p/-q/-u/-x,
type -a/-p/-t/-f/-P, suspend -f, kill -n,
- test -o optname/s1 == s2/s1 < s2/s1 > s2/-nt/-ot/-ef/-O/-G/-S
+ test -o optname/s1 == s2/s1 < s2/s1 > s2/-nt/-ot/-ef/-O/-G/-S/-R
bash reads ~/.bashrc for interactive shells, $ENV for non-interactive
bash restricted shell mode is more extensive
bash allows functions and variables with the same name
case-modifying word expansions and variable attributes
associative arrays
coprocesses using the `coproc' reserved word and variables
+ shell assignment of a file descriptor used in a redirection to a variable
Things sh has that bash does not:
uses variable SHACCT to do shell accounting
builtins: bind, builtin, command, declare, dirs, echo -e/-E, enable,
exec -l/-c/-a, fc -s, export -n/-f/-p, hash, help, history,
jobs -x/-r/-s, kill -s/-n/-l, local, logout, popd, pushd,
- read -e/-p/-a/-t/-n/-d/-s, readonly -a/-n/-f/-p,
+ read -e/-p/-a/-t/-n/-d/-s/-N, readonly -a/-n/-f/-p,
set -o braceexpand/-o histexpand/-o interactive-comments/
-o notify/-o physical/-o posix/-o hashall/-o onecmd/
-h/-B/-C/-b/-H/-P, set +o, suspend, trap -l, type,
case-modifying word expansions and variable attributes
associative arrays
coprocesses using the `coproc' reserved word and variables
+ shell assignment of a file descriptor used in a redirection to a variable
Things ksh88 has or uses that bash does not:
tracked aliases (alias -t)
C3) Which new features in ksh-93 are not in bash, and which are?
-This list is current through ksh93t (11/04/2008)
+This list is current through ksh93v (10/08/2013)
-New things in ksh-93 not in bash-4.0:
- floating point arithmetic and variables
- math library functions
+New things in ksh-93 not in bash-4.3:
+ floating point arithmetic, variables, and constants
+ math library functions, including user-defined math functions
${!name[sub]} name of subscript for associative array
`.' is allowed in variable names to create a hierarchical namespace
more extensive compound assignment syntax
discipline functions
KEYBD trap
variables: .sh.edchar, .sh.edmode, .sh.edcol, .sh.edtext, .sh.version,
- .sh.name, .sh.subscript, .sh.value, .sh.match, HISTEDIT
+ .sh.name, .sh.subscript, .sh.value, .sh.match, HISTEDIT,
+ .sh.sig, .sh.stats, .sh.siginfo, .sh.pwdfd, .sh.op_astbin,
+ .sh.pool
backreferences in pattern matching (\N)
`&' operator in pattern lists for matching (match all instead of any)
exit statuses between 0 and 255
no scoping for local variables in `POSIX' functions
$'' \C[.collating-element.] escape sequence
-C/-I invocation options
- print -f (bash uses printf)
+ print -f (bash uses printf) and rest of print builtin options
+ printf %(type)q, %#q
`fc' has been renamed to `hist'
`.' can execute shell functions
getopts -a
- printf %B, %H, %P, %R, %T, %Z modifiers, output base for %d, `=' flag
- read -N (read -n differs, too)/-v
+ printf %B, %H, %P, %R, %Z modifiers, output base for %d, `=' flag
+ read -n/-N differ/-v/-S
set -o showme/-o multiline (bash default)
+ set -K
+ kill -Q/-q/-L
+ trap -a
`sleep' and `getconf' builtins (bash has loadable versions)
- typeset -n and `nameref' variables
- typeset -C/-S/-T/-X/-h/-s
+ [[ -R name ]] (checks whether or not name is a nameref)
+ typeset -C/-S/-T/-X/-h/-s/-c/-M
experimental `type' definitions (a la typedef) using typeset
- negative subscripts for indexed array variables
array expansions ${array[sub1..sub2]} and ${!array[sub1..sub2]}
associative array assignments using `;' as element separator
command substitution $(n<#) expands to current byte offset for fd N
new '${ ' form of command substitution, executed in current shell
- new >;/<#pat/<##pat/<#/># redirections
- redirection operators preceded with {varname} to store fd number in varname
+ new >;/<>;/<#pat/<##pat/<#/># redirections
brace expansion printf-like formats
+ CHLD trap triggered by SIGSTOP and SIGCONT
+ ~{fd} expansion, which replaces fd with the corresponding path name
+ $"string" expanded when referenced rather than when first parsed
+ job "pools", which allow a collection of jobs to be managed as a unit
-New things in ksh-93 present in bash-4.0:
+New things in ksh-93 present in bash-4.3:
associative arrays
[n]<&word- and [n]>&word- redirections (combination dup and close)
for (( expr1; expr2; expr3 )) ; do list; done - arithmetic for command
expansions: ${!param}, ${param:offset[:len]}, ${param/pat[/str]},
${!param*}
compound array assignment
+ negative subscripts for indexed array variables
the `!' reserved word
loadable builtins -- but ksh uses `builtin' while bash uses `enable'
new $'...' and $"..." quoting
`command', `builtin', `disown' builtins
echo -e
exec -c/-a
+ printf %T modifier
read -A (bash uses read -a)
read -t/-d
trap -p
the `;&' case statement "fallthrough" pattern list terminator
csh-style history expansion and set -H
negative offsets in ${param:offset:length}
+ redirection operators preceded with {varname} to store fd number in varname
+ DEBUG can force skipping following command
+ [[ -v var ]] operator (checks whether or not var is set)
+ typeset -n and `nameref' variables
+ process substitutions work without /dev/fd
Section D: Why does bash do some things differently than other Unix shells?
bash reverts to the bash-3.1 behavior with respect to quoting the rhs of
the =~ operator.
+E15) Tell me more about the shell compatibility level.
+
+Bash-4.0 introduced the concept of a `shell compatibility level', specified
+as a set of options to the shopt builtin (compat31, compat32, compat40 at
+this writing). There is only one current compatibility level -- each
+option is mutually exclusive. This list does not mention behavior that is
+standard for a particular version (e.g., setting compat32 means that quoting
+the rhs of the regexp matching operator quotes special regexp characters in
+the word, which is default behavior in bash-3.2 and above).
+
+compat31 set
+ - the < and > operators to the [[ command do not consider the current
+ locale when comparing strings
+ - quoting the rhs of the regexp matching operator (=~) has no
+ special effect
+
+compat32 set
+ - the < and > operators to the [[ command do not consider the current
+ locale when comparing strings
+
+compat40 set
+ - the < and > operators to the [[ command do not consider the current
+ locale when comparing strings
+ - interrupting a command list such as "a ; b ; c" causes the execution
+ of the entire list to be aborted (in versions before bash-4.0,
+ interrupting one command in a list caused the next to be executed)
+
+compat41 set
+ - interrupting a command list such as "a ; b ; c" causes the execution
+ of the entire list to be aborted (in versions before bash-4.1,
+ interrupting one command in a list caused the next to be executed)
+ - when in posix mode, single quotes in the `word' portion of a
+ double-quoted parameter expansion define a new quoting context and
+ are treated specially
+
+compat42 set
+ - the replacement string in double-quoted pattern substitution is not
+ run through quote removal, as in previous versions
+
Section F: Things to watch out for on certain Unix versions
F1) Why can't I use command line editing in my `cmdtool'?
does the same thing.
This is not the same thing as ksh93 `nameref' variables, though the syntax
-is similar. I may add namerefs in a future bash version.
+is similar. Namerefs are available bash version 4.3, and work as in ksh93.
G4) How can I make the bash `time' reserved word print timing output that
looks like the output from my system's /usr/bin/time?
a bash programmer's guide with a chapter on creating loadable builtins
a better loadable interface to perl with access to the shell builtins and
variables (contributions gratefully accepted)
-ksh93-like `nameref' variables
ksh93-like `xx.yy' variables (including some of the .sh.* variables) and
associated disipline functions
Some of the new ksh93 pattern matching operators, like backreferencing
H5) When will the next release appear?
-The next version will appear sometime in 2009. Never make predictions.
+The next version will appear sometime in 2015. Never make predictions.
-This document is Copyright 1995-2009 by Chester Ramey.
+This document is Copyright 1995-2014 by Chester Ramey.
Permission is hereby granted, without written agreement and
without license or royalty fees, to use, copy, and distribute
projects / platform / upstream / bash.git / blobdiff