Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#246305: zsh: completion for sudo doesn't add commands under root's path
- X-seq: zsh-workers 19855
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx, 246305@xxxxxxxxxxxxxxx
- Subject: Re: Bug#246305: zsh: completion for sudo doesn't add commands under root's path
- Date: Fri, 30 Apr 2004 15:21:22 +0200
- In-reply-to: <20040430122712.GA2985@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <877jw0gzp3.wl@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20040428130449.GA3198@xxxxxxxxxxx> <1040428160206.ZM29342@xxxxxxxxxxxxxxxxxxxxxxx> <20040430122712.GA2985@xxxxxxxxxxx>
Clint Adams wrote:
>
> Well, you could do the equivalent of "strings =sudo | grep sbin:", but
> that seems ugly and error-prone.
That wouldn't work on my system here. It looks like there is a
"SECURE_PATH" compile option to sudo which needs to be enabled before it
uses a different path:
% PATH=/usr/bin sudo printenv PATH
/usr/bin
Out of interest, is there any way to run a process detached from the tty?
(the above sometimes prompts for a password.)
> I have a sneaking suspicion that sudo isn't the only command for which
> it would make sense to override the path for _command_names though.
If you use a style, give it a generic sounding name then. Perhaps it
could be looked up from _command_names instead of _sudo. Keep in mind
that people might want to do things like add to the existing path or
remove `.'.
Oliver
Messages sorted by:
Reverse Date,
Date,
Thread,
Author