Re: Issues with history substitution and its documentation

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Issues with history substitution and its documentation
Date	2019-11-18 11:18 -0500
Message-ID	<mailman.1860.1574093944.13325.bug-bash@gnu.org> (permalink)
References	<CA+VKLw-WX8zUz06MZ9ThuMhUuW97aJ5ted8oSfJSvrVJBLW3hA@mail.gmail.com> <CA+VKLw_XMx1xjiFt-Tio8S+Mdt_AeS9v64SuMYYMdDdDnJFSBQ@mail.gmail.com> <CA+VKLw_hceb_xzu7kzTJAVuegWzqxJDa8xw4ja5TOBPpOWvRDQ@mail.gmail.com> <CA+VKLw_dh_SgozSCqqeg0SBTacx6PyobJff6Thu6uuV-LPCdeQ@mail.gmail.com> <6387fbce-a15e-8a32-8eea-d4cec4587f62@case.edu>

Show all headers | View raw

On 11/4/19 9:42 AM, Jim Monte wrote:
> Related to the issues with the ? event designator, the %word designator
> substitutes the *first* word  matched by the ? event designator or nothing
> if the match begins with a space. These details are not documented.

Thanks. The issue is that, unlike csh, bash allows substring matches to
span `words'. This leads to issues when the matching portion does not
begin on a word character. If the match begins on a non-word, how do you
substitute a word there?

-- 
``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 11:18 -0500

csiph-web