Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Piotr Grzybowski
On Nov 6, 2014 3:25 AM, "Chet Ramey" wrote: > > On 11/4/14 5:16 PM, Piotr Grzybowski wrote: > > Chet: for reasons unexplained calls to read_history_range at [..] > > There is an issue with this particular, relatively infrequent, set of > circumstances [..] > Thanks a lot Chet, seems that this wa

Re: [PATCH] bracketed paste support

2014-11-05 Thread Daniel Colascione
On 11/06/2014 02:38 AM, Chet Ramey wrote: > On 11/5/14 9:02 PM, Daniel Colascione wrote: >> On 10/29/2014 08:49 PM, Chet Ramey wrote: On 10/27/14, 6:35 PM, Daniel Colascione wrote: > This patch adds support for "bracketed paste mode" to readline. In > this mode, readline instructs the

Re: [PATCH] bracketed paste support

2014-11-05 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/5/14 9:02 PM, Daniel Colascione wrote: > On 10/29/2014 08:49 PM, Chet Ramey wrote: >>> On 10/27/14, 6:35 PM, Daniel Colascione wrote: This patch adds support for "bracketed paste mode" to readline. In this mode, readline instructs the t

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Graham Jones
Thanks Chet. Couple of notes: 1) I’m not setting HISTFILESIZE, only HISTSIZE. HISTFILESIZE is getting set for me based on my choice of HISTSIZE (though I assume this is something that bash does that you know about). 2) As mentioned in the initial bug report, if I set PROMPT_COMMAND='history -

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Chet Ramey
On 11/5/14 8:39 PM, Graham Jones wrote: > Just out of curiosity, this mechanism is obviously something of a work > around to give bash a single shared history in the same style as ksh had. > Has there ever been any thought of providing a mechanism to support a > single history session in a more na

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Chet Ramey
On 11/4/14 5:16 PM, Piotr Grzybowski wrote: > Chet: for reasons unexplained calls to read_history_range at > > history.def:219 > 219 result = read_history_range (filename, history_lines_in_file, > -1); > > return more and more records (77824 is above my HISTFILESIZE): There is an iss

Re: [PATCH] bracketed paste support

2014-11-05 Thread Daniel Colascione
On 10/29/2014 08:49 PM, Chet Ramey wrote: >> On 10/27/14, 6:35 PM, Daniel Colascione wrote: >>> This patch adds support for "bracketed paste mode" to readline. In >>> this mode, readline instructs the terminal to wrap pasted strings in >>> special control sequences so that programs can distinguish

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Graham Jones
Just out of curiosity, this mechanism is obviously something of a work around to give bash a single shared history in the same style as ksh had. Has there ever been any thought of providing a mechanism to support a single history session in a more native way? I know that zsh has the setopt shar

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Graham Jones
> On 6 Nov 2014, at 9:11 am, Piotr Grzybowski wrote: > > On Wed, Nov 5, 2014 at 2:57 PM, Chet Ramey wrote: >> I still can't reproduce it on OS X 10.10: [..] > > not only I cannot reproduce it at the moment, but also I have reached > the following state (user: root): > > # cat .bash_history >

Re: Odd bash behaviour with time:

2014-11-05 Thread Piotr Grzybowski
On Tue, Nov 4, 2014 at 1:24 AM, Ángel González wrote: > > There are more syntax errors equivalent to the "time;" case: [..] I completely agree with Linda :) > time | foo this one can be got rid of by the following (it will make time | time | time | time; possible, very much like having spam-w

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Piotr Grzybowski
On Wed, Nov 5, 2014 at 2:57 PM, Chet Ramey wrote: > I still can't reproduce it on OS X 10.10: [..] not only I cannot reproduce it at the moment, but also I have reached the following state (user: root): # cat .bash_history ls -al #1415144153 ls -al .bash_history #1415144154 pwd #1415144159 rm .

Re: Shellshock-vulnerable version still most obvious on ftp.gnu.org

2014-11-05 Thread Chet Ramey
On 11/5/14, 7:35 AM, Ian Jackson wrote: > If you go to ftp://ftp.gnu.org/pub/gnu/bash/, the most obvious most > recent version of bash is this: > ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz > ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz.sig > The shellshock fix is hidden in a subdirectory:

Re: Shellshock-vulnerable version still most obvious on ftp.gnu.org

2014-11-05 Thread Greg Wooledge
On Wed, Nov 05, 2014 at 03:20:13PM +0100, Eric Blake wrote: > On 11/05/2014 01:35 PM, Ian Jackson wrote: > > Could there please be a new full tarball release of the patched > > version ? > > There has never been a full tarball release of any other official patch; There is a tarball of bash 3.2.48

Re: Shellshock-vulnerable version still most obvious on ftp.gnu.org

2014-11-05 Thread Eric Blake
On 11/05/2014 01:35 PM, Ian Jackson wrote: > If you go to ftp://ftp.gnu.org/pub/gnu/bash/, the most obvious most > recent version of bash is this: > ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz > ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz.sig > The shellshock fix is hidden in a subdirecto

Shellshock-vulnerable version still most obvious on ftp.gnu.org

2014-11-05 Thread Ian Jackson
If you go to ftp://ftp.gnu.org/pub/gnu/bash/, the most obvious most recent version of bash is this: ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz.sig The shellshock fix is hidden in a subdirectory: ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3-patches

Re: PROMPT_COMMAND='history -a; history -n' causes shell hang in OX 10.10 Yosemite / bash 3.2.53

2014-11-05 Thread Chet Ramey
On 11/4/14, 5:16 PM, Piotr Grzybowski wrote: > Chet: for reasons unexplained calls to read_history_range at > > history.def:219 > 219 result = read_history_range (filename, history_lines_in_file, > -1); > > return more and more records (77824 is above my HISTFILESIZE): > > 1: history