From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Thomas Köhler" <jean-luc@picard.franken.de>, zsh-workers@sunsite.auc.dk
Subject: Re: _killall on linux
Date: Sat, 8 Jul 2000 17:02:05 +0000 [thread overview]
Message-ID: <1000708170205.ZM3781@candle.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C20000708164920=2EA19816=40picard=2Efranken?= =?iso-8859-1?Q?=2Ede=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_Thomas_K=F6hler_=3Cjean-luc=40pica?= =?iso-8859-1?Q?rd=2Efranken=2Ede=3E?= =?iso-8859-1?Q?________=22_killall_on_linux=22_=28Jul__8=2C__4=3A49pm=29?=
On Jul 8, 4:49pm, Thomas Köhler wrote:
} Subject: _killall on linux
}
} Now, the problem is: _killall won't complete all process names. This is
} not a big deal for "normal" users, but root may have to kill other
} user's processes, too. May I suggest something like this (completing
} _all_ process names for super users)
We could put something like that [*] in, but you should note that this
can already be configured via a style in root's .zshrc:
zstyle ':completion:*:processes-names' command ps xa ho comm
Making that configurable is the reason for the $(_call ...) expression.
It's a bit weird that it's "processes-names" rather than "process-names".
(Was there some reason for that? It's not completing both processes and
names, and one doesn't normally use the possessive "processes' names" to
refer to "names of processes".)
[*] Rather than $( [[ "$UID" = 0 ]] && print -n xa ) I'd suggest the less
resource-intensive ${=EUID//(#s)0(#e)/ps xa}.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-08 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-08 14:49 Thomas Köhler
2000-07-08 17:02 ` Bart Schaefer [this message]
2000-07-08 17:25 ` Bart Schaefer
2000-07-08 18:50 ` Thomas Köhler
2000-07-10 7:13 Sven Wischnowsky
2000-07-10 9:31 ` Bart Schaefer
2000-07-10 9:43 Sven Wischnowsky
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=1000708170205.ZM3781@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=jean-luc@picard.franken.de \
--cc=zsh-workers@sunsite.auc.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).