From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: protect spaces and/or globs
Date: Thu, 11 Feb 2021 08:31:22 -0800 [thread overview]
Message-ID: <8a718224-f0e4-d960-1d65-f600ec818415@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Z6qDQPT5Mvep086mNEJ3hnJ10euN3LM=Bcgcb=5ST5_Q@mail.gmail.com>
On 2021-02-10 2:14 p.m., Bart Schaefer wrote:
>
> You probably want (@q-) there, to minimize the number of quoted
> things, or (@q+) if you use a lot of unicode characters or control
> strings.
Seems to be working fine:
grep_wrapper ()
{
grepargs=()
sstring=
while [[ $# -gt 0 ]] ; do
arg="$1"
shift
grepargs+=( "$arg" )
done
sarray=(grep --color=always -i -- "${grepargs[@]}")
print -sr -- "${(@q)sarray}"
echo "\nwhat should be going to history:"
print -r -- "${(@q)sarray}"
echo "\neval:"
eval "${(@q)sarray}"
}
Test run:
9 /aWorking/Zsh/Source/Wk 3 $ . test; grep_wrapper 'on the current'
'i,2,light edit' 'i,1,old stable'
what should be going to history:
grep --color=always -i -- on\ the\ current i,2,light\ edit i,1,old\ stable
eval:
i,2,light edit:Find any command named 'mtr*' on the current path.
i,1,old stable:Find any command named 'mtr*' on the current path.
Up arrow to recall and then re-execute:
9 /aWorking/Zsh/Source/Wk 3 $ grep --color=always -i -- on\ the\ current
i,2,light\ edit i,1,old\ stable
i,2,light edit:Find any command named 'mtr*' on the current path.
i,1,old stable:Find any command named 'mtr*' on the current path.
--------------------------------------------------------------------------------------------------------------------
So, the single quotes might be protected by double quoting as I had it
before,
or we can use the magic of ' (q) ' to protect the spaces with
backslashes even
though the single quotes themselves are gone. Or, using ' (q-) ':
9 /aWorking/Zsh/Source/Wk 3 $ . test; grep_wrapper 'on the current'
'i,2,light edit' 'i,1,old stable'
what should be going to history:
grep --color=always -i -- 'on the current' 'i,2,light edit' 'i,1,old stable'
eval:
i,2,light edit:Find any command named 'mtr*' on the current path.
i,1,old stable:Find any command named 'mtr*' on the current path.
Up arrow and re-execute:
9 /aWorking/Zsh/Source/Wk 3 $ grep --color=always -i -- 'on the current'
'i,2,light edit' 'i,1,old stable'
i,2,light edit:Find any command named 'mtr*' on the current path.
i,1,old stable:Find any command named 'mtr*' on the current path.
-------------------------------------------------------------------------------------------------------
Seems cleaner, the single quotes are themselves protected or replaced so
that
it not only runs right, it looks right; on recall it is visually
exactly the same. And is it not
intuitive that, since single quotes already protect their string, if you
add protection for the
single quotes themselves, you then have a perfectly protected string?
It can be
passed from one function to the next unchanged. This is the holy grail
for me.
Any gotchas? Or is that robust? Can I use it everywhere? Seems
right. The array
separates the arguments even if the might look like they run together in
a string.
Thanks all.
next prev parent reply other threads:[~2021-02-11 16:32 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
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 [this message]
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=8a718224-f0e4-d960-1d65-f600ec818415@eastlink.ca \
--to=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).