From: Bart Schaefer <email@example.com>
To: Zsh hackers list <firstname.lastname@example.org>
Subject: [PATCH] Clarify named references doc RE "for" loops
Date: Sat, 11 Mar 2023 13:09:08 -0800 [thread overview]
Message-ID: <CAH+w=7YZ_t5rVTqs5Ag6Hvuvz+oW9VZ4yPmySMMPSuJaUYeQAQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
Oops, forgot to label the preceding message as a patch.
Almost didn't bother to do a post for this one.
[-- Attachment #2: zsh_2023-03-11_p2.txt --]
[-- Type: text/plain, Size: 653 bytes --]
diff --git a/Doc/Zsh/grammar.yo b/Doc/Zsh/grammar.yo
index 1b834f41a..915b93bc0 100644
@@ -190,6 +190,9 @@ use the positional parameters instead of the var(word)s.
If any var(name) has been declared as a named reference,
the corresponding var(word) is treated as the name of a
parameter and var(name) is made a reference to that.
+Note that for the positional parameters, this treats the
+value of each positional as parameter name rather than
+creating a reference to the position.
The var(term) consists of one or more newline or tt(;)
which terminate the var(word)s, and are optional when the
reply other threads:[~2023-03-11 21:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).