zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: _killall on linux
Date: Mon, 10 Jul 2000 09:31:03 +0000	[thread overview]
Message-ID: <1000710093103.ZM7132@candle.brasslantern.com> (raw)
In-Reply-To: <200007100713.JAA18387@beta.informatik.hu-berlin.de>

On Jul 10,  9:13am, Sven Wischnowsky wrote:
} Subject: Re: _killall on linux
}
} Bart Schaefer wrote:
} 
} > It's a bit weird that it's "processes-names" rather than "process-names".
} > (Was there some reason for that?
} 
} It doesn't have anything to do with real english -- it's just the tag
} used with some strings appended, to make it easier to remember them.

Aha.
 
} 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?

} > [*] 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.

-- 
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   


  reply	other threads:[~2000-07-10  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-10  7:13 Sven Wischnowsky
2000-07-10  9:31 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-10  9:43 Sven Wischnowsky
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=1000710093103.ZM7132@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=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).