Trouble with uxterm in Snow Leopard
Trouble with uxterm in Snow Leopard
- Subject: Trouble with uxterm in Snow Leopard
- From: Richard Cobbe <email@hidden>
- Date: Thu, 3 Dec 2009 17:16:06 -0500
- Mail-followup-to: email@hidden
I just upgraded from 10.5.8 to 10.6.2, and I'm running the version of
XQuartz that shipped with Snow Leopard (XQuartz 2.3.4, xorg-server
1.4.2-apple45).
On the whole, everything works quite nicely, but I'm having two problems
with /usr/X11/bin/uxterm. Interestingly, /usr/X11/bin/xterm works just
fine, as far as these problems are concerned.
First, I use xrdb to set the geometry of all xterms to 80x63+0+0. The
windows do indeed display at the specified size, but the inner terminal
seems to think that the window only has 24 lines. So, for instance, if I
use "less" to view a long text file, I only see 24 lines of it at a time.
If I resize the window to 80x63 (i.e., grab the resize handle in the lower
right and move it around a bit, dropping it back in its original location),
then the terminal detects the correct window size and things start behaving
as expected.
Another data point, for what it's worth: upon starting uxterm, the first
line of the output of "stty -a" reads
speed 38400 baud; 0 rows; 0 columns;
whereas in a plain old xterm, I get
speed 38400 baud; 63 rows; 80 columns;
After I resize the uxterm, stty produces the same output as with xterm.
* * * * *
Second problem: I'm very used to the emacs-style editing keybindings that
bash supports, and under 10.5 and in plain old xterm, command acts as meta
for things like M-b, M-f, M-backspace and so forth. (I obviously have the
"Enable key equivalents under X11" option disabled.) Under uxterm on 10.6,
though, cmd-b and cmd-f insert â and æ, respectively, and cmd-backspace
appears to delete the previous character without updating the display, as
far as I can tell. Suffice to say that the command key isn't working as I
expect it to.
I checked the X modifier map (xmodmap -pm), but it's the same on both 10.5
and 10.6; I'm not playing with xmodmap.
I have the following entries in my xrdb database; these do seem to be
relevant for handling meta:
XTerm*eightBitInput: False
UXTerm*eightBitInput: False
* * * * *
I don't know if this is relevant, but TERM is indeed set to "xterm", under
both programs.
Are these configuration issues on my end, or is this a bug in uxterm?
If it is a bug in uxterm, is there a workaround? I mean, is it as easy as
starting xterm and setting XTERM_LOCALE and LC_CTYPE to en_US.UTF-8 ? Or
does uxterm do something more sophisticated upon startup?
Thanks much,
Richard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden