unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Utkarsh Singh <utkarsh190601@gmail.com>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: Notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: Add more front ends for address completion
Date: Sun, 13 Mar 2022 09:21:34 +0530	[thread overview]
Message-ID: <87ee36v7ax.fsf@gmail.com> (raw)
In-Reply-To: <ab30e4e280cc59569101a74fa73cbf36@condition-alpha.com>

On 2022-03-11, 18:50 +0100, Alexander Adolf <alexander.adolf@condition-alpha.com> wrote:

> Utkarsh Singh <utkarsh190601@gmail.com> writes:
>
>> On 2022-03-08, 16:29 +0100, Alexander Adolf <alexander.adolf@condition-alpha.com> wrote:
>>
>>> Utkarsh Singh <utkarsh190601@gmail.com> writes:
>>>
>>>> [...]
>>>> `notmuch-address-post-completion-functions'.
>>>> [...]
>>> [...]
>> Although its a general customization option, here its documentation from
>> company.el:
>>      
>>      `post-completion': Called after a completion candidate has been inserted
>>      into the buffer.  The second argument is the candidate.  Can be used to
>>      modify it, e.g. to expand a snippet.
>> [...]
>
> Hm, that sounds like it would functionally be similar to specifying an
> :exit-function property in completion-extra-properties?

Great!  We can definitely work with this.

> And what could be a use-case for this?

Honestly, I don't have a use-case.  But the goal here is to use standard
Emacs API with least amout of incompatible changes.

-- 
Utkarsh Singh
https://utkarshsingh.xyz/

  reply	other threads:[~2022-03-13  3:55 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
     [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 [this message]
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=87ee36v7ax.fsf@gmail.com \
    --to=utkarsh190601@gmail.com \
    --cc=alexander.adolf@condition-alpha.com \
    --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).