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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16496 in the body.
You can then email your comments to 16496 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50;
 Some completion functions in Emacs still return a function of no
 argument
Date: Sun, 19 Jan 2014 18:19:08 +0200

...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 monnier <at> iro.umontreal.ca-20140113153301-ozd3taipkkc7p5cr
Windowing system distributor `The X.Org Foundation', version 11.0.11405000
System Description:	Ubuntu 13.10

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 16496 <at> debbugs.gnu.org
Subject: Re: bug#16496: 24.3.50; Some completion functions in Emacs still
 return a function of no argument
Date: Sun, 06 Dec 2020 15:59:40 +0100

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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!

Previous Next

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