zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: that execution stuff
Date: Tue, 29 Jun 1999 15:58:36 +0400	[thread overview]
Message-ID: <001201bec226$b7c9e400$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199906291051.MAA23127@beta.informatik.hu-berlin.de>

> Andrej Borsenkow wrote:
>
> > > I don't need to point out that `while true; do gzip ...; done' is not
> > > expected to be ^C'able again, do I? Maybe we should document this?
> > > (Together with the ^Z/fg/^C-trick?)
> >
> > It does not work. I can suspend *and* kill 'while true; do gzcat
> -f; done'. But
> > after I suspend and resume it, I can neither kill nor suspend it again.
>
> Hm, it worked for me with `zcat ... >/dev/null'. But this patch might
> also have an effect on this (because of this sub-shell-pgrp thing).
>

Yes, now it works as described. No way to kill loop with gzcat before ^Z; ant
two ^C's after that (I forgot, are two ^C's expected? Or was it supposed to be
only one?).

In any case, as long as it is documented, it is far better as csh or ksh here.
And thinking more about it - the only clean way to implement job control that
works in any case is to start "guard zsh" for every pipeline (and run every
pipeline in seperate process group). This is probably too much. It could be
optimised if we are sure pipeline never executes external commands ... no idea
how hard it is.

/andrej


  reply	other threads:[~1999-06-29 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-29 10:51 Sven Wischnowsky
1999-06-29 11:58 ` Andrej Borsenkow [this message]
1999-06-29 14:43 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1999-06-30 10:34 Sven Wischnowsky
1999-06-30  9:56 Sven Wischnowsky
1999-06-29 12:07 Sven Wischnowsky
1999-06-29  6:56 Sven Wischnowsky
1999-06-29  7:34 ` Bart Schaefer
1999-06-29 10:27 ` Andrej Borsenkow

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='001201bec226$b7c9e400$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).