diff options
author | Chet Ramey <chet.ramey@case.edu> | 2020-10-05 18:18:34 -0400 |
---|---|---|
committer | Chet Ramey <chet.ramey@case.edu> | 2020-10-05 18:18:34 -0400 |
commit | 5f2b5d79e0c0dd8f29e1d8e798675e33afbeda37 (patch) | |
tree | 277bdd6f7a4458806d9c02010c3e25797209515b /CWRU | |
parent | 3eb0018e75b74bb886df7fba4b1712529ce7258f (diff) | |
download | bash-5f2b5d79e0c0dd8f29e1d8e798675e33afbeda37.tar.gz |
Bash-5.1-rc1 releasebash-5.1-rc1
Diffstat (limited to 'CWRU')
-rw-r--r-- | CWRU/changelog | 76 |
1 files changed, 76 insertions, 0 deletions
diff --git a/CWRU/changelog b/CWRU/changelog index 7ce16461..967d0cc4 100644 --- a/CWRU/changelog +++ b/CWRU/changelog @@ -8977,3 +8977,79 @@ eval.c This protects against a command from PROMPT_COMMAND[n] unsetting the corresponding element of PROMPT_COMMAND. From a report from Koichi Murase <myoga.murase@gmail.com> + + 9/7 + --- +[bash-5.1-beta frozen] + + 9/8 + --- +lib/readline/display.c + - _rl_update_final: don't bother doing anything if the line structures + have not been initialized. Report and fix from gary@catalyst.net.nz + +variables.c + - get_histcmd: perform the same adjustment as in prompt_history_number; + make sure to subtract one if we're doing this while executing a + command that has already been saved to the history list. Inspired + by a report from L A Walsh <bash@tlinx.org> + + 9/14 + ---- +aclocal.m4 + - BASH_STRUCT_WEXITSTATUS_OFFSET: fix typo in loop condition reported + by Andreas K. Hüttel <dilfridge@gentoo.org> + +syntax.h + - slashify_in_here_document: restore previous value that doesn't + include double quote, since it's only special in certain cases + +subst.c + - expand_word_internal: when processing backslash-double quote inside + a ${...} construct inside a here documemt, treat it the same as if + it were double-quoted, as posix says. Fixes report from + Andreas Schwab <schwab@linux-m68k.org> + + 9/15 + ---- +support/signames.c + - added a number of more esoteric signal names from AIX and Solaris + +parse.y + - report_syntax_error: make sure that the exit status is only set to + one of the special builtin exit statuses if we are really executing + a builtin here, not just if parse_and_execute_level > 0. Reported by + Rob Landley <rob@landley.net> + +execute_cmd.c + - EX_BADSYNTAX: make sure that gets translated into EX_BADUSAGE (2) + - execute_simple_command: if a function returns a value greater than + EX_SHERRBASE, use builtin_status to translate it, as if a builtin + were being executed + - builtin_status: make sure a status > EX_SHERRBASE gets translated to + EXECUTION_FAILURE + + 9/21 + ---- +subst.c + - process_substitute: set up input from /dev/null (standard for an + asynchronous process) only if the shell is interactive and reading + input from the terminal. This allows scripts to use process + substitution to filter stdin. From a report from + Andreas Schwab <schwab@linux-m68k.org> + + 9/23 + ---- +doc/{bash.1,bashref.texi} + - ENV: a couple of changes clarifying that it's only used when an + interactive shell is started in posix mode. Report from + Reuben Thomas <rrt@sc3d.org> + +examples/loadables/asort.c + - asort: loadable builtin to sort an array. Contributed by + Geir Hauge <geir.hauge@gmail.com> + + 10/1 + ---- + +[bash-5.1-beta frozen] |