unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Tory S. Anderson" <webdev@toryanderson.com>
To: David Bremner <david@tethera.net>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: PATCH [1/2] mail user agent
Date: Thu, 03 Jun 2021 09:15:09 -0600	[thread overview]
Message-ID: <87lf7r569u.fsf@toryanderson.com> (raw)
In-Reply-To: <87r1hjjg45.fsf@tethera.net> (David Bremner's message of "Thu, 03 Jun 2021 09:18:50 -0300")

Nice follow-upabout what other browsers do!

David Bremner <david@tethera.net> writes:

> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> On Mon, May 31 2021, David Bremner wrote:
>>
>>> Tomi Ollila <tomi.ollila@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.

No, I'm guilty here. I used my patch instead and haven't looked back since. I think having to add code lines to an init file is much more annoying (and less transparent) than simply having something for which I can add a =:custom= line in my use-package statements, or new users just use the customizer to explore to. Maybe that's just me, but I feel much more comfortable about sharing that config or that suggestion with others, too. Explorability is what customizer's big benefit to emacs is, so it seems to me a real advantage to have this in there. 

>>>
>>> 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-leave@notmuchmail.org

  reply	other threads:[~2021-06-03 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 16:03 [PATCH] emacs: PATCH [1/2] mail user agent Tory S. Anderson
2021-05-22 12:16 ` David Bremner
2021-05-22 13:28   ` Tomi Ollila
2021-05-22 15:38     ` Tory S. Anderson
2021-05-31 23:33     ` David Bremner
2021-06-02 19:10       ` Tomi Ollila
2021-06-03 12:18         ` David Bremner
2021-06-03 15:15           ` Tory S. Anderson [this message]
2021-06-03 18:22             ` Tomi Ollila

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lf7r569u.fsf@toryanderson.com \
    --to=webdev@toryanderson.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).