From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: What's the reasoning behind z & s returning nular for empty input?
Date: Sat, 9 Nov 2019 10:09:44 +0100 [thread overview]
Message-ID: <CAKc7PVCvXNx2R_sJsDAGW1vU_LKHRK5W_HDm496Efk0XpG9KzQ@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMriuV_u+LpOJDjRLtrE94h5hEXgrQXtVH-cpBg+kRCh-w@mail.gmail.com>
On Sat, 9 Nov 2019 at 09:52, Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> On Sat, Nov 9, 2019 at 9:40 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> > Yes, I was also referring to this fragment, however it states that the
> > empty elements should be removed, and even – that they should be
> > removed more eagerly, so I still wonder why produce a nular for an
> > empty input?
>
> Oh, I see what you mean. Apparently, only inner empty elements are
> dropped by "${(s...)...}" while the first and the last are retained.
>
> "${(s:,:):-a,,b}" => (a b)
> "${(s:,:):-,,}" => ('' '')
>
> Looks like it's either a bug in the code or in the documentation.
True, I wasn't fully aware of that:
array=( "${(s:,:):-,,}" )
print -r ${(q)array}
Output:'' ''
array=( "${(s:,:):-,}" )
print -r ${(q)array}
Output:'' ''
I think that the documentation or the behavior should be updated.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2019-11-10 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 7:26 Sebastian Gniazdowski
2019-11-09 7:50 ` Roman Perepelitsa
2019-11-09 7:52 ` Roman Perepelitsa
2019-11-09 8:11 ` Sebastian Gniazdowski
2019-11-09 8:22 ` Roman Perepelitsa
2019-11-09 8:40 ` Sebastian Gniazdowski
2019-11-09 8:52 ` Roman Perepelitsa
2019-11-09 9:09 ` Sebastian Gniazdowski [this message]
2019-11-09 14:33 ` Peter Stephenson
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=CAKc7PVCvXNx2R_sJsDAGW1vU_LKHRK5W_HDm496Efk0XpG9KzQ@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-users@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).