From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: Disowning a stopped job
Date: Thu, 31 May 2001 17:28:47 +0200 (MET DST) [thread overview]
Message-ID: <200105311528.RAA12612@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010531141546.ZM18139@candle.brasslantern.com>
Bart Schaefer wrote:
> On May 31, 2:35pm, Sven Wischnowsky wrote:
> } Subject: PATCH: Re: tag-order problem?
> }
> } [1] My only suggestion at this time would be to think about changing the
> } warnings to `warning: job is still suspended' (i.e. inserting that
> } `still' to make it clearer that the job has been disowned but is
> } still sleeping). Dunno.
>
> Or what about something actually useful, like:
>
> disown: disowned a stopped job (use `kill -CONT -<pgrp here>')
>
> where <pgrp here> is of course the actual pgrp of the stopped job. Is
> there a reason that won't work?
The only case I can think of where it wouldn't work is if the job in
question is a super job. The user would then have to continue the
sub-job, sometimes (see killjb() in signals.c).
> ...
>
> As you point out:
>
> } execcmd() actually inserts a `disown' into the list of command words
>
> So don't insert a `disown'. Insert `bg' and delete the job table entry
> in execcmd() the way it's done in execpline2().
Hm, yes, I hadn't thought about that.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-05-31 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 16:24 tag-order problem? Tanaka Akira
2001-05-28 8:26 ` Sven Wischnowsky
2001-05-28 9:23 ` Tanaka Akira
2001-05-28 10:30 ` Sven Wischnowsky
2001-05-31 12:35 ` PATCH: " Sven Wischnowsky
2001-05-31 14:15 ` Disowning a stopped job Bart Schaefer
2001-05-31 15:28 ` Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 20:45 Bart Schaefer
2001-05-29 9:28 ` Sven Wischnowsky
2001-05-29 15:12 ` Bart Schaefer
2001-05-30 7:26 ` Sven Wischnowsky
2001-05-30 13:42 ` Sven Wischnowsky
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=200105311528.RAA12612@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.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).