Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Peter Benjamin Newsgroups: gnu.bash.bug Subject: Re: man bash does not list 'in' as a builtin command Date: Thu, 05 Dec 2019 23:51:23 -0800 Lines: 30 Approved: bug-bash@gnu.org Message-ID: References: <14db6b9f69f249db60a0f92df80339d88efba152.camel@peterbenjamin.com> <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <6F7CBE03-C2F4-45CC-91D6-8A72A0C7B3B6@gmail.com> <2919.1574767603@jinx.noi.kre.to> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1575644274 20769 209.51.188.17 (6 Dec 2019 14:57:54 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bash.bug list" To: Robert Elz Envelope-to: bug-bash@gnu.org In-Reply-To: <2919.1574767603@jinx.noi.kre.to> X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 173.230.157.158 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: <14db6b9f69f249db60a0f92df80339d88efba152.camel@peterbenjamin.com> <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <6F7CBE03-C2F4-45CC-91D6-8A72A0C7B3B6@gmail.com> <2919.1574767603@jinx.noi.kre.to> Xref: csiph.com gnu.bash.bug:15698 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