Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: man bash does not list 'in' as a builtin command
Date: Tue, 26 Nov 2019 05:13:41 +0700
Lines: 31
Approved: bug-bash@gnu.org
Message-ID: <mailman.2637.1574720095.13325.bug-bash@gnu.org>
References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <4259.1574720021@jinx.noi.kre.to>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1574720096 18180 209.51.188.17 (25 Nov 2019 22:14:56 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org, bash@packages.debian.org
To: Peter Benjamin <pete@peterbenjamin.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <4259.1574720021@jinx.noi.kre.to>
X-Mailman-Original-References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com>
Xref: csiph.com gnu.bash.bug:15644

    Date:        Mon, 25 Nov 2019 13:43:41 -0800
    From:        Peter Benjamin <pete@peterbenjamin.com>
    Message-ID:  <4dc457e0135603025cd500acdc95db53f9d30482.camel@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 just for completeness, the man
page *does* include it...

RESERVED WORDS
       Reserved words are words that have a special meaning to the shell.  The
       following words are recognized as reserved when unquoted and either the
       first word of a simple command (see SHELL GRAMMAR below) or the third
       word of a case or for command:

       ! case  coproc  do done elif else esac fi for function if in select
       then until while { } time [[ ]]

If you really have some burning desire to use "in" (or any of the others
listed there) as a command name (I doubt any will ever become any kind of
builtin, that would be bizarre) in bash or any other Bourne-type shell
(they *all* treat in as a reserved work) you can change the word (as your
 ./in did) or quote it somehow, like
	'in' "in" \in i\n \i\n

kre

ps: you really should read the whole manual page, beginning to end.