From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.dk
Subject: Re: Disowning a stopped job
Date: Thu, 31 May 2001 14:15:46 +0000 [thread overview]
Message-ID: <1010531141546.ZM18139@candle.brasslantern.com> (raw)
In-Reply-To: <200105301342.PAA10666@beta.informatik.hu-berlin.de>
In-Reply-To: <200105311235.OAA12648@beta.informatik.hu-berlin.de>
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?
} Adding a flag to tell bin_fg() that it's a
} `%1 &!' and then calling killjb() there isn't hard to implement
} either, of course, but we got no comments on this, so...
Oops, sorry, I meant to comment on it:
On May 30, 3:42pm, Sven Wischnowsky wrote:
} Subject: Re: Disowning a stopped job
}
} Bart Schaefer wrote:
}
} > Here's the thing to consider: `disown %1' is equivalent to `%1 &!'.
}
} > Would it be weird (or even possible) to have those two variants work in
} > different ways in this case?
}
} I would actually prefer it if they would differ. The only possible way
} to implement this is adding a global variable that gets set in execcmd()
} and tested in bin_fg().
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().
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-05-31 14:21 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 ` Bart Schaefer [this message]
2001-05-31 15:28 ` Disowning a stopped job Sven Wischnowsky
-- 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=1010531141546.ZM18139@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).