Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: man bash does not list 'in' as a builtin command Date: Mon, 25 Nov 2019 16:53:07 -0500 Lines: 16 Approved: bug-bash@gnu.org Message-ID: References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <20191125215307.GO851@eeg.ccf.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1574718793 17231 209.51.188.17 (25 Nov 2019 21:53:13 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org, bash@packages.debian.org To: Peter Benjamin Envelope-to: bug-bash@gnu.org Mail-Followup-To: Peter Benjamin , bug-bash@gnu.org, bash@packages.debian.org Content-Disposition: inline In-Reply-To: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 139.137.100.1 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: <20191125215307.GO851@eeg.ccf.org> X-Mailman-Original-References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> Xref: csiph.com gnu.bash.bug:15641 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 case WORD in PATTERN) ... ;; esac I would not recommend attempting to create a command named "in" to use in shell scripts. It's bound to get ugly.