From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: Disowning a stopped job
Date: Wed, 30 May 2001 09:26:11 +0200 (MET DST) [thread overview]
Message-ID: <200105300726.JAA09468@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010529151211.ZM13398@candle.brasslantern.com>
Bart Schaefer wrote:
> On May 29, 11:28am, Sven Wischnowsky wrote:
> } Subject: Re: Disowning a stopped job
> }
> } Bart Schaefer wrote:
> }
> } > Using "disown" on a stopped job leaves the job stopped. There should be at
> } > least a warning about this.
> }
> } Nobody answered -- or did I miss something?
>
> It's been difficult to get opinions out of people lately. I think we're
> having -pre-X burnout.
Yes, I feel like that myself.
> } The other possibilities would of course be to generate an error, not
> } disowning the job or to call makerunning() on it before clearing the job
> } table entry.
> }
> } Of these, I think I prefer the former. The user can then still call `bg'
> } and then `disown'.
>
> I suppose the former with an option to do the latter would not work, as
> bg/fg/disown have always interpreted their first argument as a string to
> match against job names.
Yep. I was half-heartedly playing with the idea of a setopt-option,
something like silent_disown or, better, disown_auto_continue.
> Here's the thing to consider: `disown %1' is equivalent to `%1 &!'. I
> won't go so far as to say it's "intuitive," but the latter certainly looks
> as though it should cause the job to run.
True. I had forgotten about this shortcut.
> 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(). Not nice, but since execcmd() actually inserts
a `disown' into the list of command words, these cases are
indistinguishable for bin_fg().
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-05-30 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-05-30 13:42 ` Sven Wischnowsky
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
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=200105300726.JAA09468@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).