On Sun, Sep 19, 2021 at 02:29:57AM +0100, ropers wrote:
> I appreciate not everyone is as verbose as I can be, but your initial
> email was very terse. For example, when you say:
>
> > in emacs search-history mode, abort if ^@ is encountered
>
> is that the desired behaviour or the problem
I appreciate not everyone is as verbose as I can be, but your initial
email was very terse. For example, when you say:
> in emacs search-history mode, abort if ^@ is encountered
is that the desired behaviour or the problem behaviour?
>From testing, it seems like the current behaviour is that
Ping. Please don't be discouraged or scared just because it's a diff to ksh(1).
It really is rather simple.
Noone else ever ran into this ksh command line history search bug?
/Alexander
On September 14, 2021 12:17:22 AM GMT+02:00, Alexander Hall
wrote:
>in emacs search-history mode, abort if
in emacs search-history mode, abort if ^@ is encountered
This has been bugging me for ages, and I finally realized it was me
accidentally pressing Ctrl+, rendering ^@ (a.k.a '\0' or NUL)
Easily tested with: Ctrl+R Ctrl+ ...
Minimal investigation, for reference:
bash: misbehaves in a slightly
