luit package and pty

2009-07-28 Thread neomjp
Hi, The recent xterm is configured with --enable-luit, but /usr/bin/luit is currently broken. $ cygcheck -f `which luit` luit-1.0.3-1 $ luit Couldn't allocate pty: No such file or directory The cause of this error and a possible fix is in http://sourceware.org/ml/cygwin/2009-04/msg00725.html

Re: Updated: xterm-238-1

2009-02-20 Thread neomjp
erm-238-1. (Try installing the xterm-238-1 source package and see /usr/src/xterm-238-1.cygport .) For more information on how to enable utf8 resource, see http://sourceware.org/ml/cygwin-xfree/2008-12/msg00079.html -- neomjp -- Power up the Internet with Yahoo

Re: Bug in "startXwin.bat"

2009-02-13 Thread neomjp
le is used, but is worse in that two black cmd.exe windows flash and disappear before XWin starts up. These two are not the ideal solution, but at least they work for the above case. I hope these patches help and get thoughtfully considered. -- neomjp diff -us /usr/bin/startxwin.bat /usr/bin

Re: xterm-237-2 still has no UTF-8 support

2008-12-10 Thread neomjp
sh, startxwin.bat, etc.) and xterm? Does the file contain anything about fonts? -- neomjp -- Power up the Internet with Yahoo! Toolbar. http://pr.mail.yahoo.co.jp/toolbar/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem rep

Re: xterm-237-2 still has no UTF-8 support

2008-12-09 Thread neomjp
-u8 2. xterm -en UTF-8 3. or use cygwin-1.7 with proper locale settings. Start bash and say, perl -we 'binmode(STDOUT, ":utf8"); print(pack("U*", 12371, 12435, 12395, 12385, 12399, 32, 50504, 45397, 54616, 49464, 50836, 63, 32, 20320, 22909));'

Re: xterm(229-1) does not accept "-u8"

2007-08-24 Thread neomjp
is needed. I will be glad if UTF-8 support is turned back on again, maybe in future updates. -- neomjp -- Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar http://pr.mail.yahoo.co.jp/toolbar/ -- Unsubscribe info: http://cygwin.com/ml/#unsub

xterm(229-1) does not accept "-u8"

2007-08-23 Thread neomjp
p". Similar problem was reported before for xterm-185-2, and the cause was that --enable-wide-chars was not used at the configuration step. (http://cygwin.com/ml/cygwin-xfree/2004-03/msg00616.html) I wonder if it is also the case this time. -- neomjp -- Unsubscribe info: http://