On Tue, 2019-11-26 at 18:26 +0700, Robert Elz wrote:
> With that in mind the message in question isn't really confusing at all.
I agree. With one little exception.
Bash has two levels of error checking, that can generate the message.
1) Command line parsing and interpreting.
2) Bash script par
On 11/26/19 6:26 AM, Robert Elz wrote:
> echo get out of here, do something else for yourself
for for in for ; do echo for; done
case for in for) echo for;; esac
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet
On 11/25/19 8:15 PM, Clint Hepner wrote:
Alternatively, maybe a short list of sections at the top of the man page would
provide
a hint.
The man page format is pretty entrenched. This is an opportunity for other
tools to fill the gap.
For example, imagine the man page started out like this:
Date:Mon, 25 Nov 2019 19:13:19 -0800
From:Peter Benjamin
Message-ID:
<14db6b9f69f249db60a0f92df80339d88efba152.ca...@peterbenjamin.com>
| Only those RESERVED WORDS when tried at the CLI, alone, that generate a
| 'confusing' error message,
It is possible for some
Clint,
My thoughts on man page changes are near identical to yours. And I
thought wiser minds might first try their hand, as I do not know the
conventions the authors have used. I like how it's done now. And
something might be done a little better, I agree. So, here is my
thought. Pardon the
> On 2019 Nov 25 , at 4:43 p, Peter Benjamin wrote:
>
>
> Description:
> 'in' is a builtin command and is not listed in the man page as such.
>
> Repeat-By:
>
> type at the bash command line:
>
> $ in
> bash: syntax error near unexpected token `in'
This should be a big hint that it is *no
Date:Mon, 25 Nov 2019 13:43:41 -0800
From:Peter Benjamin
Message-ID:
<4dc457e0135603025cd500acdc95db53f9d30482.ca...@peterbenjamin.com>
| Description:
| 'in' is a builtin command and is not listed in the man page as such.
Others have indicated what it is, but j
On 11/25/19 4:53 PM, Greg Wooledge wrote:
> On Mon, Nov 25, 2019 at 01:43:41PM -0800, Peter Benjamin wrote:
>> Description:
>> 'in' is a builtin command and is not listed in the man page as such.
>
> It's actually a keyword. It's part of the "for" and "case" syntax.
>
> wooledg:~$ type in
> in
On Mon, 25 Nov 2019, Peter Benjamin wrote:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR=
On Mon, Nov 25, 2019 at 01:43:41PM -0800, Peter Benjamin wrote:
> Description:
> 'in' is a builtin command and is not listed in the man page as such.
It's actually a keyword. It's part of the "for" and "case" syntax.
wooledg:~$ type in
in is a shell keyword
for NAME in WORDS; do ...; done
cas
10 matches
Mail list logo
