zsh-users
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Dominik Vogt" <dominik.vogt@gmx.de>
Cc: zsh-users@zsh.org
Subject: Re: view onto command pipeline?
Date: Wed, 20 Jul 2022 15:07:48 -0400	[thread overview]
Message-ID: <1f3dad2e-9fa3-4082-9c0f-6a81c136ca9b@www.fastmail.com> (raw)
In-Reply-To: <Ytf2n57VHRJg54Re@gmx.de>

On Wed, Jul 20, 2022, at 8:35 AM, Dominik Vogt wrote:
> On Wed, Jul 20, 2022 at 02:22:21PM +0200, Vincent Bernat wrote:
>> On 2022-07-20 13:37, Dominik Vogt wrote:
>> > For proper handling of whitecpace in options and arguments:
>> >
>> >    command git "${opts[@]}" "$@"
>> >
>> > Otherwise, if you have, say, files "a", "b" and "a b",
>> >
>> >    $ git commit "a b"
>> >
>> > Would commit a and b but not "a b" if the $@ is not quoted.  As a
>> > rule of thumb, _never_ use unquoted variables in shell scripts.
>>
>> I don't think this is true for Zsh.
>
> Depends on shell options:

Additionally, without quoting empty words are removed.

    % foo=                                
    % bar=(a '' 'b c')                    
    % printf '<%s>' "$foo" "$bar[@]"; echo
    <><a><><b c>
    % printf '<%s>' $foo $bar[@]; echo    
    <a><b c>

Whether or not this is desirable is up to the application.

-- 
vq


  reply	other threads:[~2022-07-20 19:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 16:15 Anthony Heading
2022-07-16 21:30 ` Bart Schaefer
2022-07-20 11:23   ` Anthony Heading
2022-07-20 11:37     ` Dominik Vogt
2022-07-20 12:22       ` Vincent Bernat
2022-07-20 12:35         ` Dominik Vogt
2022-07-20 19:07           ` Lawrence Velázquez [this message]
2022-07-21  0:15       ` Anthony Heading
2022-07-21  1:35         ` Lawrence Velázquez
2022-07-21  2:11           ` Anthony Heading
2022-07-21  3:15             ` Lawrence Velázquez
2022-07-21  6:43             ` Dominik Vogt
2022-08-04 21:12             ` Felipe Contreras
2022-07-20 19:27     ` Phil Pennock
2022-07-21  0:18       ` Anthony Heading

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=1f3dad2e-9fa3-4082-9c0f-6a81c136ca9b@www.fastmail.com \
    --to=larryv@zsh.org \
    --cc=dominik.vogt@gmx.de \
    --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).