Shouldn't let its shortcuts propagate to windows about warpd HOT 6 CLOSED

It depends on the shortcuts in question. Traditionally X grabs are used to avoid interference among multiple clients which want to listen for the same set of keys. warpd used to use these grabs before they were replaced by a custom input layer based on xinput in order to allow compatibility with more applications.

While warpd is active it should grab all keys, but before it is active it has no way of preventing applications from processing the activation keys. It is up to the user to ensure there are no conflicts. This is why it is currently possible to bind activation keys which conflict with your window manager bindings.

Having said that, I am currently in the process of doing a partial rewrite (mainly to add macos support) which will likely end up using standard X grabs for the linux implementation.

from warpd.

Well the shortcut that most bothers me is esc. I dont mean the activation keys. On some programs I try to use warpd to focus on a text box but when I hit esc to exit warpd it also exits the textbox.

from warpd.

Actually seems this is only happening with the exit shortcut. Is there something specific to it that is making other applications grab it?

from warpd.

I just bisected and the problem was introduced by: 806f6a0

It is the leaking exit key problem.

from warpd.

Changing that 0 to 1 fixes it for me. Maybe it has other consequences?

diff --git a/src/main.c b/src/main.c
index 348a72b..94809c5 100644
--- a/src/main.c
+++ b/src/main.c
@@ -440,7 +440,7 @@ void main_loop()
                }


-               input_ungrab_keyboard(0);
+               input_ungrab_keyboard(1);
                set_cursor_visibility(1);
        }
 }

from warpd.

Sorry, you're right. This is indeed a regression. I have fixed it in the latest commit. Note that I will be releasing a fairly major overhaul of the current code base in the next few days that will also include some design changes.

from warpd.