From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] sudo strace -e <TAB>
Date: Fri, 6 Mar 2015 23:42:25 -0800 [thread overview]
Message-ID: <150306234225.ZM12537@torch.brasslantern.com> (raw)
In-Reply-To: <20150307042733.GF2206@tarsus.local2>
On Mar 7, 4:27am, Daniel Shahaf wrote:
} Subject: [PATCH] sudo strace -e <TAB>
}
} Is there a smarter way to detect whether -e was passed to sudo?
Perhaps
(( $words[(i)-e] < $words[(i)[^-]*] ))
would do? That is, the -e appears before the first word that doesn't
begin with a hyphen. The way (i) works in subscripts, the above will
always be true if all the words begin with a hyphen.
A slight tweak might fix the problem with -Ae not working:
(( $words[(i)-(e|Ae)] < $words[(i)[^-]*] ))
next prev parent reply other threads:[~2015-03-07 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 4:27 Daniel Shahaf
2015-03-07 7:42 ` Bart Schaefer [this message]
2015-03-09 19:57 ` Daniel Shahaf
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=150306234225.ZM12537@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).