From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh Users <zsh-users@zsh.org>
Subject: protect spaces and/or globs
Date: Tue, 9 Feb 2021 12:42:08 -0800 [thread overview]
Message-ID: <a417e71d-f1dd-73ab-6ef0-7ff34e0804fc@eastlink.ca> (raw)
grep allow multiple filespecs of course, and if there are spaces they
have to be quoted naturally:
$ grep 'some string' filename 'filename with spaces' more_files*
My wrapper around grep has a problem with that tho because when I'm
grabbing the filespecs if I do something like this:
while [[ -n "$1" ]]; do
ffilespec+=" $1"
shift
done
Obviously the final list of files is chaos once the original enclosing
single quotes are stripped off as they are. Trying:
while [[ -n "'$1'" ]]; do
... as a brute force addition of single quotes works fine with filenames
with spaces but it also kills any glob expansions. Can I have it both
ways? I think I need to preserve any single quotes I add on CL verbatim
rather than trying to add them myself in the code. The various (q)
family flags don't seem to work. The closest I can get is to both
single quote and backslash the spaces as the input to my wrapper:
g 'some string' filename 'filename\ with\ spaces' more_files*
... and that's not so bad, but I'm betting there's an elegant way. Hafta
somehow not break the middle filespec on those spaces even without the
backslashes. And preserve the single quotes. Basically the arguments
should pass thru the function absolutely unmolested and grep should get
them exactly as I type them.
next reply other threads:[~2021-02-09 20:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 20:42 Ray Andrews [this message]
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
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=a417e71d-f1dd-73ab-6ef0-7ff34e0804fc@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).