From: Bart Schaefer <schaefer@brasslantern.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Inconsistencies in "-quoting and @-splitting, could someone elaborate?
Date: Sun, 28 Oct 2018 14:20:40 -0700 [thread overview]
Message-ID: <CAH+w=7Z+wx9s5p4spjTePKJTqLm8FOtEFiM12-NdCFeJr2HJQw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVBWSeSna03nsPnXutEQ4Q8gw0=wLkNZ0-gPhbgsg9dBbw@mail.gmail.com>
On Sun, Oct 28, 2018 at 8:41 AM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> (one could think that if a flag takes the responsibility for
> splitting in string-context ("-quoted), then that it will mimic the
> first tool to do that, the @)
Just to beat this entirely to death, you are wrong because that is NOT
WHAT @ DOES.
> 2.description) if ${(@)array} makes single-element quoted array back
> an array again, then shouldn't @ acting on single-element data (Bart
> said it's not array) returned by (z)/(s::) also make it an array
> again?
We could have done that instead of using (A), but it would have broken
historical behavior, so we did not.
> 3.description) Basically, the general method of Zshell to obtain
> scalars with no splits – double-quoting – isn't followed by (z) and
> (s::) flags.
Also explained in my first message. Implicit joining occurs before
explicit splitting.
> The manuals often elaborate about some situations
This is spelled out in painful detail in the "Rules" subsection.
next prev parent reply other threads:[~2018-10-28 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 10:33 Sebastian Gniazdowski
2018-10-28 0:34 ` dana
2018-10-28 4:54 ` Bart Schaefer
2018-10-28 11:54 ` Sebastian Gniazdowski
2018-10-28 15:41 ` Sebastian Gniazdowski
2018-10-28 15:45 ` Sebastian Gniazdowski
2018-10-28 21:20 ` Bart Schaefer [this message]
2018-10-28 21:12 ` Bart Schaefer
2018-10-29 9:10 ` Sebastian Gniazdowski
2018-10-29 15:24 ` Bart Schaefer
2018-11-05 19:03 ` Sebastian Gniazdowski
2018-11-05 23:20 ` 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=7Z+wx9s5p4spjTePKJTqLm8FOtEFiM12-NdCFeJr2HJQw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=sgniazdowski@gmail.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).