zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@ifh.de>, zsh-workers@sunsite.auc.dk
Subject: Xterm terminal settings (Re: 3.0.6-pre-5 problem)
Date: Fri, 25 Jun 1999 16:17:57 +0000	[thread overview]
Message-ID: <990625161757.ZM5127@candle.brasslantern.com> (raw)
In-Reply-To: <199906251556.RAA04789@hydra.ifh.de>

On Jun 25,  5:56pm, Peter Stephenson wrote:
} Subject: Re: 3.0.6-pre-5 problem
}
} By the way, although this is totally unrelated, looking at this I
} discovered that
}   SHELL=/usr/bin/ksh xterm &
} creates an xterm with terminal settings messed up.  Without the & it's OK.

I believe this to be an OS pty-allocation problem rather than a zsh problem.
I've seen it before in contexts unrelated to zsh.  SunOS in particular is a
culprit; what's happening is that the tty driver for the pseudo-tty copies
its settings from the current controlling terminal of the process that opens
the master side.  When the master process (xterm in this case) doesn't have
an associated tty, the pty gets bad values -- on SunOS, it gets the values
for the system console, which are generally nothing like what you want an
xterm to have.

(It just occurred to me that this problem may show up on any system that
uses STREAMS modules instead of BSD-style TTY drivers.)

Anyway, for several releases of X11 now there's been a resource for setting
your xterm TTY values to work around this bug; it's XTerm*ttyModes: and the
value looks like an stty command line (without the command name).

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


  reply	other threads:[~1999-06-25 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 12:52 3.0.6-pre-5 problem Sven Wischnowsky
1999-06-25 15:56 ` Peter Stephenson
1999-06-25 16:17   ` Bart Schaefer [this message]
1999-06-25 16:29 ` Bart Schaefer
1999-06-25 17:14   ` Bart Schaefer
1999-06-28  6:04     ` 3.0.6-pre-5 problem and loop killing Andrej Borsenkow

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=990625161757.ZM5127@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=pws@ifh.de \
    --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).