strange xmodmap behaviour [kind of solved]

andre.ramaciotti · 2009-01-25 14:03:41

I'm trying to set AltGr+n to the oe ligature used in French but with no luck.

I set it like this:

xmodmap -e 'keycode  57 = n N n N oe oe'

And you can see it works, because 1) using the -verbose option it doesn't show an error:

xmodmap -verbose -e 'keycode  57 = n N n N oe OE'  
! 1:  keycode  57 = n N n N oe OE
        keycode 0x39 = n N n N oe OE
!
! executing work queue
!
        keycode 0x39 = n N n N oe OE

2) If oe wasn't a legal keysym name, it would show an error:

xmodmap -e 'keycode  57 = n N n N qwe qe'
xmodmap:  commandline:1:  bad keysym name 'qwe' in keysym list
xmodmap:  commandline:1:  bad keysym name 'qe' in keysym list
xmodmap:  2 errors encountered, aborting.

3) It shows when I run xmodmap -pk and -pke:

38        0x0061 (a)    0x0041 (A)    0x0061 (a)    0x0041 (A)    0x00e6 (ae)    0x00c6 (AE)
...
57        0x006e (n)    0x004e (N)    0x006e (n)    0x004e (N)    0x13bd (oe)    0x13bc (OE)
...

keycode  38 = a A a A ae AE
...
keycode  57 = n N n N oe OE
...

Still, when I press AltGr + n, it shows 'n'. It works correctly with a (Altgr+a = æ), though, even if I set it manually or I just load my keyboard layout.

Any thoughts?

TIA

PS: I'm using the last xorg in [extra] with no hal. Parts of my xorg.conf:

Section "ServerFlags"
    Option         "AutoAddDevices" "false"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
    Option      "XkbRules"        "xorg"
    Option      "XkbModel"        "abnt2"
    Option      "XkbLayout"       "br"
    Option      "XkbVariant"      "abnt2"
EndSection

Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Last edited by andre.ramaciotti (2009-01-26 13:12:39)

andre.ramaciotti · 2009-01-26 12:34:41

I'm sorry to bump, but nobody? Should I ask it somewhere else? Or maybe report a bug upstream...

edit: I tried

xmodmap -e 'keycode 32 = o O o O oe OE'

and it worked as it should. Maybe the problem is my keyboard?

Last edited by andre.ramaciotti (2009-01-26 13:12:20)

leonardof · 2009-11-19 07:56:47

See http://bbs.archlinux.org/viewtopic.php? … 23#p405623

andre.ramaciotti · 2009-11-19 11:34:10

It doesn't work.

Once, in another post, I and another forist concluded that the problem is probably with xkb. IIRC, he is German (and I'm Brazilian) but both keyboard layouts shared this problem. When you try to define the AltGr meaning of certain keys, it doesn't work (as you can see from the posts above, if I define o, it works, but if I define n, it doesn't).

As the other forist found, it was somewhat related to how the keyboard layout is defined by xkb by default. I don't remember exactly the syntax, but almost all keys have a meaning defined when pressed together with AltGr, except (in the layout I use) j and n, so I can't define a meaning to them via xmodmap, because xkb will ignore it anyway.

I'm sorry, but I don't remember the name of this topic. I don't even know how to start searching for it. If I find it, I'll post it here.

Thanks anyway.

edit: ok, so the guy wasn't German, sorry, but this is the topic I was talking about: http://bbs.archlinux.org/viewtopic.php?id=64886

Last edited by andre.ramaciotti (2009-11-19 11:48:02)

Arch Linux

#1 2009-01-25 14:03:41

strange xmodmap behaviour [kind of solved]

#2 2009-01-26 12:34:41

Re: strange xmodmap behaviour [kind of solved]

#3 2009-11-19 07:56:47

Re: strange xmodmap behaviour [kind of solved]

#4 2009-11-19 11:34:10

Re: strange xmodmap behaviour [kind of solved]

Board footer