Bug#306554: gnome-terminal doesn't honor xmodmap settings

[Vincent Ho]

On Wed, May 31, 2006 at 11:26:49AM +0200, Vincent Lefevre wrote:

Hi again Vincent (sorry for delay),

> On 2006-05-31 14:56:43 +1000, Vincent Ho wrote:
> > $ xev
> >  ...
> > KeyPress event, serial 29, synthetic NO, window 0x2600001,
> >     root 0x136, subw 0x0, time 2294871541, (397,488), root:(470,536),
> >     state 0x1, keycode 100 (keysym 0x1, (no name)), same_screen YES,
> >     XLookupString gives 1 bytes: (01) "
> > 
> > Do you still experience the problem?
> 
> I can't test it on my current machine, but I recently still had the same
> problem; xev gave the right thing (as quoted above), but gnome-terminal
> didn't take it into account.
> 
> If you type "cat[Return]", then [Ctrl-V] [Shift-Left] in gnome-terminal,
> do you get "^A"?

Well I think we agree that the xmodmap itself is taking effect.  The
difference is that in other terminals, the value of XLookupString() is
being inserted as input.  gnome-terminal (more specifically, either vte
or GDK) don't seem to do this, which results in the behaviour we're
seeing.

I've looked briefly into the code, but am uncertain which of the vte/GDK
is responsible for producing the final string.  To be honest I'm not
sure that using XLookupString() is required behaviour.  I'm sure it's
not wrong of xterm to do so, but I'm also not sure there's anything
wrong with not using it.


   Vince

-- 
  Vincent Ho

"If we hit that bullseye, the rest of the dominos will fall like a house
of cards. Checkmate."