From: Bart Schaefer <schaefer@brasslantern.com>
To: Sebastian Gniazdowski <psprint@zdharma.org>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Feature request – substitutions similar to +, -, :+, :-
Date: Sat, 18 Nov 2017 10:46:18 -0800 [thread overview]
Message-ID: <CAH+w=7aorJaP31T7X3Q9_HUJOu95ToHUeOEjy902V43bPVpPvg@mail.gmail.com> (raw)
In-Reply-To: <etPan.5a107a4b.459f7f60.137@zdharma.org>
On Sat, Nov 18, 2017 at 10:22 AM, Sebastian Gniazdowski
<psprint@zdharma.org> wrote:
>
> On 18 Nov 2017 at 19:05:25, Sebastian Gniazdowski (psprint@zdharma.org) wrote:
> > echo "I'm ${${theme[use-name]:&Patrick}:-a subscriber}, hello."
>
> Just realized that with the description of :& I gave, this would work the same, except not only for "1", but any non-empty string:
>
> echo "I'm ${${theme[use-name]:+Patrick}:-a subscriber}
>
> So it's a matter of getting consensus on details of :& and :^.
If I understand your example correctly, $theme[use-name] is either
unset/empty, or it contains "1" or "0".
So I think :& is just ${(M)theme[use-name]:#1} and :^ is ${theme[use-name]:#0}.
For $options, ${(M)options[...]:#on} and ${options[...]:#off}, so this
trick works with non-numeric booleans too.
You can do something similar with ${var/pat/repl} if you need to test
for substrings.
next prev parent reply other threads:[~2017-11-18 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 18:05 Sebastian Gniazdowski
2017-11-18 18:22 ` Sebastian Gniazdowski
2017-11-18 18:46 ` Bart Schaefer [this message]
[not found] ` <etPan.5a10805d.57d72d7c.137@AirmailxGenerated.am>
2017-11-25 11:15 ` Sebastian Gniazdowski
2017-12-03 9:11 ` Ternary expression in Zsh (was: Feature request – substitutions similar to +, -, :+, :-) Sebastian Gniazdowski
2017-12-05 6:55 ` Stephane Chazelas
2017-12-05 8:06 ` Tom M.
2017-12-05 9:04 ` Bart Schaefer
2017-12-05 8:24 ` Sebastian Gniazdowski
2017-12-05 9:05 ` 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='CAH+w=7aorJaP31T7X3Q9_HUJOu95ToHUeOEjy902V43bPVpPvg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=psprint@zdharma.org \
--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).