From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: protect spaces and/or globs
Date: Wed, 10 Feb 2021 15:47:31 +0000 (GMT) [thread overview]
Message-ID: <752329601.3729797.1612972051119@mail2.virginmedia.com> (raw)
In-Reply-To: <cbcc17c7-e4c6-638d-8d6f-931fa5fe5097@eastlink.ca>
> On 10 February 2021 at 15:18 Ray Andrews <rayandrews@eastlink.ca> wrote:
> sstring="grep --color=always -i -- ${grepargs[@]}" # I need to save
> to a scalar ...
> print -rS "$sstring" # Write to
> history ...
> eval "$sstring" # And 'eval'.
Don't turn it into a string here.
fullargs=(grep --color=always -i -- "${grepargs[@]}")
print -rS "$fullargs"
"${fullargs[@]}"
No eval needed, the arguments are now exactly the correct command arguments.
Actually, the
"${stuff[@]}"
is only needed to preserve empty arguments. It's a good habit to get into,
but you can think about it more simply as just
$stuff
i.e. a set of array elements that turn into a set of command arguments.
pws
next prev parent reply other threads:[~2021-02-10 15:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 20:42 Ray Andrews
2021-02-09 21:05 ` Lawrence Velázquez
2021-02-09 21:08 ` Peter Stephenson
2021-02-09 23:45 ` Ray Andrews
2021-02-10 0:22 ` Lawrence Velázquez
2021-02-10 0:51 ` Ray Andrews
2021-02-10 1:46 ` Lawrence Velázquez
2021-02-10 2:25 ` Ray Andrews
2021-02-10 2:52 ` Lawrence Velázquez
2021-02-10 1:52 ` Greg Klanderman
2021-02-10 2:29 ` Ray Andrews
2021-02-10 15:18 ` Ray Andrews
2021-02-10 15:47 ` Peter Stephenson [this message]
2021-02-10 16:19 ` Ray Andrews
2021-02-10 16:29 ` Peter Stephenson
2021-02-10 20:53 ` Ray Andrews
2021-02-10 22:14 ` Bart Schaefer
2021-02-11 16:31 ` Ray Andrews
2021-02-11 17:19 ` Lawrence Velázquez
2021-02-11 19:48 ` Ray Andrews
2021-02-10 18:08 ` Bart Schaefer
2021-02-10 20:56 ` Ray Andrews
2021-02-10 16:28 ` Lawrence Velázquez
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=752329601.3729797.1612972051119@mail2.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=rayandrews@eastlink.ca \
--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).