[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] Strange keyboard layouts and Stumpwm

From: Eric Wolf
Subject: Re: [STUMP] Strange keyboard layouts and Stumpwm
Date: Sun, 13 Jun 2010 22:11:43 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Shawn Betts <address@hidden> writes:

> 2010/6/13 Eric Wolf <address@hidden>:
>> Hi there!
>> I use a keyboard layout, where ISO_Level3_Shift is needed to get
>> the ;:@! and so on symbols. And ISO_Level3_Shift was placed on the
>> caps lock key.
>> If I try to exec ( C-t ! ) something I would have to type
>> C-t capslock-k. But in the moment I press capslock in this
>> sequence, stumpwm complains about C-t ISO_Level3_Shift not
>> being mapped.
>> How can I get stumpwm not to recognise ISO_Level3_shift as
>> a relevant keystroke in this context? (So that it can do
>> its job changing the keyboard level.)
> It's probably not marked as a modifier in X. it should appear on one
> of the MOD lines in the output from xmodmap.

Okay, I modified the symbols-file of the keyboardlayout to
include "modifier_map ModX { <KEY> };" statements instead of
"modifier_map ModX { ISO_Level3_Shift };".

And now xmodmap displays
mod3        ISO_Level5_Shift (0x5e),  ISO_Level5_Shift (0x6c),  
ISO_Level5_Shift (0xcb)
mod5        ISO_Level3_Shift (0x33),  ISO_Level3_Shift (0x42),  
ISO_Level3_Shift (0x5c)
for the relevant modifiers.

And stumpwm doesn’t complain any more.

But now there is another problem. If I type C-t capslock-k stumpwm does
"kill" instead of "exec".

So stumpwm receives "k" instead of "!". But in xfterm4 and emacs for
example capslock-k gives "!".

I don‘t have any idea whats going on. Maybe you have some idea?
Would a xkbcomp-dump be helpful ?

Yours sincerely,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]