Suspending the global KDE&X-Windows keyboard shortcuts while specific application is running

kdekeyboard shortcuts

I'm running KDE on Arch-Linux 64b.

I've been a Vim user for two years now, and I want to try learning Emacs – just so I can have a justification when I diss Emacs users. So far, my main problem with Emacs is that it many of it's shortcuts use ctrl+alt and ctrl+shift – so they collide with my global shortcuts.

I have no desire to change my global shortcuts(to what? Emacs leaves no key combination unbound…), but I can afford to disable them while the Emacs window has the focus.

So – can it be done? Can I disable the global shortcuts only when a specific application is running?

Best Answer

right-click on the emacs window titlebar, then:

More Actions ->

Special Application Settings ->

select tab Appearance & Fixes ->

check Ignore global shortcut, select Force from the dropdown menu and check the radio button Yes. enter image description here

You can access all your custom application settings via System Settings, selecting Window behaviour and then Window rules

Related Solutions

KDE custom global shortcuts

First make sure that your script is executable, e.g. like this

chmod +x ~/scripts/myscript.sh

Then create the shortcut using the tool which can be accessed by System Settings > Input Actions. Do a right click in the left pane where existing shortcuts are listed and say New Global Shortcut > Command/URL. Set the name to something sensible, choose your desired shortcut, set the command to your script, e.g. ~/scripts/myscript.sh and tick the Enabled box. If you put your script in a folder in path, (following common conventions one would use /usr/local/bin) you can skip the path in the command and just write myscript.sh.

Grabbing the Ctrl+s key

Analyzing the Xorg.0.log in more details showed that Ctrl+s was consumed by the kglobalaccel5 process which is the Wayland/KDE global hot key manager.

However, since I knew there were no Ctrl+s key defined as a global hotkey the only solution was that this was a keymap collision (or rather a key chord collision).

It turned out (after some trial and error testing) that the resulting key events for Ctrl+§ on my keyboard was the same as for Ctrl+s (I used to map Ctrl+§ to open the "Dashboard Widget" )

Most likely because I use a Generic keyboard mapping and not specific for my "rapoo"-quick typing keyboard. I don't have the detailed knowledge of how the interaction of keys + modifier can result in this collision. The normal keys, i.e. 's' and '§' individually works but apparently using them together with the 'Ctrl' modifier gives the same chord value.

The solution was to remove the global mapping for Ctrl+§

Interesting problem!

Best Answer

Related Solutions

KDE custom global shortcuts

Grabbing the Ctrl+s key

Related Question