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

[GNU bug Tracking System]

Your message dated Mon, 7 Dec 2020 00:40:02 +0200
with message-id <c172f08b-eb64-9058-6fd6-1c1e15ad0314@yandex.ru>
and subject line Re: bug#16496: 24.3.50; Some completion functions in Emacs 
still return a function of no argument
has caused the debbugs.gnu.org bug report #16496,
regarding 24.3.50; Some completion functions in Emacs still return a function 
of no argument
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
16496: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16496
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> 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@iro.umontreal.ca-20140113153301-ozd3taipkkc7p5cr
> Windowing system distributor `The X.Org Foundation', version 11.0.11405000
> System Description:     Ubuntu 13.10
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> 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
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
>
>
>
>
> On 06.12.2020 16:59, Lars Ingebrigtsen wrote:
> > Dmitry Gutov<dgutov@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!
>
>
> --- End Message ---