From: webdev@toryanderson.com (Tory S. Anderson)
To: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: do not unconditionally set mail-user-agent
Date: Fri, 14 May 2021 09:22:32 -0600 [thread overview]
Message-ID: <87im3le3wn.fsf@toryanderson.com> (raw)
In-Reply-To: <m2mtsx1j0c.fsf@guru.guru-group.fi> (Tomi Ollila's message of "Fri, 14 May 2021 17:34:43 +0300")
This would be terrific on my account, with that user-agent problem. It seems reasonable to ask Notmuch to NOT mess with global settings unconditionally.
The one thing I wasn't sure about in what I saw of the changes of this patch is where the "conditional" option is. Usually when I've implemented something like this I just create a custom variable and IF that variable is something, then I do the new thing; otherwise do the old thing, thereby maintaining reverse-compatibility. I didn't see that pattern here, I'm not familiar with this medium of code discussion.
I'm not familiar with how the git process goes here, since it's somewhat different than gitlab/github. Is there something I can do to apply this, or is there a separate notification for master, or should I subscribe to a different branch?
- Tory
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Thu, May 13 2021, David Bremner wrote:
>
>> A user that loads notmuch.el does not necessarily want to user
>> notmuch-message-mode to send mail.
>
> If this does not break anything, could be point release content,
> provided it did not ship yet (then to the next sailing ship...).
>
>> ---
>> emacs/notmuch.el | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/emacs/notmuch.el b/emacs/notmuch.el
>> index 6d37c623..3e2713e2 100644
>> --- a/emacs/notmuch.el
>> +++ b/emacs/notmuch.el
>> @@ -1162,8 +1162,6 @@ Point should be at the beginning of the line."
>>
>> ;;; _
>>
>> -(setq mail-user-agent 'notmuch-user-agent)
>> -
>> (provide 'notmuch)
>>
>> ;; After provide to avoid loops if notmuch was require'd via notmuch-init-file.
>> --
>> 2.30.2
>> _______________________________________________
>> notmuch mailing list -- notmuch@notmuchmail.org
>> To unsubscribe send an email to notmuch-leave@notmuchmail.org
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2021-05-14 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 23:28 [PATCH] emacs: do not unconditionally set mail-user-agent David Bremner
2021-05-14 14:34 ` Tomi Ollila
2021-05-14 15:22 ` Tory S. Anderson [this message]
2021-05-15 13:21 ` David Bremner
2021-05-15 13:11 ` David Bremner
2021-06-04 23:16 ` [PATCH] emacs: drop setting mail-user-agent, and document how to set it David Bremner
2021-06-07 15:26 ` Tomi Ollila
2021-06-07 23:30 ` David Bremner
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=87im3le3wn.fsf@toryanderson.com \
--to=webdev@toryanderson.com \
--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).