Since upgrading to OS X 10.10 Yosemite and thus bash 3.2.53 use of the
PROMPT_COMMAND='history -a; history -n'
workaround to get a single ksh-style history causes the shell to become less
and less responsive until it permanently hangs.
The problem is somewhat intermitant in terms of how quickly
These are for:
bash --version
GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin14.0.0)
lldb backtrace:
(lldb) process attach --pid 5955
Process 5955 stopped
Executable module set to "/usr/local/bin/bash".
Architecture set to: x86_64h-apple-macosx.
(lldb) bt
* thread #1: tid = 0x169339, 0x00
Resend with missing stats for truss after ctrl-C
> On 4 Nov 2014, at 9:08 am, Graham Jones
> wrote:
>
> These are for:
> bash --version
> GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin14.0.0)
>
> lldb backtrace:
> (lldb) process attach --pid 5955
> Pro
/Users/graham/.bash_history
>
> cheers,
> pg
>
>
>
> On Tue, Nov 4, 2014 at 2:54 PM, Chet Ramey wrote:
>> On 11/3/14 5:08 PM, Graham Jones wrote:
>>> These are for:
>>> bash --version
>>> GNU bash, version 4.3.30(1)-release (x86_64-apple-darw
> On 5 Nov 2014, at 12:54 am, Chet Ramey wrote:
>
> On 11/3/14 5:08 PM, Graham Jones wrote:
>> These are for:
>> bash --version
>> GNU bash, version 4.3.30(1)-release (x86_64-apple-darwin14.0.0)
>
> This trace looks pretty reasonable. Maybe you could tempor
> 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
>
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
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 -
Guys thanks so much for taking this discussion further than just the reported
bug that prevented the existing workaround.
I’ve often considered putting this work in myself but wasn’t sure what the
reason was for this not being in bash already and if there was an architectural
difficulty with im
