From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: PATCH: [key]=value syntax, work in progress
Date: Thu, 14 Sep 2017 07:03:34 +0000 [thread overview]
Message-ID: <20170914070334.6ayvv5e6pdgq7sa4@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <20170913204108.7a55fdd6@ntlworld.com>
Peter Stephenson wrote on Wed, Sep 13, 2017 at 20:41:08 +0100:
> +++ b/Doc/Zsh/params.yo
> @@ -91,13 +91,36 @@ cindex(array assignment)
> +available. Both var(key) and var(value) undergo all forms of expansion
> +allowed for single word substitutions (this does not include filename
> +generation).
This uses the term "single word substitutions". The completion for 'e'
after ${(<TAB> says "single word shell expansions". The manual entry
for ${(e)} does not use either term.
Perhaps the manual for ${(e)} could use the term "single-word
(substitutions|expansions)"? And then this sentence might
cross-reference that flag; for example:
Both var(key) and var(value) undergo single word expansions,
as in `tt(${+LPAR()e+RPAR())var(...)tt(+RPAR())'
(note, this does not include filename generation).
Cheers,
Daniel
next prev parent reply other threads:[~2017-09-14 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 20:51 Peter Stephenson
2017-09-11 20:56 ` Peter Stephenson
2017-09-12 20:25 ` Peter Stephenson
2017-09-12 20:28 ` Peter Stephenson
2017-09-13 7:13 ` Bart Schaefer
2017-09-13 8:53 ` Peter Stephenson
2017-09-13 16:44 ` Bart Schaefer
2017-09-14 20:48 ` Peter Stephenson
2017-09-19 1:13 ` Bart Schaefer
2017-09-13 9:14 ` Oliver Kiddle
2017-09-13 19:41 ` Peter Stephenson
2017-09-14 7:03 ` Daniel Shahaf [this message]
2017-09-14 20:38 ` Peter Stephenson
2017-09-16 10:30 ` Daniel Shahaf
2017-09-14 6:54 ` 'typeset -p' of assocs (was: Re: PATCH: [key]=value syntax, work in progress) Daniel Shahaf
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=20170914070334.6ayvv5e6pdgq7sa4@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=p.w.stephenson@ntlworld.com \
--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).