Subject: bug#16496: closed (Re: bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 06 Dec 2020 22:41:01 +0000

Your bug report

#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
16496: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16496
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument
From: Dmitry Gutov <[email-masked]>
To: Lars Ingebrigtsen <[email-masked]>
Cc: [email-masked]
Date: Mon, 7 Dec 2020 00:40:02 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

On 06.12.2020 16:59, Lars Ingebrigtsen wrote:
> Dmitry Gutov<[email-masked]>  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!

Subject: 24.3.50; Some completion functions in Emacs still return a function of no argument
From: Dmitry Gutov <[email-masked]>
To: [email-masked]
Date: Sun, 19 Jan 2014 18:19:08 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

...which is officially "discouraged" and doesn't work with company-capf.

semantic-completion-at-point-function
nxml-completion-at-point-function
message-completion-function

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.

In GNU Emacs 24.3.50.3 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.6)
 of 2014-01-13 on axl
Repository revision: 116011 [email-masked]
Windowing system distributor `The X.Org Foundation', version 11.0.11405000
System Description:	Ubuntu 13.10