From: Mikael Magnusson <mikachu@gmail.com>
To: gak@klanderman.net
Cc: zsh-workers@zsh.org
Subject: Re: have '&' automatically disown?
Date: Sun, 7 Feb 2010 22:59:09 +0100 [thread overview]
Message-ID: <237967ef1002071359y2b2b8bb9jea5717539aebf436@mail.gmail.com> (raw)
In-Reply-To: <m3sk9c7o33.fsf@klanderman.net>
On 7 February 2010 22:06, Greg Klanderman <gak@klanderman.net> wrote:
>>>>>> On February 7, 2010 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
>
>> If you start going looking for them you'll still find them.
>
> Certainly not the end of the world...
>
>> I don't know if that's good enough for your needs or not.
>
> nohup + nocheckjobs does most of what I care about I guess.
> I just noticed the later before starting this thread.
>
>> I can well believe all of this, but it's not clear to me why its
>> relevant.
>
> Because if I turn monitor back on I can completely wedge my shell.
>
>> If it means you still need job control to work continuously, then
>> certainly turning off "monitor" isn't an option.
>
> I don't actually want to use job control on the jobs started while
> monitor was off, but since they are still there, chances are I will at
> some point shoot myself in the foot.
>
> Would it make sense to just auto-disown when monitor is off?
This will probably get really annoying quickly...
_self_insert() { [[ ! -o monitor && $KEYS = '&' ]] &&
RBUFFER=!$RBUFFER; zle .$WIDGET; ((CURSOR++)) }
--
Mikael Magnusson
next prev parent reply other threads:[~2010-02-07 21:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 17:01 Greg Klanderman
2010-02-05 17:33 ` Peter Stephenson
2010-02-05 17:36 ` Peter Stephenson
2010-02-06 3:26 ` Greg Klanderman
2010-02-07 18:20 ` Peter Stephenson
2010-02-07 21:06 ` Greg Klanderman
2010-02-07 21:34 ` Peter Stephenson
2010-02-07 22:36 ` Bart Schaefer
2010-09-02 14:57 ` Greg Klanderman
2010-09-05 19:11 ` Bart Schaefer
2010-09-06 1:50 ` Greg Klanderman
2010-02-07 21:59 ` Mikael Magnusson [this message]
[not found] <gak@klanderman.net>
2009-06-26 20:40 ` bug in ztrftime(): '%e' and '%f' specifiers swapped Greg Klanderman
2009-06-26 21:23 ` Peter Stephenson
2009-06-26 21:57 ` Greg Klanderman
-- strict thread matches above, loose matches on Subject: below --
2009-05-17 4:55 PATCH: make PROMPT_SP end-of-line marker configurable Greg Klanderman
2009-05-17 17:27 ` Peter Stephenson
2009-05-17 18:04 ` Greg Klanderman
2009-05-17 19:23 ` Peter Stephenson
2009-05-18 1:00 ` Greg Klanderman
2009-05-18 18:27 ` Greg Klanderman
2009-01-13 7:32 treatment of empty strings - why is this not a bug? Greg Klanderman
2009-01-13 19:24 ` Peter Stephenson
2009-01-13 22:08 ` Peter Stephenson
2009-01-15 20:11 ` Greg Klanderman
2009-01-15 20:29 ` Peter Stephenson
2009-01-16 10:02 ` Peter Stephenson
2009-01-15 20:28 ` Greg Klanderman
2009-01-15 20:34 ` Peter Stephenson
2009-01-16 4:19 ` Bart Schaefer
2009-01-16 17:35 ` Greg Klanderman
2009-01-16 17:55 ` Peter Stephenson
2009-01-16 19:40 ` Greg Klanderman
2009-01-16 23:26 ` Richard Hartmann
2009-01-17 3:45 ` Bart Schaefer
2009-01-17 3:35 ` Bart Schaefer
2009-01-17 5:31 ` Greg Klanderman
2009-01-17 17:53 ` Peter Stephenson
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=237967ef1002071359y2b2b8bb9jea5717539aebf436@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=gak@klanderman.net \
--cc=zsh-workers@zsh.org \
/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).