-
Notifications
You must be signed in to change notification settings - Fork 134
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
org-resolve-clocks
(and other spontaneous focus-grabing functions) has conflict with EXWM-mode buffers
#921
Comments
Org is using I'm not sure whether changing EXWM to detect it is desirable (fullscreen?) or even doable. (I miss @ch11ng.) I also have little time available. I suggest you to bring this up with the Org developers: could they use a higher-level function instead, like |
The difference was that in earlier versions of EXWM I could click on some other window (beside the active EXWM) and the focus would go back to emacs and I was able to deal with org and that was an acceptable work around when on had a mouse. But now clicking on other windows while org has taken control of keyboard input does nothing. I assume the the desired behavoir is to change the focus when clicking even if org has taken over the keyboard input. |
Org recently (Org 9.6-3-ga4d38e, ~2022) changed the function to use |
I submitted a bug: https://lists.gnu.org/archive/html/emacs-orgmode/2023-11/msg00150.html They put it on EXWM I think: " I also do not see any reason why Org should not use I would not mind changing Not an Org bug. |
@drskalman, we just merged a new change to deal with this issue (by new maintainer @Stebalien). Please test latest master and report back. |
Sorry for the delay. I keep my exwm running for weeks and rarely logout. But I rebooted yesterday and logged backed in with the new exwm and this morning I had the same problem:
I still can put end on org keyboard tyranny of org by issuing:
In another tty beside X. I can reproduce it relaibly if you need more info. |
Just to make sure everything is working, when you run
At the bottom. Do you see that? Also, is your EXWM buffer in line or char mode? |
Finally, try running |
My bad. I had exwm also installed from gnu repo and so it was loading that instead of the one from os package manager. So yes to all of your above questions. it prints the character in message like
I believe my buffer is in line mode. But also it messed up completely with my randr and systray so i think I'm going back to 0.28 for now from GNU repo. |
There's nothing on master that should mess with the systray or randr. Can you open a new issue for those? We're likely going to cut a release pretty soon. |
Specifically, can you open issues in https://github.com/emacs-exwm/exwm/issues. We're going to try to slowly close down issues on this issue tracker. 🙏 |
The problem seems to be with various functions of systray module failing with:
including
This error was preventing (Given that nobody else is reporting this) It might me because while I'm using exwm freshly cloned from github, I'm still using its dependency from elpa and I'm not able to easily remove the dependancies because I have variaous exwm dependant packages install from elpa (exwm-modeline, exwm-edite etc). So maybe I'm not a good tester after all, you probably need someone who doesn't depend so much on elpa to test. Having said, I could start a new issue on that if you think it still makes sense. |
Ah. You need to install |
While working in an EXWM-mode buffer if one clocks in an Org mode task, org consider user being idle and call org-resolve-clocks. This results in EXWM sending all normal keys (like k or i which are needed to deal with org-resolve-clocks) to the EXWM-mode buffer so one can not interact with
org-resolve-clocks
and all EXWM related keys (win+1..7 for example) is being taken byorg-resolve-clocks
so one can not interact with EXWM (to get out of EXWM-mode buffer).The only way out seems to be either quit the app in EXWM buffer (if the app offer a way to do that) or send
abort-recursive-edit
from another tty.The text was updated successfully, but these errors were encountered: