FW: no longer interprets mod5 modifier

sillysloft / fluxbox

Fluxbox Window Manager (Mirror)

http://fluxbox.org/news/

Other

0 stars 1 forks source link

FW: no longer interprets mod5 modifier #784

Open sillysloft opened 17 years ago

sillysloft commented 17 years ago

With the recent upgrade to v1.0, fluxbox no longer reacts to mod5 modifier events. For instance, I have

Mod5 comma :PrevTab Mod5 period :NextTab

in ~/.fluxbox/keys, but pressing the Mod5 key (Caps Lock here, I used xmodmap) does not have any effect. It works fine with the 0.9.14 fluxbox version and stops working as soon as I start the 1.0 version.

Reported by: *anonymous

sillysloft commented 17 years ago

xmodmap config

Original comment by: nobody

sillysloft commented 17 years ago

Logged In: NO

xmodmap config example:

clear Mod5 clear Control add Mod5 = Control_R add Control = Control_L

Original comment by: nobody

sillysloft commented 17 years ago

status: open --> closed-duplicate

Original comment by: mark-t

sillysloft commented 17 years ago

Logged In: YES user_id=1538990 Originator: NO

It's actually because of Caps Lock. It's already been fixed in svn.

Original comment by: mark-t

sillysloft commented 17 years ago

Logged In: NO

>It's actually because of Caps Lock. It's already been fixed in svn.

I've asked to test the revesion 4983 but mod5 doesn't function there.

Original comment by: nobody

sillysloft commented 17 years ago

Logged In: YES user_id=1538990 Originator: NO

I followed your example configuration. It works for me.

Original comment by: mark-t