commit bash-20050915 snapshot

This commit is contained in:
Chet Ramey
2011-12-03 13:51:07 -05:00
parent a2e7f35864
commit 66e6d7cffd
14 changed files with 2948 additions and 1046 deletions
+31
View File
@@ -12087,3 +12087,34 @@ doc/bashref.texi
builtins/mkbuiltins.c
- change to not generate N_(""), because the translated empty string is
special to GNU gettext
9/13
----
lib/readline/complete.c
- a negative value for rl_completion_query_items means to not ask
lib/readline/doc/{{rltech,rluser}.texi,readline.3}
- documented new semantics for rl_completion_query_items/
completion-query-items
9/14
----
bashline.c
- bind M-TAB in emacs mode to dynamic-complete-history even if the
current binding is `tab-insert' (which is what it is by default),
not just if it's unbound
9/15
----
eval.c
- call QUIT before calling dispose_command on current_command after
the `exec_done' label. If we dispose current_command first, the
longjmp might restore the value of current_command after we've
disposed it, and the subsequent call to dispose_command from the
DISCARD case will free memory twice
9/16
----
lib/sh/strto[iu]max.c
- make sure the function being declared is not a cpp define before
defining it -- should fix problems on HP-UX
+31
View File
@@ -12081,3 +12081,34 @@ builtins/echo.def
doc/bashref.texi
- describe the --enable-strict-posix-default option to configure
9/10
----
builtins/mkbuiltins.c
- change to not generate N_(""), because the translated empty string is
special to GNU gettext
9/13
----
lib/readline/complete.c
- a negative value for rl_completion_query_items means to not ask
lib/readline/doc/{{rltech,rluser}.texi,readline.3}
- documented new semantics for rl_completion_query_items/
completion-query-items
9/14
----
bashline.c
- bind M-TAB in emacs mode to dynamic-complete-history even if the
current binding is `tab-insert' (which is what it is by default),
not just if it's unbound
9/15
----
eval.c
- call QUIT before calling dispose_command on current_command after
the `exec_done' label. If we dispose current_command first, the
longjmp might restore the value of current_command after we've
disposed it, and the subsequent call to dispose_command from the
DISCARD case will free memory twice