-
Notifications
You must be signed in to change notification settings - Fork 14
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
Split window X application windows #22
Comments
I can confirm. It should leave the X window behind. I'm guessing this is a "time of check" bug in the EXWM focusing logic. If you run |
Thanks, I've updated my personal function. If anyone's interested I've changed it to the following.
I can see this issue potentially cropping up again with anyone trying manipulate windows quickly, Ill close this as completed for now. EDIT: use this instead;
|
Awesome! But this is definitely a bug so I'm going to leave it open till we can fix it. |
This might save you 100ms : ch11ng/exwm#685 (comment) |
Thank you, I've updated the function with the redisplay workaround |
The issue I have currently is that when running my interactive function to split a window and then switch to the other window it seems to flip the buffers and keep the focus on the original X window.
The function doesn't do anything crazy, its just does what I would normally do with 2 keybindings but in one. The funny thing is if I run these two commands using
M-x split-window-* RET
andM-x other-window RET
it works how you would expect it.Also other function such as 'find-file-other-window' work fine when focused on an X Application.
I've used other split window function in place but all seem to have the same issue.
(F) = user focus
Understandably you cant have two windows of the same X application but the movement of the window should be the same as any other buffer?
Currently I've fixed this 'issue' my amending the function to check the major mode an act accordingly. Annoyingly I have to now switch to the other window myself, oh the horror!.
The text was updated successfully, but these errors were encountered: