Tomi Ollila <tomi.oll...@iki.fi> writes: > On Mon, May 31 2021, David Bremner wrote: > >> Tomi Ollila <tomi.oll...@iki.fi> writes: >>> >>> I am for 'ripping the bandage off' and not configure mail-user-agent >>> outside of notmuch use (and just require 'notmuch would not set anything...) >>> >>> Could we have some 'compose-mail' variant (different name, of course; >>> I had one in mind but then came off-by one problem... >;) which >>> configures mail-user-agent just for that use (or something). >>> >> >> Are you thinking about notmuch-mua-mail (which exists)? >> >> Tory, did you try the eval-after-load trick I mentioned btw? That seemed >> to work in my testing, and I'm just not sure that customizing a >> notmuch-* variable is much less annoying than adding an eval-after-load to >> reset the variable after notmuch messes with it. >> >> Still waiting for feedback from notmuch users that actually use M-x >> compose-mail or other similar generic entry points. > > Does anyone know how compose-mail behaves when one has loaded any other > emacs mua (mh, vm, gnus, mu, ...) ? >
As far as I can tell vm: only locally binds mail-user-agent mh-e: used to have a setq mail-user-agent, removed in 2003-ish mu4e: documents how to set mail-user-agent rmail: reads mail-user-agent, but does not set gnus: only locally binds mail-user-agent wanderlust: tells you how how to set mail-user-agent (and oddly, how to define conditionaly define a user agent) So I think notmuch is the odd one out here. _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org