This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: Xterm hangs with latest Cygwin (-62?)
On Oct 5 20:47, Corinna Vinschen wrote:
> Unfortunately, luit has no alternative way to make the new tty the
> controlling tty. What we need is a patch like this in luit:
>
> --- sys.c.ORIG 2009-10-05 19:23:58.000000000 +0200
> +++ sys.c 2009-10-05 19:18:34.000000000 +0200
> @@ -408,7 +408,11 @@ openTty(char *line)
> int rc;
> int tty = -1;
>
> +#ifdef __CYGWIN__
> + tty = open(line, O_RDWR);
> +#else
> tty = open(line, O_RDWR | O_NOCTTY);
> +#endif
>
> if(tty < 0)
> goto bail;
>
> This works fine for me with tcsh now as well.
Oh, btw., this only works with tcsh for me if the shortcut is
run xterm -e /bin/tcsh -l
In that case xterm calls `luit -- /bin/tcsh'. Or, it works to call
`xterm -ls' from a Cygwin shell.
However, it still behaves weird if the shortcut is
run xterm -ls
or if you start `xterm -ls' from a cmd shell. This results in xterm
calling
luit -argv0 -tcsh
which in turn starts /bin/sh with argv[0] set to "tcsh". This looks
somehow like a bug in xterm.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/