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: 3.0.6-pre-5 problem
Date: Fri, 25 Jun 1999 16:29:19 +0000	[thread overview]
Message-ID: <990625162919.ZM5194@candle.brasslantern.com> (raw)
In-Reply-To: <199906251252.OAA02488@beta.informatik.hu-berlin.de>

On Jun 25,  2:52pm, Sven Wischnowsky wrote:
} Subject: Re: 3.0.6-pre-5 problem
}
} I could finally reproduce it when trying to look at it with strace,
} which finally opened my eyes (I would have needed a `ps j' output).

 PPID   PID  PGID   SID TTY TPGID  STAT  UID   TIME COMMAND
 5161  5162  5162  5162  p4  5162  T     674   0:00 Src/zsh -f 
 5162  5164  5162  5162  p4  5162  T     674   0:00 mutt 
28198  5165  5165 28198  p3  5165  R     674   0:00 ps j 
28198  5161  5161 28198  p3  5169  S       0   0:00 xterm -e Src/zsh -f 

zsh(28198)-+-pstree(5173)
           `-xterm(5161)---zsh(5162)---mutt(5164)

} It goes like this: Someone exec()s zsh without putting it into its own
} process group. Then we start the function and zsh executes external
} commands in its own process group.

The top-level xterm case is now producing process trees exactly like
the case where there's an intermediate zsh, but the parent zsh is still
not ignoring the TSTP.

} So, if we have agreed to use the kill-loop-patches, we'll have to make 
} sure that every decent interactive zsh with job-control runs in its
} own process group which is what the patch below does.

This is a good idea in any case.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~1999-06-25 16:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 12:52 Sven Wischnowsky
1999-06-25 15:56 ` Peter Stephenson
1999-06-25 16:17   ` Xterm terminal settings (Re: 3.0.6-pre-5 problem) Bart Schaefer
1999-06-25 16:29 ` Bart Schaefer [this message]
1999-06-25 17:14   ` 3.0.6-pre-5 problem Bart Schaefer
1999-06-28  6:04     ` 3.0.6-pre-5 problem and loop killing Andrej Borsenkow
  -- strict thread matches above, loose matches on Subject: below --
1999-06-25  9:38 3.0.6-pre-5 problem Sven Wischnowsky
1999-06-25 10:10 ` Bart Schaefer
1999-06-25  9:19 Sven Wischnowsky
1999-06-25  6:22 Sven Wischnowsky
1999-06-25  9:03 ` Bart Schaefer
1999-06-25  9:17 ` Bart Schaefer
1999-06-25  9:23   ` Bart Schaefer
1999-06-24 15:05 Jos Backus
1999-06-24 15:26 ` Jos Backus
1999-06-24 18:54   ` Jos Backus

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=990625162919.ZM5194@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).