From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29554 invoked from network); 19 Nov 1999 09:13:33 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Nov 1999 09:13:33 -0000 Received: (qmail 13165 invoked by alias); 19 Nov 1999 09:11:07 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8676 Received: (qmail 13103 invoked from network); 19 Nov 1999 09:11:02 -0000 Sender: aduret@antares.l2i To: zsh-workers@sunsite.auc.dk Cc: Falk Hueffner Subject: Re: Suggestion for _killall References: <87zowbbihr.fsf@student.uni-tuebingen.de> X-Attribution: plx From: Alexandre Duret-Lutz Date: 19 Nov 1999 10:10:50 +0000 In-Reply-To: Falk Hueffner's message of "18 Nov 1999 22:24:48 +0100" Message-ID: <7d7ljeg5at.fsf@antares.l2i> User-Agent: Gnus/5.0700000000000003 (Pterodactyl Gnus v0.97) Emacs/20.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>> "FH" == Falk Hueffner writes: [...] FH> Unfortunately, ps behaves different on each platform, so I don't know FH> if this is really portable. It isn't. Perhaps it could be done the same way as _kill? One other issue is that killall also behaves differently : - On Debian (and probably most Linux distribution) it kill process by names; - On Solaris, Digital Unix, RISC/os and maybe others, it kills *all* actives process and thus completing with process name is inappropriate. Maybe there could be two _killall in Zsh ? Let's say one in Completion/User/_killall and one in Completion/Linux/_killall. Then ./configure and Makefile would be hacked to install Linux/* only on Linux system and in such a way that Linux/* functions would overwrite previously installed User/* completions. Look quite ugly :( -- Alexandre Duret-Lutz