Yes, I'm getting the same behaviour as you on the buffer switching. >From my brief testing, it seems that the problem is fixed by making the obvious change in these lines in mu4e-main.el:
(defconst mu4e~main-buffer-name " *mu4e-main*" "*internal* Name of the mu4e main view buffer.") Dirk? On Tuesday, August 12, 2014 7:30:09 PM UTC-4, Alexis wrote: > > > Brett Presnell writes: > > > I tried to figure this out some time ago and failed. It will probably > > be obvious to someone here. > > > > When I run either list-buffers or ibuffer, the *mu4e-main* buffer does > > not show up. Buffers with mode mu4e-headers-mode, mu4e-view-mode, and > > mu4e-compose-mode all show up fine, but not mu4e-main-mode. Why, and > > what can I do to fix this? > > In my experience, buffers with a leading space in their name don't get > displayed in user-facing buffer lists; and from a quick test here, my > *mu4e-main* buffer /does/ have a leading space in the name (i.e. its > buffer-name is " *mu4e-main"). To check if this is the case in your own > setup, call the switch-to-buffer command twice, first specifying > *mu4e-main* with, and then without, a leading space. The former should > get you the mu4e main buffer, whereas the latter will probably display > an empty buffer. > > Not sure how to change this behaviour, though! > > > Alexis. > -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
