From: Shea Levy <shea@shealevy.com>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/4] Allow specifying alternate names for addresses in other_email
Date: Sun, 14 Aug 2016 08:43:47 -0400 [thread overview]
Message-ID: <87oa4vtta4.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k2fk98yh.fsf@nikula.org>
Hi Jani,
Jani Nikula <jani@nikula.org> writes:
> On Tue, 09 Aug 2016, Shea Levy <shea@shealevy.com> wrote:
>> Currently, while notmuch-reply will recognize email addresses other than
>> the main address with user.other_email, it always sets the name part of
>> the address in the envelope-from and From headers to user.name. This
>> patchset enables specifying names on a per-address basis with a new
>> user.other_name property. Presumably other users of user.other_email
>> may want to use this as well, but those are not updated currently.
>
> I am not convinved by adding another configuration option, especially
> when it has to be in sync with another configuration option (ordering in
> user.other_name having to match user.other_email). I would much prefer
> allowing (but not requiring) "Name <user@example.org>" style addresses
> both in user.primary_email and user.other_email.
>
This would be fine with me. Is there already code in place to separate
out the name and email values from that kind of email address?
>
> With a cursory glance at the implementation, I wonder if you could just
> pick the name based on the address you've picked earlier, and leave the
> address matching mostly as it is. Would save some passing of parameters
> around. Maybe.
>
Hmm, I'm not sure what you mean by this, sorry. Can you expand?
>
> Additionally, I'd very much like to have my series [1] merged
> first. It'll be *much* easier to rebase your series on top than the
> other way around...
>
Happy to rebase my work on yours.
>
> BR,
> Jani.
>
>
> [1] id:cover.1471088022.git.jani@nikula.org
next prev parent reply other threads:[~2016-08-14 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 20:55 [PATCH 0/4] Allow specifying alternate names for addresses in other_email Shea Levy
2016-08-09 20:55 ` [PATCH 1/4] Add user.other_name property to associate names with other_email Shea Levy
2016-08-09 20:55 ` [PATCH 2/4] notmuch-reply: respect users.other_name in From Shea Levy
2016-08-09 20:55 ` [PATCH 3/4] Add documentation for user.other_name Shea Levy
2016-08-09 20:55 ` [PATCH 4/4] Update NEWS " Shea Levy
2016-08-13 11:58 ` [PATCH 0/4] Allow specifying alternate names for addresses in other_email Jani Nikula
2016-08-14 12:43 ` Shea Levy [this message]
2016-08-14 13:35 ` Jani Nikula
2016-08-14 13:45 ` Jani Nikula
2016-08-18 10:52 ` 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=87oa4vtta4.fsf@shlevy-laptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=shea@shealevy.com \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/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).