exwm icon indicating copy to clipboard operation
exwm copied to clipboard

exwm-workspace-switch-to-buffer loses input focus

Open gyps opened this issue 5 years ago • 9 comments

Hi, I'm using exwm 0.23 on emacs 26.3 on a debian testing/bulleseye os.

The issue can be reproduced in the following way:

  1. Bind exwm-workspace-switch-to-buffer to some key let's say "s-b".
  2. open a regular text file
  3. open a X-application e.g. firefox.
  4. switch to char-mode
  5. press s-b followed by tab to see the completions buffer
  6. enter first characters of filename and press tab to complete -> focus is lost to X-application in char-mode

Any idea why this happens? Thanks for any hint, Alex

gyps avatar Nov 19 '19 16:11 gyps

What if you continue by typing the name? The minibuffer may seem to have no focus but it should be able to receive inputs anyway.

ch11ng avatar Nov 24 '19 10:11 ch11ng

No unfortunately it doesnt. If e.g. the X-application is firefox and search field currently has focus, all further characters (after above described procedure) go into firefox's search field.

gyps avatar Nov 25 '19 17:11 gyps

Could you share your configuration or try a minimal one like in https://github.com/ch11ng/exwm/issues/680#issuecomment-557924333 ? Sounds like there is some conflicting package in use.

ch11ng avatar Nov 27 '19 14:11 ch11ng

I tried to reduce my config to the minimum. The effect is, that die phenomenon becomes nondeterministic and with an empty exwm-config I can't reproduce the behavior at all. The nondeterminism suggests that there is some kind of race condition!? I'll dig further and as soon as I find a minimal setting I'll post it here.

gyps avatar Dec 04 '19 14:12 gyps

Thanks! Waiting for your update.

ch11ng avatar Dec 08 '19 10:12 ch11ng

same...

Zik42 avatar Nov 19 '20 22:11 Zik42

same!

11111000000 avatar Jul 08 '21 06:07 11111000000

any progress?

11111000000 avatar Dec 27 '22 04:12 11111000000

I learned to live with the problem. I persists in different Linux-distributions, Emacs-versions, etc. If I reduce the init.el to the absolute minimum the problem is gone but as soon as init.el becomes a bit more complex the problem is back. I was not able to find which package causes the problems.

gyps avatar Jan 02 '23 10:01 gyps