zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: hniksic@public.srce.hr
Cc: zsh-workers@math.gatech.edu (Zsh workers list)
Subject: Re: "You have running jobs" warning
Date: Mon, 3 Jun 1996 18:01:22 +0200 (MET DST)	[thread overview]
Message-ID: <199606031601.SAA17377@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199606031345.PAA03340@jagor.srce.hr> from Hrvoje Niksic at "Jun 3, 96 03:45:28 pm"

> In your mail, you said:
> > >I am not sure I follow you.
> > >          MONITOR (-m)
> > >               Allow job control.  Set by default in  interactive
> > >               shells.
> > > 
> > >What does this have to do with what I have written?
> > 
> > If you disable job control, you will not get the warning when
> > terminating the shell.
> 
> Well, yes of course. If I kill -9 $$, I will also get no warning, but it is
> definitely not what I had in mind.

You can alias exit to 'unsetopt monitor ; exit' or you can write an exit
function which checks if there are suspended jobs and exits unconditionally
if no suspended jobs found and gives a warning otherwise.  This way you can
write an exit which does exactly what you want.  The main point that this
can be done uning the existing shell tools so we should not complicate the
code with this.  Also many people (including myself) perfer the present
behaviour.  I always use setopt nohup but I'd still like to get warnings.

Zoltan



  reply	other threads:[~1996-06-03 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-01 17:52 Hrvoje Niksic
1996-06-03 11:37 ` Zefram
1996-06-03 13:18   ` Hrvoje Niksic
1996-06-03 13:37     ` Zefram
1996-06-03 13:45       ` Hrvoje Niksic
1996-06-03 16:01         ` Zoltan Hidvegi [this message]
1996-06-03 16:10           ` Hrvoje Niksic
1996-06-03 10:31 Duncan Sinclair
1996-06-03 13:19 ` Hrvoje Niksic
1996-06-03 13:41   ` Zoltan Hidvegi

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=199606031601.SAA17377@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=hniksic@public.srce.hr \
    --cc=zsh-workers@math.gatech.edu \
    /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).