From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _killall on linux
Date: Mon, 10 Jul 2000 11:43:28 +0200 (MET DST) [thread overview]
Message-ID: <200007100943.LAA18552@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 10 Jul 2000 09:31:03 +0000
Bart Schaefer wrote:
> ...
>
> } At least I thought it would be easier...
>
> It's only easier that way if you know about the rule in advance (and if it
> is applied consistently, which it may very well be, I haven't looked). Is
> it mentioned as a general principle anywhere in the docs?
Well, the docs mention the processes and processes-list tags for the
command style (as examples).
The processes-names is listed together with processes and
processes-list in the tag list, of course, and processes seems to be
the only case where we needed to call _call more than once for a given
tag.
> } > [*] Rather than $( [[ "$UID" = 0 ]] && print -n xa ) I'd suggest the less
> } > resource-intensive ${=EUID//(#s)0(#e)/ps xa}.
> }
> } I wouldn't be agains that patch. But I think it raises the question if
> } we should add other default for some systems, such as -u$USER.
>
> As it turns out, the _call to ps is already in a linux-specific section
> of _killall, so the syntax for other variants of ps is irrelevant.
Ah. Sorry. I was looking at _pids.
Well, then...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-07-10 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 9:43 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 7:13 Sven Wischnowsky
2000-07-10 9:31 ` Bart Schaefer
2000-07-08 14:49 Thomas Köhler
2000-07-08 17:02 ` Bart Schaefer
2000-07-08 17:25 ` Bart Schaefer
2000-07-08 18:50 ` Thomas Köhler
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=200007100943.LAA18552@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.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).