Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Xterm terminal settings (Re: 3.0.6-pre-5 problem)
- X-seq: zsh-workers 6858
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Peter Stephenson <pws@xxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Xterm terminal settings (Re: 3.0.6-pre-5 problem)
- Date: Fri, 25 Jun 1999 16:17:57 +0000
- In-reply-to: <199906251556.RAA04789@xxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199906251556.RAA04789@xxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author