Utkarsh Singh writes:
>>
>> Can you be more precise about what you are asking / proposing here?
>> Assume I only skimmed the thread.
>
> Currently, notmuch-address.el, the library used to generate completion
> candidates for recipient's addresses in Notmuch's message compostion
> mode uses
Hello David,
First of all, apologies for the late reply. It would have been much
better if Alexander could himself purposed the solution he is developing.
On 2022-03-20, 07:49 -0300, David Bremner wrote:
> Utkarsh Singh writes:
>
>> Thank you for working on this issue. But from now, its up
Utkarsh Singh writes:
> Thank you for working on this issue. But from now, its up to Notmuch
> maintainers to decide whether or not they want any improvements in
> `notmuch-address.el'.
Can you be more precise about what you are asking / proposing here?
Assume I only skimmed the thread.
d
On 2022-03-15, 13:37 +0100, Alexander Adolf
wrote:
> Utkarsh Singh writes:
>
>> [...]
`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.
Utkarsh Singh writes:
> [...]
>>> `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
On 2022-03-11, 18:50 +0100, Alexander Adolf
wrote:
> Utkarsh Singh writes:
>
>> On 2022-03-08, 16:29 +0100, Alexander Adolf
>> wrote:
>>
>>> Utkarsh Singh writes:
>>>
[...]
`notmuch-address-post-completion-functions'.
[...]
>>> [...]
>> Although its a general customization
Utkarsh Singh writes:
> On 2022-03-08, 16:29 +0100, Alexander Adolf
> wrote:
>
>> Utkarsh Singh writes:
>>
>>> [...]
>>> `notmuch-address-post-completion-functions'.
>>> [...]
>> [...]
> Although its a general customization option, here its documentation from
> company.el:
>
>
On 2022-03-08, 16:29 +0100, Alexander Adolf
wrote:
> Utkarsh Singh writes:
>
>> [...]
>> `notmuch-address-post-completion-functions'.
>> [...]
>
> Showing off my lack of understanding: What are they for, and why do we
> need to run something _after_ completion appears to have already
>
Utkarsh Singh writes:
> [...]
> I don't think its possible to modify `notmuch-expand-name' into CAPF
> without breaking backward compatibility.
> [...]
See attached.
patch-notmuch-address.el
Description: application/emacs-lisp
___
notmuch mailing
Hi,
On 2022-02-28, 14:31 +0530, Utkarsh Singh wrote:
> Currently I'm trying to prepare a patch which will remove all Company
> specific calls with standard Emacs API. For now, evaluate the following
> expression to review the user-side changes:
I don't think its possible to modify
Alexander Adolf writes:
> [...]
> Variant 2 "core Emacs":
> [...]
It was not as much work as I had anticipated, and hence here is a first
sketch of the idea:
patch-notmuch-address.el
Description: application/emacs-lisp
Some further cleanup to remove all company stuff from notmuch-address.el
Tomi, apologies for the delay in getting back to you. I'm moving office,
so had a couple of other chores for having fun with. ;-)
Tomi Ollila writes:
> [...]
>> In case not, how can I prevent modification of message-completion-alist
>> by notmuch, and still have notmuch use the 'internal
Hello Alexander,
On 2022-02-12, 17:09 +0100, Alexander Adolf
wrote:
> Tomi Ollila writes:
>
>> On Tue, Feb 08 2022, Utkarsh Singh wrote:
>>
>>> [...]
>>> Corfu enhances the default completion in region function with a
>>> completion overlay. The current candidates are shown in
On Mon, Feb 21 2022, Alexander Adolf wrote:
> Alexander Adolf writes:
>
>> [...]
>> Hence, from my personal point of view, moving _all_ completion to go
>> through completion-at-point-functions seems the only reasonable way
>> forward.
>>
>> That would remove any special cases for when company
Alexander Adolf writes:
> [...]
> Hence, from my personal point of view, moving _all_ completion to go
> through completion-at-point-functions seems the only reasonable way
> forward.
>
> That would remove any special cases for when company is available from
> the elisp. Fewer third-party
On Fri, Feb 11 2022, Utkarsh Singh wrote:
> On 2022-02-10, 19:37 +0200, Tomi Ollila wrote:
>
>>
>> When doing in notmuch repo, one can execute ./devel/try-emacs-mua -Q
>>
>> ... which probably uses the same package database (under $HOME) as any
>> other emacs invocation would do -- what is the
Tomi Ollila writes:
> On Tue, Feb 08 2022, Utkarsh Singh wrote:
>
>> [...]
>> Corfu enhances the default completion in region function with a
>> completion overlay. The current candidates are shown in a popup
>> below or above the point. Corfu is the minimalistic
>>
On 2022-02-10, 19:37 +0200, Tomi Ollila wrote:
> On Thu, Feb 10 2022, Utkarsh Singh wrote:
>
>> Start of forwarded message
>> From: Utkarsh Singh
>> To: Tomi Ollila
>> Subject: Re: [PATCH] emacs: Add more front ends for a
On Thu, Feb 10 2022, Utkarsh Singh wrote:
> Start of forwarded message
> From: Utkarsh Singh
> To: Tomi Ollila
> Subject: Re: [PATCH] emacs: Add more front ends for address completion
> Date: Thu, 10 Feb 2022 08:58:49 +0530
>
> He
Start of forwarded message
From: Utkarsh Singh
To: Tomi Ollila
Subject: Re: [PATCH] emacs: Add more front ends for address completion
Date: Thu, 10 Feb 2022 08:58:49 +0530
Hello Tomi,
On 2022-02-09, 23:59 +0200, Tomi Ollila wrote:
> On Tue, Feb
this is not simple to solve, as this otherwise fine
change would indicate :/
Tomi
>
> Thank you,
> Utkarsh Singh
> --
> Utkarsh Singh
> https://utkarshsingh.xyz/
> From fdc88b81fef763f7d7dcdc899aa8e90482c574fa Mon Sep 17 00:00:00 2001
> From: Utkarsh Singh
> Date: Tue, 8
that existing users can enjoy existing completion techniques.
Thank you,
Utkarsh Singh
--
Utkarsh Singh
https://utkarshsingh.xyz/
>From fdc88b81fef763f7d7dcdc899aa8e90482c574fa Mon Sep 17 00:00:00 2001
From: Utkarsh Singh
Date: Tue, 8 Feb 2022 19:17:26 +0530
Subject: [PATCH] emacs: Add more fr
22 matches
Mail list logo
