Vikas Agnihotri writes:
> All this is working fine with xterm, vim, slrn, mutt, etc when I am
> NOT using fvwm2 as my window manager.
>
> This is why I am convinced that this is a fvwm2 thingie.
...
> Is this not clear? Me thinks Fvwm2 is "resetting the prefix".
One point that I was trying to put across is that this ought
controlled by the xterm. It is receiving an event when a key is
pressed and is responsible for translating that into an action. The
influence of other programs such as a wm is limited to setting options
in xterm which alter its behaviour. (Actually programs such as
xmodmap can alter the event that clients receive but it does not seem
relevant here.)
The vanilla xterm (i.e. without any *translations) generates one of
two actions depending on whether the state is SS3 or CSI. My
hypothesis is that the translations only apply in one of the states.
If you can confirm this by using the vtmenu on ctrl-MS2 to toggle the
Application Cursor Keys, then it will be a matter of chasing through
to find out how fvwm is causing xterm's state to toggle.
Some other questions:
Is there a problem when iconifying with the mouse rather than F8?
Is there a problem if the xterm is started with -iconic?
Do other window managers behave the same?
--
Pete Forman
Western Geophysical
pete.forman_at_bedford.waii.com
--
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 Tue Jul 14 1998 - 08:21:09 BST