Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15698 > unrolled thread

Re: man bash does not list 'in' as a builtin command

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: man bash does not list 'in' as a builtin command Peter Benjamin <pete@peterbenjamin.com> - 2019-12-05 23:51 -0800

#15698 — Re: man bash does not list 'in' as a builtin command

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 parsing and interpreting.

I looked first into the latter, my new code is always thought to have the error, before I suspect open
source software quality.  Then, I started suspecting the former, the CLI, then confirmed it.

And it could only happen for the one word, 'in', and no other.  A very special case indeed.  No worthy
of time to edit and debug and QA software.

@Robert: Down Under is a very fine place to live, indeed.

@Chris: I like the 'type' command.  Thanks.

BTW, I have named thousands of custom scripts, one letter, 2, 3, or 2 to 8 words, etc.  Never had a
problem with figuring out an error message, until this one.

'in' was the initials of the longer two words I wished to name it, but for keystroke counting purposes I
wanted just two letters.  I was going to use the command frequently for some days, 20-50 times a day.  A
testing script.  I settled on 'inn' being next fastest to type.

Peter

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web