On 9/20/11 6:52 AM, gregrwm wrote:
>> The code has been this way for over 20 years, so this is a
>> very-infrequently-encountered problem. I will have to look at the startup
>> hook the command uses to see if I can fix it up there.
I fixed the problem, and the fix will be in the next version.
>
> OK, thanks for the clarification. I see the problem. It's an incorrect
>
> calculation of the `next history line' in operate_and_get_next() that
> mishandles this particular case.
>
> By default, bash limits the size of the history to 500 commands, which
> means you get the commands you execute
On 9/17/11 8:41 AM, gregrwm wrote:
>>> Repeat-By:
>>> rm $HISTFILE#start with no history file
>>> exec -cl bash --norc --noprofile#start with no history in memory
>>> pm=1.2.3.4 #do some commands
>>> sb='echo sudo -uboo'
>>> ssb="$sb
> > Repeat-By:
> > rm $HISTFILE #start with no history file
> > exec -cl bash --norc --noprofile #start with no history in memory
> > pm=1.2.3.4 #do some commands
> > sb='echo sudo -uboo'
> > ssb="$sb ssh -p1234 $pm cd boo;"
> > $ssb 'e
On 9/15/11 1:41 PM, gregrwm wrote:
> Bash Version: 4.1
> Patch Level: 2
> Release Status: release
>
> Description: ^O gets stuck if there's a bunch of history
> rpm -q bash #i have this problem on bash-4.1.2-8.el6.x86_64
> dpkg-query -W bash #and on 4.2-0ubuntu3
> echo $BASH_VERS
