NetBSD-Bugs archive

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

Re: misc/52344: editline ^W mis-behaviour?

Yes, as everyone has pointed out, it was an error on *my* part wrt
what mode was being emulated, though Christos did find an opportunity
for a drive-by patch.

I was probably a bit expectant of an issue because of other occasional
shell issues in the course of its refactoring that I didn't look deep
enough before reporting.

My apologies, this can be closed.

On 6/26/17, Robert Elz <> wrote:
> The following reply was made to PR misc/52344; it has been noted by GNATS.
> From: Robert Elz <kre%munnari.OZ.AU@localhost>
> To:
> Cc:
> Subject: Re: misc/52344: editline ^W mis-behaviour?
> Date: Tue, 27 Jun 2017 04:28:18 +0700
>      Date:        Mon, 26 Jun 2017 19:45:00 +0000 (UTC)
>      From:        bch <>
>      Message-ID:  <>
>    =7C 	=5EW (control-w) appears to be working like =5EU, deleting entire =
>  line
>    =7C instead of expected single previous word
>  From this I am assuming you are in emacs mode (echo =24- should show 'E' =
>  amongst
>  other characters.)
>  In emacs mode, =5EW is bound to =22em-kill-region=22 (see editline(7)) an=
>  d
>  em-kill-region apparently deletes to the =22mark=22 which in your case I
>  assuming is being set at beginning of line (and I observed that too,
>  though I would normally never go near anything that even smelled of emacs=
>  ).
>  Again according to editline(7) the emacs mode equiv of =5EW in vi mode
>  (or when no line editing is enabled and the tty driver is doing it)
>  is Ctrl-Meta-H or Ctrl-Meta-? which I cannot test, as those combinations
>  do not make it to regular applications the way I have my X and window
>  manager configured.)
>  You could bind =5EW to ed-delete-word instead of em-kill-region for emacs=
>  mode, or you could do the sane thing and just switch to vi mode.
>  See editline(7) and editrc(5).
>  kre

Home | Main Index | Thread Index | Old Index