Jon TURNEY wrote: > This is typical of the current issue we have where 'run xterm' blocks when > xterm tries to output 'Warning: Missing charsets in String to FontSet > conversion' > > Any one of: > - installing the CJK fonts > - having 'tty' in the CYGWIN environment variable > - having the LANG environment set to a non-UTF-8 locale > should work around this problem > > Note that the environment variable will have to be set via the system > applet in the Windows control panel, as only that controls the environment > for the startxwin.bat started from the start menu...
There's another option. In startxwin.bat, you could use run2.exe instead of run. Instead of: %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error" Use %RUNTWO% /usr/bin/XWin.xml where XWin.xml is something like the following (untested): <?xml version="1.0" encoding="us-ascii"?> <Run2Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="run2.xsd"> <SelfOptions /> <Global> <Environment> <!-- either of these, or both, and modified as desired --> <Set var="LANG" value="C.ASCII"/> <Append var="CYGWIN" value=" tty"/> </Environment> <Target filename="/usr/bin/bash.exe" startin="~"> <Arg>-l</Arg> <Arg>-c</Arg> <Arg>"XWin -multiwindow -clipboard -silent-dup-error"</Arg> </Target> </Global> </Run2Config> -- Chuck -- 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/