Re: Problem with /usr/X11R6/bin/xterm
Re: Problem with /usr/X11R6/bin/xterm
- Subject: Re: Problem with /usr/X11R6/bin/xterm
- From: "Cook, Rich" <email@hidden>
- Date: Mon, 6 Dec 2010 09:52:55 -0800
- Acceptlanguage: en-US
- Thread-topic: Problem with /usr/X11R6/bin/xterm
On Dec 6, 2010, at 9:42 AM, Ambrose LI wrote:
> 2010/12/6 Cook, Rich <email@hidden>:
>> How can I test your theories? Can I trap SIGWINCH or test whether auto-wraparound is set?
>>
>> http://wealthychef.net/xterm-bug/X11ScreenSnapz001.mov
>
> As a user, to test my theories I would have done the following:
>
> If it's SIGWINCH not propagating, then the following steps should work
> around the problem:
> - After resizing, enter "eval `resize`" in the shell to reset
> environment variables and tty settings. If this fixes things up (for
> this xterm) then it's something to do with SIGWINCH (or rather changed
> tty settings not being re-read)
Have you seen my movie? In order to reproduce, I need to have something sitting there on the command line while resizing. So I'm not sure how this would work for me.
But SIGWINCH is being sent as I indicated in my other email (trapped).
> - If it does not, enter "exec $SHELL" to relaunch the shell.
> If things are still not fixed in that xterm then it is not a SIGWINCH problem.
>
> If it is auto-wraparound being turned off, then echoing a very long
> string (longer than the xterm's line width) should just echo back a
> single mixed-up line,
It does not. The echoed string is perfect, but the command gets messed up while I type. It's like readline is busted or something.
> and either of the following steps should work
> around the problem:
> 1. Run xterm with the -aw option (enter "xterm -aw" in the shell in an
> term). If the newly-created xterm does not have the problem, then it's
> auto-wraparound turned off.
> 2. Try the following:
> - In an xterm (that has the problem),
Every xterm has the problem!
> enter "TERM=vt100-nam" to
> pretend that you have a VT100 terminal with auto-wraparound turned off
> (VT100 and xterm use mostly the same control codes). If after this
> your shell behaves normally it's wraparound
Nope.
> - If it still does not behave normally, enter "exec $SHELL" to
> relaunch the shell.
> If it still does not behave normally then it's something else.
I guess it's something else.
>
> Note that if you modify or move aside your .Xresources file, you will
> need to relaunch X11 for the modification/moving aside to take effect.
>
> I thought it looked more like a wraparound problem, but I think you
> mentioned that xterm -aw behaves identically, and if this is the case
> then I am stumped.
Dang. :-( I hate it when you are stumped, because as I recall you have written some heavyweight X11 stuff on the mac.
>
> --
> cheers,
> -ambrose
--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue, Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden