zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: 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 16:25:12 +0000	[thread overview]
Message-ID: <1040430162512.ZM1310@candle.brasslantern.com> (raw)
In-Reply-To: <20040430153937.GA4644@scowler.net>

On Apr 30, 11:39am, Clint Adams wrote:
}
} > 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?

If it needs eval-ing, that can be done with "zstyle -e ...".

I think he means that it should have several possible values, e.g. (just
throwing out ideas):

zstyle ':completion:*:sudo:*' command-path delete . .. '../*'

zstyle ':completion:*:sudo:*' command-path append /usr/local/bin /opt/bin

zstyle ':completion:*:sudo:*' command-path prepend ~/bin /usr/local/bin

zstyle ':completion:*:sudo:*' command-path assign /bin /usr/bin /usr/sbin

(This begs the question of what to do if you want to add things at both
the end and the beginning.)


  reply	other threads:[~2004-04-30 18:26 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
2004-04-30 16:25           ` Bart Schaefer [this message]
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=1040430162512.ZM1310@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=246305-submitter@bugs.debian.org \
    --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).