GNU bug report logs - #16496
24.3.50; Some completion functions in Emacs still return a function of no argument

Previous Next

Package: emacs;

Reported by: Dmitry Gutov <dgutov <at> yandex.ru>

Date: Sun, 19 Jan 2014 16:20:01 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3.50

Done: Dmitry Gutov <dgutov <at> yandex.ru>

Bug is archived. No further changes may be made.

Full log


Message #15 received at 16496-done <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16496-done <at> debbugs.gnu.org
Subject: Re: bug#16496: 24.3.50; Some completion functions in Emacs still
 return a function of no argument
Date: Mon, 7 Dec 2020 00:40:02 +0200
On 06.12.2020 16:59, Lars Ingebrigtsen wrote:
> Dmitry Gutov<dgutov <at> yandex.ru>  writes:
> 
>> ...which is officially "discouraged" and doesn't work with company-capf.
>>
>> semantic-completion-at-point-function
>> nxml-completion-at-point-function
> These two no longer exist?
> 
>> message-completion-function
> This was reworked in 47a767c24e9cc4323432e29103b0a2cc46f8f3e4 in 2019,
> so I'm not sure whether this is an issue any more?  (I'm a bit vague
> about how the completion system actually works.)
> 
>> The last one also pops up a BBDB buffer upon successful completion (when
>> BBDB is used, of course), so fixing it might need some additional effort
>> to keep BBDB integration from breaking.
> Is this still an issue after the 2019 rewrite of the function?

Looks like these functions have all been "fixed" indeed.

Thanks for the bump, closing!




This bug report was last modified 4 years and 164 days ago.

Previous Next


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