zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: [PATCH] docs: Expand documentation of $histchars[1].  Joint with Matthew Martin.
Date: Sat, 13 Jan 2018 16:11:14 +0000	[thread overview]
Message-ID: <20180113161114.28345-1-danielsh@tarpaulin.shahaf.local2> (raw)

---
 Doc/Zsh/expn.yo    | 11 +++++++----
 Doc/Zsh/grammar.yo |  3 ++-
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/Doc/Zsh/expn.yo b/Doc/Zsh/expn.yo
index d5e5838df..1ea6ae47b 100644
--- a/Doc/Zsh/expn.yo
+++ b/Doc/Zsh/expn.yo
@@ -83,10 +83,11 @@ subsect(Overview)
 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; history expansions do not nest.  The `tt(!)' can be escaped
-with `tt(\)' or can be enclosed between a pair of single quotes (tt(''))
-to suppress its special meaning.  Double quotes will em(not) work for
-this.  Following this history character is an optional event designator
+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.  
+
+The first character is followed by an optional event designator
 (ifzman(see )noderef(Event Designators)) and then an optional word
 designator (noderef(Word Designators)); if neither of these designators is
 present, no history expansion occurs.
@@ -96,6 +97,8 @@ but before any other expansions take place and before the command is
 executed.  It is this expanded form that is recorded as the history event
 for later references.
 
+History expansions do not nest.
+
 By default, a history reference with no event designator refers to the
 same event as any preceding history reference on that command line; if it
 is the only history reference in a command, it refers to the previous
diff --git a/Doc/Zsh/grammar.yo b/Doc/Zsh/grammar.yo
index f9600424e..d2c7cd29c 100644
--- a/Doc/Zsh/grammar.yo
+++ b/Doc/Zsh/grammar.yo
@@ -671,4 +671,5 @@ single quote if it is set.
 
 Inside double quotes (tt("")), parameter and
 command substitution occur, and `tt(\)' quotes the characters
-`tt(\)', `tt(`)', `tt(")', and `tt($)'.
+`tt(\)', `tt(`)', `tt(")', `tt($)', and the first character
+of tt($histchars) (default `tt(!)').


             reply	other threads:[~2018-01-13 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-13 16:11 Daniel Shahaf [this message]
2018-01-13 18:04 ` Bart Schaefer
2018-01-13 18:14   ` Daniel Shahaf
2018-01-13 18:28     ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180113161114.28345-1-danielsh@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).