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: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: man bash does not list 'in' as a builtin command Date: Tue, 26 Nov 2019 11:28:28 -0500 Lines: 64 Approved: bug-bash@gnu.org Message-ID: References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <6F7CBE03-C2F4-45CC-91D6-8A72A0C7B3B6@gmail.com> <8b8e4751-4a3c-825a-3dd4-96a788fedf06@case.edu> Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1574785714 22300 209.51.188.17 (26 Nov 2019 16:28:34 GMT) X-Complaints-To: action@cs.stanford.edu Cc: chet.ramey@case.edu, "bash.bug list" , bash@packages.debian.org To: Clint Hepner , Peter Benjamin Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574785708; bh=YUQT2NFyFHn0CFJb3g3V5H7YfNwFikixP1BOhuzNN9M=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=MqXJZMiMoBgGrtaxCemf25wdwoPYAmg1J2mzG5OSFX3W9em+9dXzZP95DOaL+rTvY9 vwffPeQrIEn6EpOuawxWW+jdf8Jp9SUWtL+fxokY+k5N6gNknjq5K8SfX0HTYjl5Sg9 U3m4l6fqe2jJzz9lx7lL9S+FuE/cIZZw7gjYzD7m1fJ6yGW4J7gzF95x+0/Yz1Xj30B wIKQEnt7wbZkXfVVm7fe7CCB/Ns9jTruqI9DqSeiy3bvzNKUTSOBqJwp/WdLC/KwGo1 Nm5V55+PvI9Wij6waa4EoygZvNDHvw1uh3yfDggcLAgtlcHE32f7yonDdNvTWF4NcMf Dbq8BNcA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574785707; bh=tuzG99rXSV9st9JiRajigFZuy/jmSfUip9dT3mKi8zI=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=9R6f/yNIOHkRTQkDSzt7oyF9tC0fL+GG+LFLC4aCXziwgdr2jJVzYEQ0lxAmeHIFPj kwZByjr04H7yDCNOpODOTMT2ljbJUGNHr3jzm8i7nUZnH9IUS/ToCkHDJqfvXq2gGy/ GZfSfP54dCzZ6S+8UDEghb/6tm14hY04BzGwWIIRxMuntLDxviitIT2Ug+Z6Qs0K2l1 WUOj8jdHZNNDbxD3ZAeGJidO2hk0ssU1fPk9Wk3roHkzwqZiuNKLt17mUmF0dZmBn83 rm4hGg5wouthAQlZsKGuIrgEN7NhA/tPoRlfa2YQeuAdR4Tm999czyMkGnSC+YdUAmt PQxXyJSQ== User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 In-Reply-To: <6F7CBE03-C2F4-45CC-91D6-8A72A0C7B3B6@gmail.com> Content-Language: en-US X-Junkmail-Status: score=8/90, host=mpv2-2015.case.edu X-Junkmail-PrAS-Raw: score=8/90, refid=2.7.2:2019.11.26.160017:17:8.510, ip=, rules=DKIM_SIGNATURE, __HAS_REPLYTO, __HAS_CC_HDR, __MULTIPLE_RCPTS_CC_X2, __CC_NAME, __CC_NAME_DIFF_FROM_ACC, __SUBJ_REPLY, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __HAS_REFERENCES, __REFERENCES, __HAS_FROM, FROM_EDU_TLD, __HAS_MSGID, __SANE_MSGID, DATE_TZ_NA, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __FROM_DOMAIN_IN_ANY_CC2, __REPLYTO_SAMEAS_FROM_DOMAIN, __DKIM_ALIGNS_1, __DKIM_ALIGNS_2, __ANY_URI, __URI_MAILTO, __URI_WITH_PATH, __URI_NO_WWW, __CP_URI_IN_BODY, __SUBJ_ALPHA_NEGATE, __LINES_OF_YELLING, __URI_IN_BODY, __URI_NOT_IMG, __FORWARDED_MSG, __BODY_NO_MAILTO, __NO_HTML_TAG_RAW, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1600_1699, __MIME_TEXT_P1, __MIME_TEXT_ONLY, [TRUNCATED], so=2010-03-03 19:42:08, dmn=2016-08-03-0138 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 129.22.103.227 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: <8b8e4751-4a3c-825a-3dd4-96a788fedf06@case.edu> X-Mailman-Original-References: <4dc457e0135603025cd500acdc95db53f9d30482.camel@peterbenjamin.com> <6F7CBE03-C2F4-45CC-91D6-8A72A0C7B3B6@gmail.com> Xref: csiph.com gnu.bash.bug:15658 On 11/25/19 8:15 PM, Clint Hepner wrote: > Alternatively, maybe a short list of sections at the top of the man page would provide > a hint. The man page format is pretty entrenched. This is an opportunity for other tools to fill the gap. > For example, imagine the man page started out like this: > > NAME > bash - GNU Bourne-Again Shell > > SYNOPSIS > bash [options] [command_string | file] > > DESCRIPTION > > Bash is [...] > > TABLE OF CONTENTS > > OPTIONS > ARGUMENTS > INVOCATION > DEFINITIONS > RESERVED WORDS > SHELL GRAMMAR > COMMENTS > QUOTING > PARAMETERS > EXPANSION > REDIRECTION > ALIASES > FUNCTIONS > ARITHMETIC EVALUATION > CONDITIONAL EXPRESSIONS > SIMPLE COMMAND EXPANSION > COMMAND EXECUTION > COMMAND EXECUTION ENVIRONMENT > ENVIRONMENT > EXIT STATUS > SIGNALS > JOB CONTROL > PROMPTING > READLINE > HISTORY > HISTORY EXPANSION > SHELL BUILTIN COMMANDS > RESTRICTED SHELL > SEE ALSO > FILES > AUTHORS > BUG REPORTS > BUGS If you want something like this, the info format is a good start. It has tables of contents, menus with links, and internal cross-references. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/