You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The setting mu4e-views-next-previous-message-behaviour doesn't work for me, the focus of mu4e always switches to the message view after changing the email (by pressing n or p). However, I want it to stay focused on the header view. I tried both stick-to-current-window and always-switch-to-headers, but the behaviour didn't change.
I'm currently using Emacs 27.2. If you need additional information, please let me know.
The text was updated successfully, but these errors were encountered:
Hi, are you happen to use linux? If yes, it seems that the xwidget always captures focus when browsing a new http doc (email). If that is the case, then currently, I don't think there is anything I could do about that except maybe for a dirty hack that runs a timer and then switches to the headers view.
Hi, yes, I forgot to mention that I'm using Manjaro Linux, so that would explain the issue. Too bad, but if it's a problem with xwidget then it's probably best to wait for an upstream fix. For now, I'll simply use “y” to change focus manually if I need it. I fear, the workaround with the timer might be confusing, if the focus changes from the headers to the mail and back to the header.
yes, that would be a mess, especially since there is good choice for how long the timer would run so sometimes it would switch after another user interaction and sometimes too early when loading the html in xwidgets takes longer.
The setting
mu4e-views-next-previous-message-behaviour
doesn't work for me, the focus of mu4e always switches to the message view after changing the email (by pressing n or p). However, I want it to stay focused on the header view. I tried bothstick-to-current-window
andalways-switch-to-headers
, but the behaviour didn't change.I'm currently using Emacs 27.2. If you need additional information, please let me know.
The text was updated successfully, but these errors were encountered: