zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>, 246305-submitter@bugs.debian.org
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#246305: zsh: completion for sudo doesn't add commands under root's path
Date: Fri, 30 Apr 2004 11:39:37 -0400	[thread overview]
Message-ID: <20040430153937.GA4644@scowler.net> (raw)
In-Reply-To: <17443.1083331282@trentino.logica.co.uk>

> 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

So probably the only reasonable thing to do is to default to current
PATH and I can put the appropriate overriding zstyle in the global zshrc
of the Debian package, or at least a note about it.

> Out of interest, is there any way to run a process detached from the tty?
> (the above sometimes prompts for a password.)

Does
sudo setsid sleep 600
do what you mean?

> 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 `.'.

So... it should be eval'd?


  reply	other threads:[~2004-04-30 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877jw0gzp3.wl@broken.int.wedontsleep.org>
2004-04-28 13:04 ` Clint Adams
2004-04-28 16:02   ` Bart Schaefer
2004-04-30 12:27     ` Clint Adams
2004-04-30 13:21       ` Oliver Kiddle
2004-04-30 15:39         ` Clint Adams [this message]
2004-04-30 16:25           ` Bart Schaefer
2004-05-01  5:02             ` Clint Adams
2004-05-01  5:25               ` Bart Schaefer
2004-05-01  5:42                 ` Clint Adams
2004-05-01 17:44                   ` [OT] Mail problems (was Re: Bug#246305 ...) Bart Schaefer

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=20040430153937.GA4644@scowler.net \
    --to=clint@zsh.org \
    --cc=246305-submitter@bugs.debian.org \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-workers@sunsite.dk \
    /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).