zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zzapper <zsh@rayninfo.co.uk>, zsh-users@zsh.org
Subject: Re: disown -a
Date: Wed, 3 Mar 2021 09:40:54 +0000 (GMT)	[thread overview]
Message-ID: <847352863.152385.1614764454969@mail2.virginmedia.com> (raw)
In-Reply-To: <4e2d5b5f-18ae-de72-dadc-2eb3e2076714@rayninfo.co.uk>

> On 03 March 2021 at 09:36 zzapper <zsh@rayninfo.co.uk> wrote:
> Now something I've never quite got my head round is or isn't the 
> underlying binary in bash & zsh for say disown or  grep actually the 
> same on any particular system?

This is one of the family of the commands that do job control, like
fg, bg, jobs.  Jobs are maintained by the shell itself.  That's
necessary so that, for example, if you run "fg" on the job the
shell can tweak it to start running and then sit back and wait for
it to exit.  An external programme wouldn't be able to do all that.
So, when you get to the point where you're not actually interested
in the job any more, you need to tell the shell to forget it,
and that's what disown is doing.

pws


  reply	other threads:[~2021-03-03  9:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 11:34 quonting and globbing Pier Paolo Grassi
2021-03-02 11:58 ` Mikael Magnusson
2021-03-02 12:24   ` Pier Paolo Grassi
2021-03-02 23:31 ` disown -a zzapper
2021-03-03  0:05   ` Daniel Shahaf
2021-03-03  7:15     ` Stephane Chazelas
2021-03-03  7:57       ` Pier Paolo Grassi
2021-03-03 10:23         ` Finding out where features come from (Was: disown -a) Stephane Chazelas
2021-03-03 14:00           ` Pier Paolo Grassi
2021-03-03 14:45             ` Pier Paolo Grassi
2021-03-03  9:36       ` disown -a zzapper
2021-03-03  9:40         ` Peter Stephenson [this message]
2021-03-03 20:12         ` Daniel Shahaf
2021-03-03  0:12   ` Daniel Shahaf
2021-03-03 10:17     ` zsh

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=847352863.152385.1614764454969@mail2.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \
    --cc=zsh@rayninfo.co.uk \
    /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).