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

[Vincent Lefevre]

On 2006-06-17 17:36:09 +1000, Vincent Ho wrote:
[...]
> > > 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) "

> 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 don't think xterm does it either, otherwise it wouldn't be able
to make the difference between Backspace and Ctrl-H, for instance.

> 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.

I'm not asking to use XLookupString(). The keysym should be used.
Finally, the problem may be the fact that keysym 0x1 is not supported
by vte/GDK.

-- 
Vincent Lefèvre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA