From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Inconsistencies in "-quoting and @-splitting, could someone elaborate?
Date: Sat, 27 Oct 2018 12:33:00 +0200 [thread overview]
Message-ID: <CAKc7PVCdqYwOrYr5-7bzduNsJd9OAUz0B-68jg_D5MqMUiVnKw@mail.gmail.com> (raw)
Hello.
I'm having problem in grasping, is this behavior:
- "X-flag creates array, unless its result is a single element", and
- "X-flag creates array even when double quoted without use of @"
is this behavior consistent, or per-flag, or general
random/historical.. Because the two behaviors seem to apply for (s::)
and (z) (a='a b c d'; print -rl "${(z)a}" will print 4 lines, despite
"-quoting and lack of @), but they look like a two unrelated,
accidentally-similar, with possible further differences, exceptions,
so I would state there's a major inconsistency/historically-driven
problem in Zsh. Are there other such flags in Zsh?
I would add this information to Zsh Native Scripting Handbook. I will
investigate by experimenting and come up with conclusion myself if no
one will help.
Worth noting: the first behavior – no-array for singular result – can
be fixed into consistent (i.e. "always array") behavior by the updated
(A) flag, patch 40640, first appearing in Zsh version 5.4.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next reply other threads:[~2018-10-27 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 10:33 Sebastian Gniazdowski [this message]
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
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=CAKc7PVCdqYwOrYr5-7bzduNsJd9OAUz0B-68jg_D5MqMUiVnKw@mail.gmail.com \
--to=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).