-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Child frames grab input events #414
Comments
May be it's similar to this issue #381 (comment)? |
Setting (add-to-list 'lsp-ui-doc-frame-parameters '(no-accept-focus . t)) Perchance this should just be added to lsp-ui. It seems semantically correct, and you can even still scroll in the childframe to see the rest of the text (although doing so will focus the frame, which is not super desirable -- although this could be argued both ways). |
Actually, I am now observing the problem even with that setting. I must have done something wrong when I tested previously. |
Is there any update on this? It makes emacs very annoying to use in an i3 context when you happen to leave your cursor in the window, particularly if the window is small. I'm using the i3 edition of Manjaro Linux, with everything else default. I would use the workaround |
@samwalls Did you try what raxod502 mentioned? Setting |
Also, see i3/i3#1127 |
Hey @kiennq, I've just been trying to get that to work. Using spacemacs, it seems like it does work at a first glance, although it causes an error on startup when I add it to
Where would be the appropriate place in |
Thanks for the i3 issue link. It looks like |
#414 (comment) fixed it for me. I was losing focus and sometimes getting crashes. Both are OK now. |
The way the frame is focused has changed in recent commits. Can someone see if the issue still occurs |
I notice that the |
I just tested and the issue appears to be resolved. I do not believe I have any special configuration related to this at present. The issue has come and gone unexpectedly in the past, however, so perhaps it is best to wait for confirmation from one or more others who have encountered the same problem. I do not observe the problem reported by @kiennq w.r.t. the mouse cursor, but I presume that depends greatly on window manager configuration. |
That's already been fixed in latest version |
Today I removed this from my config:
Then I updated lsp-mode and lsp-ui. The previous problem has gone away. Also, the popup now appears top-right instead of at the cursor, which I greatly prefer (the previous behavior obscured context). Thanks! (My versions are now: lsp-mode-20200923.2151 and lsp-ui-20200923.1558.) |
Using the childframe-based interface for LSP popups, having the mouse cursor over the childframe causes all input events to be directed to the childframe's buffer, usually causing errors because that buffer is read-only and will not react correctly to most user commands. This is extremely frustrating as you can be typing and then suddenly a documentation popup will appear and all further editing commands become no-ops (they try to act on the wrong buffer) until you realize what's going on and move the mouse.
According to the Emacs manual, this behavior may vary depending on the window manager in use. I am running Manjaro Linux KDE with the default window manager.
Workaround:
The text was updated successfully, but these errors were encountered: