Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug related to stdin/always/jobcontrol
- X-seq: zsh-workers 39411
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- Subject: Re: Bug related to stdin/always/jobcontrol
- Date: Thu, 22 Sep 2016 11:59:21 +0000
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=gboGk3PKeWaZD2WQ3Mwjy4HQl48=; b=LyKt+k 4KJ8RS0aPFdC2EICw8wU1XlADwsnyG4dKxmvg2dqvDwYBYDKJYCCeDbVlXI82c4V mRdGd8Zs1fRI7pzL6VRD+XtzBLWNaSaipWojSwzhWnQeiIQ3OPYosNzhUfYLGF4M 6jnFrd+ZElgv93Gs4b/fSME5oGmwL206qebco=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=gboGk3PKeWaZD2WQ3Mwjy4HQl48=; b=tOuTk /iJlGXnmHCqS/FTYIUfsXJv46/qy99uzFmq+nc3s+F/Y/pdLoTmoYuOs7DkE55oj Y/DTvLD5Y3EBhSHVYe0MOvv8bGl2TOdBGnf8NcdOVZG3pP9ZMajiaoYaWSDoVrJt apZsKl59Xkn2w1TZZA8AOSD4mCCWDKSaT2Bmkg=
- In-reply-to: <20160914223553.3173c8ca@ntlworld.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <87r392jgd0.fsf@juno.home.vuxu.org> <20160905164207.4630643b@pwslap01u.europe.root.pri> <CGME20160914173110eucas1p1f0567e319ae439b975b19f4e55676fed@eucas1p1.samsung.com> <20160914183105.69862fa9@pwslap01u.europe.root.pri> <20160914223553.3173c8ca@ntlworld.com>
Peter Stephenson wrote on Wed, Sep 14, 2016 at 22:35:53 +0100:
> On Wed, 14 Sep 2016 18:31:05 +0100
> Peter Stephenson <p.stephenson@xxxxxxxxxxx> wrote:
> > I think I might be getting close with the attached patch... first
> > guess is we need to create a new process group, or something.
>
> The subjob needs to keep its process group because it's too late to
> change it; I found out what was missing, it needs process group leader
> assigning from that of list_pipe_job (obviously, right?) Seems a bit
> weird this never got noticed before, but it's hard to see how it can be
> wrong since this is the way the pipeline always works, regardless of
> whether the ls process or equivalent has exited. I've tried a few bits
> of job control with multiple different list-pipe-style constructs lying
> around and they still seem to work.
This (39331) broke fg'ing a function for me:
% print $ZSH_PATCHLEVEL
zsh-5.2-dev-1-401-g4e51079
% f() { $EDITOR }
% f
<press ^Z in the editor>
zsh: suspended f
% fg
[1] + continued f
zsh: suspended (tty output) f
After the 'fg' I get another prompt immediately, instead of being
returend to $EDITOR.
Cheers,
Daniel
Messages sorted by:
Reverse Date,
Date,
Thread,
Author