zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: mason@primenet.com.au, zsh-workers@sunsite.auc.dk
Subject: Re: BUG: backgrounding zsh does bad tty stuff
Date: Sat, 12 Feb 2000 05:58:46 +0000	[thread overview]
Message-ID: <1000212055846.ZM6576@candle.brasslantern.com> (raw)
In-Reply-To: <slrn8a9qc6.j8r.mason@coral.primenet.com.au>

On Feb 12,  5:03am, Geoff Wing wrote:
} Subject: BUG: backgrounding zsh does bad tty stuff
}
} Heyla,
} 
} % zsh-3.0.7 -f
} % echo $SHLVL
} 2
} % zsh-3.0.7 -f &
} [1] 19784

I immediately get

[1]  + suspended (tty output)  zsh -f

at this point, even with "stty -tostop".  Linux won't let any process
but the tty group leader poke settings into the tty driver.

What operating system are you using?

However, what did you expect?  "zsh -f" has no idea that it's in the
background, and attempts to start up ZLE as usual.  That's going to
play havoc with the parent shell's tty driver if the OS will let it
get away with it.

There's even a loop in init.c:init_io() where zsh repeatedly attempts to
force itself to be the tty foreground process, sending the pgrp leader
a SIGTTIN and then attempting to grab the tty.  Not pretty, but it has
been there for a very long time.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-02-12  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-12  5:03 Geoff Wing
2000-02-12  5:58 ` Bart Schaefer [this message]
2000-02-12 12:17   ` PATCH: 3.1.6-dev-17 (Was: BUG: backgrounding zsh does bad tty stuff) Geoff Wing
2000-02-12 18:00     ` Bart Schaefer
2000-02-13  5:22       ` Geoff Wing

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=1000212055846.ZM6576@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=mason@primenet.com.au \
    --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).