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: Peter Benjamin Newsgroups: gnu.bash.bug Subject: man bash does not list 'in' as a builtin command Date: Mon, 25 Nov 2019 13:43:41 -0800 Lines: 59 Approved: bug-bash@gnu.org Message-ID: References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> 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 1574718314 17058 209.51.188.17 (25 Nov 2019 21:45:14 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org, bash@packages.debian.org Envelope-to: bug-bash@gnu.org 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-Mailman-Approved-At: Mon, 25 Nov 2019 16:45:13 -0500 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: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> Xref: csiph.com gnu.bash.bug:15640 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='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I../. -I.././include -I.././lib - Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/bash- N2nMjo/bash-4.4.18=. -fstack-protector-strong -Wformat -Werror=format- security -Wall -Wno-parentheses -Wno-format-security uname output: Linux Precision 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 4.4 Patch Level: 20 Release Status: release 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' $ which in $ Or how I found out about this issue (I did not test the below): $ cd $ mkdir bin $ PATH=$HOME/bin:$PATH $ echo 'echo test in script' | tee -a ~/bin/in $ chmod 755 ~/bin/in $ which in /home/user/bin/in $ in bash: syntax error near unexpected token `in' $ Then, test the script does work just fine $ ./in test in script $ Why is this bug report important? Why change the man page? I wasted 20 minutes of my time, to prove to my satisfaction that 'in' was not invoking my script at all. Search engines did not find a match to the error message. I can not imagine this report is the first time this bug was found.