zsh-users
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Bart Schaefer <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: Counting characters in command output?
Date: Fri, 16 Feb 2024 22:06:45 +0100	[thread overview]
Message-ID: <CAHYJk3QsQ+5j3E7dF14mFy8C6PEWYO_Dg-TnkWagYJBGM8j+5w@mail.gmail.com> (raw)
In-Reply-To: <8691219b-313f-4876-963b-75fddd39be85@app.fastmail.com>

On 2/16/24, Lawrence Velázquez <larryv@zsh.org> wrote:
> On Fri, Feb 16, 2024, at 1:03 PM, Bart Schaefer wrote:
>> On Thu, Feb 15, 2024 at 8:55 PM Lawrence Velázquez <larryv@zsh.org>
>> wrote:
>>>
>>> +  Unless enclosed in double quotes, the expansion of mytt($(command))
>>> is
>>> +  split on mytt(IFS).  In contrast, and contrary to bash and ksh,
>>> unquoted
>>> +  mytt(${ command }) and its variants are not split unless the
>>> +  mytt(SH_WORD_SPLIT) option is set.
>>
>> That's not quite accurate, though.
>>
>> % print -l ${|reply| reply=(a b c)}
>> a
>> b
>> c
>>
>> It's only ${| REPLY=...} and ${ command } that always behave like
>> scalars.
>
> Ah, you got me.  I only tested out ${ command }, and I overlooked
> that var in ${|var| command } could be an array.

Arguably the statement is still correct; the value is not split in
this case either, it is already an array.
% print -l ${|reply| reply=(a\ b c d)}
a b
c
d

notice how 'a b' is not split on $IFS.

-- 
Mikael Magnusson


      reply	other threads:[~2024-02-16 21:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 20:38 Mark J. Reed
2024-02-13 20:41 ` Roman Perepelitsa
2024-02-14  0:45   ` Mark J. Reed
2024-02-14  6:49     ` Roman Perepelitsa
2024-02-14 13:56       ` Mark J. Reed
2024-02-14 15:36       ` Ray Andrews
2024-02-14 15:58         ` Mark J. Reed
2024-02-14 16:30           ` Ray Andrews
2024-02-15 14:34             ` Lawrence Velázquez
2024-02-15  9:50         ` Roman Perepelitsa
2024-02-15 14:30           ` Lawrence Velázquez
2024-02-15 15:29             ` Ray Andrews
2024-02-15 16:16               ` Roman Perepelitsa
2024-02-15 16:55                 ` Ray Andrews
2024-02-15 14:53           ` Ray Andrews
2024-02-16  1:53       ` Bart Schaefer
2024-02-16  4:53         ` Lawrence Velázquez
2024-02-16 18:03           ` Bart Schaefer
2024-02-16 18:38             ` Mark J. Reed
2024-02-16 19:36               ` Bart Schaefer
2024-02-16 19:37             ` Lawrence Velázquez
2024-02-16 21:06               ` Mikael Magnusson [this message]

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=CAHYJk3QsQ+5j3E7dF14mFy8C6PEWYO_Dg-TnkWagYJBGM8j+5w@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=larryv@zsh.org \
    --cc=schaefer@brasslantern.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).