From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: Oliver Kiddle <okiddle@yahoo.co.uk>,
Zsh hackers list <zsh-workers@zsh.org>,
Daniel Shahaf <d.s@daniel.shahaf.name>
Subject: Re: sudo autocompletion
Date: Wed, 12 Feb 2020 17:29:07 -0800 [thread overview]
Message-ID: <CAH+w=7Z-8A5r0AZX790pmMWxYsMqsiFK9k2kiwV9=oNsm+HTCQ@mail.gmail.com> (raw)
In-Reply-To: <B8D456C0-2CFE-4B8E-BFA6-F227FB662A0E@dana.is>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
On Wed, Feb 12, 2020, 5:21 PM dana <dana@dana.is> wrote:
>
> PS: This does not fix `su -c` — _su doesn't set _c_p_p, presumably because
> it
> always prompts for a password. But since _c_p_p is passed directly to
> eval, we
> *could* make it set _c_p_p=( '' ), which would trick _command_names into
> doing
> the right thing. Is that too silly?
>
Compared to some of the other things we do? No. Just be sure not to
include a comment about it so it's just as mysterious as most of those
other tricks. (wink)
next prev parent reply other threads:[~2020-02-13 1:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <912d22db-8a8f-90f2-6738-f9f395994dcb@gmail.com>
[not found] ` <CAN=4vMqvzUTZ7bBLcbTzi-pKAVEP1xDbq=f5pLAxmffxUjTszQ@mail.gmail.com>
[not found] ` <1770be62-54d8-70a6-8b05-cfc98faa9b9f@gmail.com>
[not found] ` <20200210030219.527a3ccf@tarpaulin.shahaf.local2>
[not found] ` <ADE72275-1311-44BE-9B1D-5E617E3D9F94@gmail.com>
2020-02-10 17:13 ` dana
2020-02-10 17:40 ` Peter Stephenson
2020-02-10 18:57 ` dana
2020-02-10 19:20 ` Daniel Shahaf
2020-02-11 10:12 ` Oliver Kiddle
2020-02-11 10:28 ` Setting/Querying cache-policy (was: Re: sudo autocompletion) Daniel Shahaf
2020-02-12 16:51 ` dana
2020-02-13 1:21 ` sudo autocompletion dana
2020-02-13 1:29 ` Bart Schaefer [this message]
2020-02-15 22:22 ` Andrey Butirsky
2020-02-15 22:48 ` dana
2020-03-11 21:57 ` dana
2020-03-12 21:51 ` Andrey Butirsky
2020-02-10 22:05 ` Andrey Butirsky
2020-02-10 23:02 ` dana
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='CAH+w=7Z-8A5r0AZX790pmMWxYsMqsiFK9k2kiwV9=oNsm+HTCQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--cc=okiddle@yahoo.co.uk \
--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).