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 [thread overview]
Message-ID: <004c01bebc93$f3fab1e0$21c9ca95@mow.siemens.ru> (raw)
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
prev parent reply other threads:[~1999-06-22 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 9:35 Sven Wischnowsky
1999-06-22 9:45 ` Andrej Borsenkow [this message]
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='004c01bebc93$f3fab1e0$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.de \
--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).