From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: Utkarsh Singh <utkarsh190601@gmail.com>,
Tomi Ollila <tomi.ollila@iki.fi>,
Notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: Add more front ends for address completion
Date: Mon, 07 Mar 2022 23:14:13 +0100 [thread overview]
Message-ID: <3444ac96512ebdb53fb1faf90a2db263@condition-alpha.com> (raw)
In-Reply-To: <871qzfzgic.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
Utkarsh Singh <utkarsh190601@gmail.com> writes:
> [...]
> I don't think its possible to modify `notmuch-expand-name' into CAPF
> without breaking backward compatibility.
> [...]
See attached.
[-- Attachment #2: patch-notmuch-address.el --]
[-- Type: application/emacs-lisp, Size: 3447 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-03-07 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 14:38 [PATCH] emacs: Add more front ends for address completion Utkarsh Singh
2022-02-09 21:59 ` Tomi Ollila
2022-02-12 16:09 ` Alexander Adolf
2022-02-21 22:20 ` emacs: notmuch-address-command 'as-is throws error (was: [PATCH] emacs: Add more front ends for address completion) Alexander Adolf
2022-02-22 22:04 ` Tomi Ollila
2022-02-28 21:19 ` Alexander Adolf
2022-03-01 17:51 ` Alexander Adolf
2022-02-28 9:01 ` [PATCH] emacs: Add more front ends for address completion Utkarsh Singh
2022-03-06 7:28 ` Utkarsh Singh
2022-03-07 22:14 ` Alexander Adolf [this message]
[not found] ` <87k0d4n8tr.fsf@gmail.com>
[not found] ` <c6c39f1b36844a9160e81f2f23cb8458@condition-alpha.com>
2022-03-09 1:06 ` Utkarsh Singh
2022-03-11 17:50 ` Alexander Adolf
2022-03-13 3:51 ` Utkarsh Singh
2022-03-15 12:37 ` Alexander Adolf
2022-03-17 4:56 ` Utkarsh Singh
2022-03-20 10:49 ` David Bremner
2022-04-06 12:19 ` Utkarsh Singh
2022-04-06 18:23 ` 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=3444ac96512ebdb53fb1faf90a2db263@condition-alpha.com \
--to=alexander.adolf@condition-alpha.com \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
--cc=utkarsh190601@gmail.com \
/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).