Running two frames, A(start frame) and B.
Frame A is a normal Emacs GUI. Frame B is emacsclient -t , i.e. from terminal, with scratch buffer opened.
Upon receiving new email, mu4e is automatically switching the buffer in frame B to mu4e:headers.
This does not happen if frame A is GUI and frame B is also GUI.
Also, if in frame A, GUI window, I only start mu4e and stay in mu4e-main, and frame B is emacsclient -t, i.e. from terminal, the buffer does not switch automatically.
How to Reproduce
Frame A
Start with emacs -Q
Load minimal config to setup inbox
Run (mu4e) and (mu4e-headers-search inbox-query), which fetches full inbox
Frame B
Open a new terminal.
Run emacsclient -t
Send a test email
Wait until mu4e pulls email
Buffer in this frame switches to mu4e:headers buffer
I can reproduce this consistently.
Environment
Fedora 40
GNU Emacs 29.4, no 3rd party extensions
mu-1.12.6
Describe the bug
Running two frames, A(start frame) and B. Frame A is a normal Emacs GUI. Frame B is
emacsclient -t
, i.e. from terminal, with scratch buffer opened. Upon receiving new email, mu4e is automatically switching the buffer in frame B to mu4e:headers.This does not happen if frame A is GUI and frame B is also GUI. Also, if in frame A, GUI window, I only start mu4e and stay in mu4e-main, and frame B is
emacsclient -t
, i.e. from terminal, the buffer does not switch automatically.How to Reproduce
Frame A Start with
emacs -Q
Load minimal config to setup inbox Run(mu4e)
and(mu4e-headers-search inbox-query)
, which fetches full inboxFrame B Open a new terminal. Run
emacsclient -t
Send a test email Wait until mu4e pulls email Buffer in this frame switches to mu4e:headers bufferI can reproduce this consistently.
Environment
Fedora 40 GNU Emacs 29.4, no 3rd party extensions mu-1.12.6