From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-6779-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 21436 invoked from network); 22 Jun 1999 09:46:55 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 22 Jun 1999 09:46:55 -0000
Received: (qmail 11260 invoked by alias); 22 Jun 1999 09:46:46 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 6779
Received: (qmail 11253 invoked from network); 22 Jun 1999 09:46:46 -0000
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
        <zsh-workers@sunsite.auc.dk>
Subject: RE: pws-22: killing the ZSH loops problem (with PATCH)
Date: Tue, 22 Jun 1999 13:45:25 +0400
Message-ID: <004c01bebc93$f3fab1e0$21c9ca95@mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <199906220935.LAA24578@beta.informatik.hu-berlin.de>

>
> When thinking about implementations I would certainly prefer the
> solution using the dummy process because most of what should be needed
> for it is already there (the existing super/sub-job code). But we
> would also need it for every shell construct in a function that is
> called from the command line...
>


Why? We only need it for a function as a whole. We want to stop/kill the whole
function as a single command, don't we?

/andrej