bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bash 5.0.2(1) multiline command in history bug


From: Jason Vas Dias
Subject: Re: bash 5.0.2(1) multiline command in history bug
Date: Wed, 6 Feb 2019 00:46:30 +0000

Thank you, but it definitely happens in the up-to-date MacPorts
bash-5.0.2(1) distribution,
I'll try looking at their patches, building a completely unpatched 5.0.2, and
contact the MacPorts developers to let them know if it is a problem with their
patches. It uses Apple's EditLine, not readline, which could be something to do
with it.
Thanks & Best Regards,
Jason


On 04/02/2019, Chet Ramey <address@hidden> wrote:
> On 2/4/19 3:22 AM, Jason Vas Dias wrote:
>> Good day -
>>
>>   Under bash 4.4.23, with emacs history editing enabled, I can do:
>>    $ echo '1
>>     > 2
>>     > 3
>>     > '
>>     1
>>     2
>>     3
>>    $
>>    and I can then press the <UP-ARROW> (move-up / history-previous) key,
>>    and the same command, including embedded new lines in the arguments,
>>    is echoed back to me, and I can press <RETURN> to repeat exactly that
>>    command (scroll up in history and repeat last command).
>>
>>    Now, with bash-5.0.2,  this capability is removed: scrolling up in
>> the history,
>>    if the previous command had a multi-line argument, shows the multiline
>>    argument folded, like:
>>     $ echo '1 2 3 '
>
> I can't reproduce this. I get:
>
> $ echo $BASH_VERSION
> 5.0.2(2)-release
> $ echo '1
>> 2
>> 3'
> 1
> 2
> 3
>                       [C-P here]
> $ echo '1
> 2
> 3'
>
>
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    address@hidden    http://tiswww.cwru.edu/~chet/
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]