From: Kurtis Rader <krader@skepticism.us>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: greps pipes and eval bad patterns
Date: Sun, 25 Oct 2015 18:17:46 -0700 [thread overview]
Message-ID: <CABx2=D-i9Rj2ZRUE+JQBC4qc2bF4DEKh4XZd1QF=rsV=EMiaiw@mail.gmail.com> (raw)
In-Reply-To: <151025180235.ZM30558@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
On Sun, Oct 25, 2015 at 6:02 PM, Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Oct 25, 12:47pm, Ray Andrews wrote:
> }
> } test1 ()
> } {
> } gstring=" | grep \[01;34m "
> } tree --du -haC | grep -Ev "^[^\[]{$levels}\[*" "$gstring"
> } }
>
> One doesn't normally build up a pipeline that way, but if you must do
> so, you're on the right track with "eval" -- you just haven't applied
> enough quoting....
In addition to what Bart said I'll point out that it's usually easier and
safer to avoid the eval by using an if/else block. Getting the quoting
right when using eval can be very difficult. Especially if you don't have
direct control over the text being eval'd; e.g., if some of it is supplied
by the user; or even just built up from earlier parts of the function.
I have several functions where 99% of the time I want the output
automatically piped into my pager (e.g., /usr/bin/less). But if the output
of the function is redirected away from my tty I don't want the pager in
the pipeline. So instead of using a variable that would normally contain "|
$PAGER" and sometimes be empty (i.e., using Ray's approach) I simply spell
it out:
if [[ -t 1 ]] ; then
grep -h -E $case_insensitive -- "$search_for" $files | $PAGER
else
grep -h -E $case_insensitive -- "$search_for" $files
fi
Yes, that introduces some redundancy. But it's far clearer and safer than
writing something like this (totally untested):
if [[ -t 1 ]] ; then
pager='| $PAGER'
else
pager=''
fi
eval grep -h -E $case_insensitive -- "$search_for" $files $pager
--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank
next prev parent reply other threads:[~2015-10-26 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 19:47 Ray Andrews
2015-10-26 1:02 ` Bart Schaefer
2015-10-26 1:17 ` Kurtis Rader [this message]
2015-10-26 3:39 ` Ray Andrews
2015-10-26 3:31 ` Ray Andrews
2015-10-26 13:04 ` ZyX
2015-10-26 13:36 ` Ray Andrews
2015-10-26 14:30 ` Bart Schaefer
2015-10-26 14:49 ` Ray Andrews
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='CABx2=D-i9Rj2ZRUE+JQBC4qc2bF4DEKh4XZd1QF=rsV=EMiaiw@mail.gmail.com' \
--to=krader@skepticism.us \
--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).