Re: History search: wrong pos. after `Bksp` over typo

[Chet Ramey]

On 11/10/20 12:54 AM, Michael Allan wrote:
> Configuration Information [Automatically generated]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-pc-linux-gnu-gcc
> Compilation CFLAGS: -march=native -O2 -pipe -Wno-parentheses 
> -Wno-format-security
> uname output: Linux primeval 5.4.30-gentoo #33 SMP Wed Jul 29 00:03:46 EDT 
> 2020 x86_64 AMD Ryzen 7 3700X 8-Core Processor AuthenticAMD GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
> 
> Bash Version: 5.0
> Patch Level: 17
> Release Status: release
> 
> Description:
>     During history search, Bash allows one to correct the search term
>     by backspacing, e.g. after making a typo, but it fails to correct
>     the search position in response.
> 
>     A typo is like a ‘wrong turn at Albuquerque’, it can get one lost.
>     Backspacing and erasing part of the search term *should* take one
>     back to Albuquerque, but does not; while it corrects the search
>     term, it fails to correct the search position (inconsistency)
>     which leaves one lost.

Thanks for the suggestion. This is a request for an enhancement, since
readline has never worked like this. I'll consider it for a future
version.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/