From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Inconsistencies in "-quoting and @-splitting, could someone elaborate?
Date: Mon, 29 Oct 2018 10:10:55 +0100 [thread overview]
Message-ID: <CAKc7PVCWY1hLgpcxj+v3-ZqiuzM435WsERE_QA130_1YSVMbXw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZH7tkqcSu6gPd6yOXosa2bGg2n6YtLU2x7rtU2gqsn6w@mail.gmail.com>
On Sun, 28 Oct 2018 at 22:13, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sun, Oct 28, 2018 at 4:54 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> >
> > @ is refered to as "@ -- double-quoted splitting of scalars" in
> > completion.
>
> Well, that's incorrect, Oliver should not have put it that way. @ has
> nothing to do with splitting of scalars; it would more correctly say
> "prevent double-quoted joining of arrays". (In general you should
...
> > So one can obtain always-array behavior with @.
>
> Also wrong, which is why the (A) flag was extended to mean "treat
> single-element arrays as arrays instead of as scalars". The
Ok, with those clear pointers a new whole-picture can be constructed:
- @ - keep array form
- A - apply array form
> > I understand it as: for quoted expression, regenerate
> > array-form by doing splitting.
>
> No, it regenerates nothing. It just preserves the array form that
> already existed. If there was no array form in the first place, it
> has no effect.
I could see this clear fact from the execution times. @ doesn't cause
much slowdown. That said, people on IRC also directed to the
conclusion that @ is about splitting.
It is hard to create final-truth documents, I hope I will be able to
nicely rephrase it (ZNSHandbook).
--
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:[~2018-10-29 9:11 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
2018-10-28 21:12 ` Bart Schaefer
2018-10-29 9:10 ` Sebastian Gniazdowski [this message]
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=CAKc7PVCWY1hLgpcxj+v3-ZqiuzM435WsERE_QA130_1YSVMbXw@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.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).