Re: Bash history weirdness

2009-10-04 Thread John
On 3 Oct 2009 at 20:19, Wanna-Be Sys Admin wrote: > John wrote: >> If I do "history -w" then it writes the current history to >> ~/.bash_history as expected. >> >> But if I do "history -a" then ~/.bash_history doesn't get changed, and >> from the modification time it hasn't been touched at all. >

Re: Mailcheck and pseudo message in a mailbox

2009-10-04 Thread Chet Ramey
Yarda wrote: > With bash-4.0 the mailcheck behaviour is annoying when there is a pseudo > message in a mailbox, e.g.: It's unfortunate that the system's implementors chose a metadata format that is indistinguishable from a valid mail message. Since bash doesn't read the contents of a mail file at

Re: extglobs in case constructs

2009-10-04 Thread Chet Ramey
Martin von Gagern wrote: >> The reason that [[ conditional commands don't require extglob to be >> enabled while they're executed (and case commands do) lies in how the >> commands are defined to behave. case commands are defined by Posix: >> the pattern is always a Posix shell pattern, and any e

Re: possible write to an invalid address

2009-10-04 Thread Chet Ramey
Henning Garus wrote: > Bash Version: 4.0 > Patch Level: 33 > Release Status: release > > Description: > When bash_dequote_filename() is called with text ending with a > backslash and double quote as quote_char, it writes beyond the memory > allocated for ret, thus corrupting memory. Thank

Re: Completion: menu-complete from second TAB hit onwards

2009-10-04 Thread Chet Ramey
Julien Duval wrote: > Thanks for the quick reply Chet. > > I should have insisted on the fact that I don't want the first TAB to insert > a full match. The first TAB should only insert the longest common prefix > between all the possible completions (not a full match). A full match should > only b

Re: Bash history weirdness

2009-10-04 Thread Chet Ramey
John wrote: > Hi, > > Bash's history command is behaving oddly. > > If I do "history -w" then it writes the current history to > ~/.bash_history as expected. > > But if I do "history -a" then ~/.bash_history doesn't get changed, and > from the modification time it hasn't been touched at all. Lo

possible write to an invalid address

2009-10-04 Thread Henning Garus
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba