Re: ctrl-w oddity on bash-4.4

2017-10-26 Thread Chet Ramey
On 10/26/17 5:30 PM, Robert Elz wrote: > I should have also said that's there's no requirement (that I can see > anyway) that vi mode in readline be the same as vi. There isn't, and readline's vi mode doesn't attempt it. It only tries to implement what Posix defines as part of the `sh'

Re: ctrl-w oddity on bash-4.4

2017-10-26 Thread Chet Ramey
On 10/26/17 5:20 PM, Robert Elz wrote: > Date:Thu, 26 Oct 2017 10:04:54 -0400 > From:Chet Ramey > Message-ID: > > | Posix doesn't make that distinction. > > Actually, it does, > > Input

Re: ctrl-w oddity on bash-4.4

2017-10-26 Thread Robert Elz
I should have also said that's there's no requirement (that I can see anyway) that vi mode in readline be the same as vi. In fact, it obviously cannot be, it is just an editing mode that is somewhat similar to vi. There are going to be things missing (clearly there's no way, and no need, to

Re: ctrl-w oddity on bash-4.4

2017-10-26 Thread Robert Elz
Date:Thu, 26 Oct 2017 10:04:54 -0400 From:Chet Ramey Message-ID: | Posix doesn't make that distinction. Actually, it does, Input Mode Commands in vi In text input mode, the

Re: ctrl-w oddity on bash-4.4

2017-10-26 Thread Chet Ramey
On 10/26/17 12:21 AM, Robert Elz wrote: > Date:Wed, 25 Oct 2017 10:45:11 -0400 > From:Chet Ramey > Message-ID: <6751ad10-cccb-0467-a751-c5be8e745...@case.edu> > > | If you read the discussion in the thread I pointed to last night, `real' > |

Re: ctrl-w oddity on bash-4.4

2017-10-25 Thread Robert Elz
Date:Wed, 25 Oct 2017 10:45:11 -0400 From:Chet Ramey Message-ID: <6751ad10-cccb-0467-a751-c5be8e745...@case.edu> | If you read the discussion in the thread I pointed to last night, `real' | vi supposedly does this kind of thing. I'm not

Re: ctrl-w oddity on bash-4.4

2017-10-25 Thread Chet Ramey
On 10/25/17 10:37 AM, Aron Griffis wrote: > > > On Wed, Oct 25, 2017 at 9:48 AM, Chet Ramey > wrote: > > On 10/22/17 6:52 PM, Aron Griffis wrote: > > I'm seeing some strange behavior and don't know if it's a bug or > intended. > >

Re: ctrl-w oddity on bash-4.4

2017-10-25 Thread Aron Griffis
On Wed, Oct 25, 2017 at 9:48 AM, Chet Ramey wrote: > On 10/22/17 6:52 PM, Aron Griffis wrote: > > I'm seeing some strange behavior and don't know if it's a bug or > intended. > > > > Reproducer: > > 1. env INPUTRC=/dev/null bash --norc > > 2. set -o vi > > 3. true --foo=bar

Re: ctrl-w oddity on bash-4.4

2017-10-25 Thread Eduardo A . Bustamante López
On Wed, Oct 25, 2017 at 09:48:14AM -0400, Chet Ramey wrote: > On 10/22/17 6:52 PM, Aron Griffis wrote: > > I'm seeing some strange behavior and don't know if it's a bug or intended. > > > > Reproducer: > > 1. env INPUTRC=/dev/null bash --norc > > 2. set -o vi > > 3. true --foo=bar > > 4. up

Re: ctrl-w oddity on bash-4.4

2017-10-25 Thread Chet Ramey
On 10/22/17 6:52 PM, Aron Griffis wrote: > I'm seeing some strange behavior and don't know if it's a bug or intended. > > Reproducer: > 1. env INPUTRC=/dev/null bash --norc > 2. set -o vi > 3. true --foo=bar > 4. up arrow, then left arrow to put the cursor on the equals sign > 5. press ctrl-w,

Re: ctrl-w oddity on bash-4.4

2017-10-24 Thread Chet Ramey
On 10/22/17 10:08 PM, Eduardo A. Bustamante López wrote: > http://lists.gnu.org/archive/html/help-bash/2016-11/msg4.html > > I believe this is the entry in the change log describing the change, although > I'm unable to find Carlos' original report in the archives: > > |

Re: ctrl-w oddity on bash-4.4

2017-10-24 Thread Ángel
On 2017-10-22 at 21:08 -0500, Eduardo A. Bustamante López wrote: > On Sun, Oct 22, 2017 at 06:52:12PM -0400, Aron Griffis wrote: > > I'm seeing some strange behavior and don't know if it's a bug or intended. > [...] > > If this is intentional then I'd be curious about the rationale. > > Please

Re: ctrl-w oddity on bash-4.4

2017-10-22 Thread Eduardo A . Bustamante López
On Sun, Oct 22, 2017 at 10:15:54PM -0400, Aron Griffis wrote: [...] > Thanks Eduardo. The clue there about bind-tty-special-chars is helpful, > since previously I hadn't been able to make unix-word-rubout work either! > > However this doesn't seem to explain the case where ctrl-w doesn't work at

Re: ctrl-w oddity on bash-4.4

2017-10-22 Thread Aron Griffis
On Sun, Oct 22, 2017 at 10:08 PM, Eduardo A. Bustamante López < dual...@gmail.com> wrote: > On Sun, Oct 22, 2017 at 06:52:12PM -0400, Aron Griffis wrote: > > I'm seeing some strange behavior and don't know if it's a bug or > intended. > [...] > > If this is intentional then I'd be curious about

Re: ctrl-w oddity on bash-4.4

2017-10-22 Thread Eduardo A . Bustamante López
On Sun, Oct 22, 2017 at 06:52:12PM -0400, Aron Griffis wrote: > I'm seeing some strange behavior and don't know if it's a bug or intended. [...] > If this is intentional then I'd be curious about the rationale. Please read: http://lists.gnu.org/archive/html/help-bash/2016-11/msg4.html I

ctrl-w oddity on bash-4.4

2017-10-22 Thread Aron Griffis
I'm seeing some strange behavior and don't know if it's a bug or intended. Reproducer: 1. env INPUTRC=/dev/null bash --norc 2. set -o vi 3. true --foo=bar 4. up arrow, then left arrow to put the cursor on the equals sign 5. press ctrl-w, nothing happens I bisected master and found it was