GNU bug report logs - #73234
30.0.91; completion-preview-mode doesn't trigger for case-insensitive capf

Previous Next

Full log

Message #41 received at 73234 <at> debbugs.gnu.org (full text, mbox):

From: Eshel Yaron <me <at> eshelyaron.com>
To: Morgan Willcock <morgan <at> ice9.digital>
Cc: 73234 <at> debbugs.gnu.org
Subject: Re: bug#73234: 30.0.91; completion-preview-mode doesn't trigger for
 case-insensitive capf
Date: Fri, 20 Sep 2024 12:34:47 +0200

Morgan Willcock <morgan <at> ice9.digital> writes:

> Eshel Yaron <me <at> eshelyaron.com> writes:
>
>> If :exit-function doesn't work for your use case, please explain why,
>> and if there's indeed a need for another hook, it's easy to add one :)
>
> My reasons for not using :exit-function would be:

Thanks, these make sense.

> - If the completion was inserted using a different interface then the
>   function would be running unnecessarily.

Right, although this needn't be significant in terms of performance.

> - For completion functions that I didn't write, :exit-function isn't
>   going to be set with the expectation that a particular completion
>   interface and case preference is used to insert the candidate.

The idea is that you use a capf wrapper that adds the :exit-function,
when needed, like cape-capf-case-fold in your example.

> That said, I am just trying to think of an easy mechanism to preserve
> the case of the candidate.  A hook may generally be useful, but adding a
> hook does not solve the underlying problem that I am describing here.
>
> Perhaps it is best to just pause for the moment while you get additional
> feedback from other users.

All right, let me know if you have further thoughts or a potential patch,
and thank you for your engagement!


Best,

Eshel

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.