Re: FVWM: Strange problems with xterm and fvwm2

From: Dan Espen <dane_at_mk.bellcore.com>
Date: Sun, 12 Jul 1998 00:23:35 -0400

Vikas Agnihotri <VikasA_at_cagw1.att.com> writes:
> Using Fvwm2.0.46 on a RH5.1 system.
>
> Here is my xterm VT100 translation:
>
> XTerm.VT100.translations: #override \
> !Ctrl<Key>Right: string(0x1b) string("Oc") \n\
> None<Key>Right: string(0x1b) string("OC") \n\
> [sniped for brevity. I have similar translations for the other Special
> keys].
>
> when I initially startup fvwm and type (Ctrl-V, <Right>), I do get the^[OC,
> as per above. Also, when I startup Vim, the mouse works fine.
>
> Now, here is a snippet from my .fvwm2rc
> Key Right A S2 Scroll +100 +0
>
> i.e. NumLock+Shift+Right-arrow should pan right by one page. I did this
> because I use the numeric keypad often and so I always keep the NumLock LED
> on.
> [nsipped for brevity again. I have similar scroll commands for Up, down,
> and left keys]
>
> This also works fine. I am able o pan the viewport just fine.
>
> But, after doing even a single pan via above, for some reason, my xterm
> translations are screwed up!
>
> In other words, after I do a Pan-right, and do Ctrl-V, Right in a xterm, I
> get ^[[C instead of ^[OC as before! Same for all the other special keys
> (left, right, up, down, pageup, pagdown)
>
> And get this: Even the mouse clicks are now ignored. I launch Vim in a
> xterm and click and nothing happens!
>
> I exit from my X sessio, go back to the XDM login screen and login again,
> and everything works fine up until the point where I do a Shift-Right to
> Scroll my pager. After that things are messed up. Note that a simple
> 'Restart' doesnt fix things. I need to exit out completely.
>
> Needless to say, this is very aggravating. It is rendering all my xterm
> based applications quite useless. Mutt, slrn, etc.

I think if you check again whats going on
you will find that the curses based application (Vim) is the
cause of the problem with ^[OC changing to ^[[C.
I don't see how fvwm would be involved.

I am not saying Vim is at fault.
When I have seen this in the past, the TERMINFO had an initialization
sequence that changed what keys emit, and the reset (un-initialization)
sequence didn't undo the change.

I don't follow the part about the mouse, if you are talking about
mouse clicks in the xterm window that Vim reads, it is probably
the same terminfo problem.

>
> Thank you for any help.
>
> Vikas
> --

--
Dan Espen                                Phone: (732) 699-5570
444 Hoes Lane  Room RRC 1C-214           E-mail: dane_at_mk.bellcore.com
Piscataway, NJ 08854
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Sat Jul 11 1998 - 23:24:28 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:01 BST