-
Notifications
You must be signed in to change notification settings - Fork 118
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
Fix and simplify detection of selected window #134
base: master
Are you sure you want to change the base?
Conversation
Remove the stack of minibuffer selected windows. Instead consider (minibuffer-selected-window) the selected window whenever (selected-window) is a minibuffer. This seems to be consistent with what Emacs considers the selected window when choosing the mode line face. Also update all mode lines whenever a new window is selected, as either the previously or the newly selected window would in some cases not update, resulting in either two or zero windows apparently selected. Fixes milkypostman#120
Any chance this can be merged? |
That looks to me like a different bug in the particular theme you are using. |
It happens with the default powerline theme as well. |
Same display bug on Windows 10, by the way: |
@manuel-uberti does this fix your problem? |
As reported above, it didn't. Although I haven't tried in a while since I move to a custom mode line and a different theme. :) |
Remove the stack of minibuffer selected windows. Instead consider
(minibuffer-selected-window) the selected window whenever
(selected-window) is a minibuffer. This seems to be consistent with
what Emacs considers the selected window when choosing the mode line
face.
Also update all mode lines whenever a new window is selected, as
either the previously or the newly selected window would in some cases
not update, resulting in either two or zero windows apparently selected.
Fixes #120
I've tested this using Emacs 24.5. Moving between frames and windows including nested minibuffers I couldn't find any inconsistencies.