On Feb 10 2022, Chet Ramey wrote:
> On 2/10/22 9:53 AM, Andreas Schwab wrote:
>> On Jan 21 2022, Chet Ramey wrote:
>>
>>> i. The non-incremental history searches now leave the current history offset
>>> at the position of the last matching history entry, like incremental
>>> search.
>> That makes history-search-backward significantly less useful, because
>> you can no longer use yank-last-arg to copy arguments from the preceding
>> line.
>
> It makes previous-history, next-history, and operate-and-get-next work as
> they do with incremental searches, which is more in line with user
> expectations.
But it clobbers the matched history line, replacing it with the
uncompleted input.
$ HOME=$PWD bash --norc
bash-5.2$ history
1 history
bash-5.2$ echo 1
1
bash-5.2$ history
1 history
2 echo 1
3 history
bash-5.2$ echo 1 <-- type e <history-search-backward>
1
bash-5.2$ history
1 history
2 e
3 history
4 echo 1
5 history
bash-5.2$
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
