On Wed, 25 Feb 2004, Alexander Gottwald wrote:
On Wed, 25 Feb 2004, Danilo Turina wrote:
In effect opening an xterm within rootless mode I can see from stty that
the terminal speed is 38400, while opening the same terminal from
multiwindow mode I see that the speed is 0 (the same does not happens
for rxvt for which stty always reports 38400).
I've started bash the following ways:
cmd.exe : speed 38400
-> xterm.exe : speed 38400
-> xterm.exe : speed 38400
XWin.exe (multiwindow)
-> xterm.exe : speed 0
XWin.exe (no multiwindow)
-> xterm.exe : speed 0
-> xterm.exe : speed 0
XWin.exe (build with console window)
-> xterm.exe : speed 0
It seems the newly started xterm inherits the speed settings from the starting
program.
not exactly (I've rebooted to test cygwin, see that BAUD_0 isn't defined).
I think the issue is that the ioctl to set the baud rate fails. It
doesn't "inherit" the speed settings, since xterm "always" sets it. Seeing
why it works for rxvt would be useful, for instance.
Baud rate for a terminal emulator is bogus anyway - the reason why it is
set is to give ncurses a hint about padding. I changed it from 9600 to
38400 a few years ago, and rxvt followed suit.
The only solution seems to start the xterms from a windows console.
for now, true.