1
0
Fork 0
mirror of git://git.code.sf.net/p/zsh/code synced 2024-06-01 04:46:08 +02:00

unposted: Follow-up to previous: Clarify that ${histchars[1]} may be backslash-escaped even when it isn't '!'.

This commit is contained in:
Barton E. Schaefer 2018-01-13 18:54:36 +00:00 committed by Daniel Shahaf
parent ba752d2eb5
commit 254d8ed8cb
2 changed files with 6 additions and 2 deletions

View File

@ -1,3 +1,8 @@
2018-01-13 Barton E. Schaefer <schaefer@zsh.org>
* unposted: Doc/Zsh/expn.yo: Follow-up to previous: Clarify that
${histchars[1]} may be backslash-escaped even when it isn't '!'.
2018-01-13 Daniel Shahaf <d.s@daniel.shahaf.name>
* 42261: Doc/Zsh/expn.yo, Doc/Zsh/grammar.yo: docs: Expand

View File

@ -84,8 +84,7 @@ vindex(histchars, use of)
A history expansion begins with the first character of the tt(histchars)
parameter, which is `tt(!)' by default, and may occur anywhere on the
command line, including inside double quotes (but not inside single quotes
tt('...') or C-style quotes tt($'...')). A literal `tt(!)' may be
obtained by escaping it with a backslash.
tt('...') or C-style quotes tt($'...') nor when escaped with a backslash).
The first character is followed by an optional event designator
(ifzman(see )noderef(Event Designators)) and then an optional word