[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documentation issue
From: |
Clark Wang |
Subject: |
Re: Documentation issue |
Date: |
Mon, 30 Oct 2017 10:44:39 +0800 |
On Fri, Oct 27, 2017 at 3:28 PM, Eli Barzilay <eli@barzilay.org> wrote:
> On Fri, Oct 27, 2017 at 2:37 AM, Clark Wang <dearvoid@gmail.com> wrote:
> >
> > What `unset' does is special but there's nothing special when parsing
> > the command and bash even does not care if it's built-in command or
> > not.
>
> Exactly -- and this kind of a clarification is exactly the thing that
> many people are unaware of.
>
> (And in case it wasn't clear: I said that unset is different in the
> expectations that people have with it, not in how it expands.)
>
Different people have different expectations which they believe are all
important. It's not possible to cover so many tricky things in the manual.
To me the most important thing is to describe the syntax correctly. When
you understand the syntax "unset arr[i]" would never surprise you.
- Documentation issue, Eli Barzilay, 2017/10/26
- Re: Documentation issue, Pierre Gaston, 2017/10/26
- Re: Documentation issue, Chet Ramey, 2017/10/26
- Re: Documentation issue, Eli Barzilay, 2017/10/26
- Re: Documentation issue, Chet Ramey, 2017/10/26
- Re: Documentation issue, Eli Barzilay, 2017/10/26
- Re: Documentation issue, Clark Wang, 2017/10/26
- Re: Documentation issue, Eli Barzilay, 2017/10/27
- Re: Documentation issue, Clark Wang, 2017/10/27
- Re: Documentation issue, Eli Barzilay, 2017/10/27
- Re: Documentation issue,
Clark Wang <=
- Re: Documentation issue, Eli Barzilay, 2017/10/30
- Re: Documentation issue, Greg Wooledge, 2017/10/30
- Re: Documentation issue, Chet Ramey, 2017/10/27
- Re: Documentation issue, Eli Barzilay, 2017/10/29