Hi,
I read at http://cygwin.com/ml/cygwin-xfree/2007-08/threads.html#00068
that support for the -u8 option was dropped from newer versions of xterm
for cygwin.
I'd like to vote for keeping this option, it's quite useful to me, as it
allows me to read my mail in mutt over ssh without the screen
From: Yongwei Wu [EMAIL PROTECTED]
Subject: Re: xterm(229-1) does not accept -u8
Sent: 2007-08-27 14:01
is enough to do much, like viewing multi-byte documents in Vim. I use
this script to start a UTF-8 XTerm:
#!/bin/sh
LC_CTYPE=en_US.UTF-8 xterm -u8 -fn *-medium-*--18
Poor Yorick wrote:
Yongwei wrote:
#!/bin/sh
LC_CTYPE=en_US.UTF-8 xterm -u8 -fn *-medium-*--18-*-iso10646-1 -fb
*-bold-*--18-*-iso10646-1 -fw *-medium-*-ja-18-*-iso10646-1 -e
bash $@
Double quotes around the $@ variable will ensure that positional
variables are passed into the
On 2007/08/23 19:56, Thomas Dickey wrote:
yes (but even if it's built to support UTF-8, cygwin has
very limited
locale support - no UTF-8, except as noted a while back,
applications
that have built-in locale support such as mined will
work).
Thank you for confirming this, Thomas. I
On Fri, 24 Aug 2007, neomjp wrote:
I understand that cygwin has limited support for locale,
but even so, many small utilities in cygwin packages can
work with UTF-8, such as sed, awk, perl, ruby, grep, cat,
head, tail, less(with LESSCHARSET=utf-8) and so on.
These are the things used
The newly uploaded xterm(229-1) prematurely exits when the command line
option -u8 is given, saying:
-
$ xterm -u8
[1] 2932
xterm: bad command line option -u8
usage: xterm [...
..
Type xterm -help for a full description.
On Thu, 23 Aug 2007, neomjp wrote:
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.
yes (but even
