zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: Clarify doc for tty handling with job control.
Date: Sat, 14 Oct 2000 00:07:31 +0000	[thread overview]
Message-ID: <1001014000731.ZM5809@candle.brasslantern.com> (raw)

This duplicates in the "Jobs and Signals" section some information from the
description of the STTY parameter about the way zsh restores tty modes upon
"fg", because it applies to any fg'd command, not just those with STTY in
the environment.  This came up as a sideline to my conversation with Gray
about the gdb STGTTOU bug.

I suppose I could have deleted the text from STTY and cross-referenced, but
it didn't seem extensive enough to make that worthwhile.

Index: Doc/Zsh/jobs.yo
===================================================================
--- Doc/Zsh/jobs.yo	1999/07/23 15:48:26	1.3
+++ Doc/Zsh/jobs.yo	2000/10/13 23:59:51
@@ -44,6 +44,11 @@
 tty option, then background jobs will suspend when they try to produce
 output like they do when they try to read input.
 
+When a command is suspended and continued later with the tt(fg) or
+tt(wait) builtins, zsh restores tty modes that were in effect when it was
+suspended.  This (intentionally) does not apply if the command is
+continued via `tt(kill -CONT)', nor when it is continued with tt(bg).
+
 cindex(jobs, referring to)
 cindex(referring to jobs)
 There are several ways to refer to jobs in the shell.


-- 
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   


                 reply	other threads:[~2000-10-14  0:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1001014000731.ZM5809@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.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).