Re: Issues with history substitution and its documentation

Path	csiph.com!weretis.net!feeder6.news.weretis.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Issues with history substitution and its documentation
Date	Mon, 18 Nov 2019 10:39:40 -0500
Lines	42
Approved	bug-bash@gnu.org
Message-ID	<mailman.1848.1574091593.13325.bug-bash@gnu.org> (permalink)
References	<CA+VKLw-WX8zUz06MZ9ThuMhUuW97aJ5ted8oSfJSvrVJBLW3hA@mail.gmail.com> <4e311b5a-d290-437a-e5dd-5f5f35115a3b@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 1574091594 17189 209.51.188.17 (18 Nov 2019 15:39:54 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	chet.ramey@case.edu
To	Jim Monte <jim.monte01@gmail.com>, bug-bash@gnu.org
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574091581; bh=KbnOBJdldlsypzsPj1vgmMe64jPVNWeG/C2UQsn6IRA=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=zmRlsXWhtIewKfBb7q97m11wj4Y/wEn1TCD/zP45ES4+tlHWqrlWxvexysSq1c0jsk pjDH7gOTei4j81iUHiFyi8jgRMfqgozbBWY9CVWVCm06zeFXBH1RrAdjhauogWe20r5 AxnR9EpzgvVPCchI417TgnsHlhXa+9ZziZHaGkjDWf1z6vgSLG5n9JnHPVqVrZkxB5E tnJEx0OyYLjqbjFHGFR1SGef0PWkHHC+C36mK07m1kxkTBQMvfeLMWYRb1p8Ak9XEQ8 bENx7Tvun9TJdCVWFRH0qTOsYCSDzmo5oPwkvM+iBkGqwvWcPYa2sKTq5YFWVpQ1s5V OtfrPSTA==
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574091580; bh=dSGqCr9YpAbPMwB4IMbzxxHUPJ5CP1h5tk4pBw8VYUI=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=i7sAyBd6PtXFPs2CRE4jB+HYyTHhXhzwIHFcn4djFVPAAfg0qZfDqCeY9C7kSA6jFi gGSk8PJugh0wR8mtbwLuzezmaSx6hm5waxWO/x2FQsTf8M5HhO66HRjrz0jVwYLs2nr Ag/bYMguC0Le1unoYAr2XUOOB3v4xY7Gx9ICHcPEG/UM/ioApgo2qwAHuTPdBvRqD8j Sd6vgHRlQpyKNqWztaU88HNypTNabjffFJ6c8jcfZJMdhEBNDz/3dQLgIzGUAyLCRuA /8LEJA//hDpEoi/ftadH1WWkdOvI6soe1mIIcb0dON84XIsar72sTi3mo+AhoOL0Dw2 ZPUcc2Rw==
User-Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
In-Reply-To	<CA+VKLw-WX8zUz06MZ9ThuMhUuW97aJ5ted8oSfJSvrVJBLW3hA@mail.gmail.com>
Content-Language	en-US
X-Junkmail-Status	score=7/90, host=mpv2-2015.case.edu
X-Junkmail-PrAS-Raw	score=7/90, refid=2.7.2:2019.11.18.145116:17:7.944, ip=, rules=DKIM_SIGNATURE, __HAS_REPLYTO, __HAS_CC_HDR, __SUBJ_REPLY, __PHISH_SPEAR_SUBJ_ALERT, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __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_CC1, __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, __URI_IN_BODY, __URI_NOT_IMG, __FORWARDED_MSG, __BODY_NO_MAILTO, __NO_HTML_TAG_RAW, BODY_SIZE_1500_1599, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, SXL_IP_TFX_WM[202.103.22.129.fur], [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 <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	<4e311b5a-d290-437a-e5dd-5f5f35115a3b@case.edu>
X-Mailman-Original-References	<CA+VKLw-WX8zUz06MZ9ThuMhUuW97aJ5ted8oSfJSvrVJBLW3hA@mail.gmail.com>
Xref	csiph.com gnu.bash.bug:15602

Show key headers only | View raw

On 10/3/19 6:19 PM, Jim Monte wrote:

> 
> =============================================================================
> Documentation of the :h and :t modifiers in section 9.3.3 is incomplete.
> :h removes the last / and everything after it if a / is present. Otherwise
> it does nothing.
> 
> :t removes everything before and including the last / if one is present.
> Otherwise it does nothing.

I'm comfortable with the existing language, which is the same as the csh
documentation.

> =============================================================================
> Documentation of the :r and :e modifiers is incomplete.
> :r removes the last ".suffix" and everything after it, if a ".suffix" is
> present. Otherwise it does nothing.
> :e leaves the last ".suffix" and everything after it, if a ".suffix" is
> present. Otherwise it does nothing.

I'm comfortable with the existing language.


> =============================================================================
> Documentation of :q and :x is incomplete.
> If :q and :x are repeated, the last specification is taken.

Yes, I'll note that q and x are mutually exclusive, last one wins.

=============================================================================
> Finally, documentation of G should mention that it can be used with both :s
> and &.

Good catch.

Chet
-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Issues with history substitution and its documentation Chet Ramey <chet.ramey@case.edu> - 2019-11-18 10:39 -0500

csiph-web