Re: Documentation issue

On Thu, Oct 26, 2017 at 10:50 PM, Clark Wang wrote: > On Fri, Oct 27, 2017 at 3:00 AM, Eli Barzilay wrote: >> >> 1. Drop the current "Care must be taken ... the entire array." two >>sentences and replace them with some "See the unset builtin >>

Re: Documentation issue

On Fri, Oct 27, 2017 at 3:00 AM, Eli Barzilay wrote: > On Thu, Oct 26, 2017 at 2:02 PM, Chet Ramey wrote: > > > > It's more of a general statement about arrays, though it appears in > > the paragraph that discusses unset, so it's in the man page section

Re: ctrl-w oddity on bash-4.4

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

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

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

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: Documentation issue

On Thu, Oct 26, 2017 at 2:02 PM, Chet Ramey wrote: > > It's more of a general statement about arrays, though it appears in > the paragraph that discusses unset, so it's in the man page section on > arrays. You have to be careful about putting the same information in > too

Re: Documentation issue

On 10/26/17 11:28 AM, Eli Barzilay wrote: >> I'm not sure why this is a surprise. Pathname expansion (globbing) is >> one of the word expansions performed before a simple command is >> executed. The `unset' builtin is no different. > > The last sentence is showing why it's a surprise: it is

Re: Documentation issue

Pierre Gaston: > I think it's even more likely to happen with eg: read array[i] Maybe, but see below. > There is a large number of pitfalls in bash > (http://mywiki.wooledge.org/BashPitfalls) that most people ignore. And it doesn't even mention the unset problem, I think. On Thu, Oct 26, 2017

Re: ctrl-w oddity on bash-4.4

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: Documentation issue

On 10/26/17 1:18 AM, Eli Barzilay wrote: > Bash surprised me with the behavior mentioned here: > > https://stackoverflow.com/questions/15897473 > > This can be pretty bad in that it's very unexpected (see the comments). I'm not sure why this is a surprise. Pathname expansion (globbing) is

Re: Documentation issue

On Thu, Oct 26, 2017 at 8:18 AM, Eli Barzilay wrote: > Bash surprised me with the behavior mentioned here: > > https://stackoverflow.com/questions/15897473 > > This can be pretty bad in that it's very unexpected (see the comments). > Also, the surprise can be triggered

Documentation issue

Bash surprised me with the behavior mentioned here: https://stackoverflow.com/questions/15897473 This can be pretty bad in that it's very unexpected (see the comments). Also, the surprise can be triggered without nullglob as well: $ foo=(a b c) $ touch foo0 $ unset foo[0] $