* bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument
@ 2014-01-19 16:19 Dmitry Gutov
2020-12-06 14:59 ` Lars Ingebrigtsen
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Gutov @ 2014-01-19 16:19 UTC (permalink / raw)
To: 16496
...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
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument
2014-01-19 16:19 bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument Dmitry Gutov
@ 2020-12-06 14:59 ` Lars Ingebrigtsen
2020-12-06 22:40 ` Dmitry Gutov
0 siblings, 1 reply; 3+ messages in thread
From: Lars Ingebrigtsen @ 2020-12-06 14:59 UTC (permalink / raw)
To: Dmitry Gutov; +Cc: 16496
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?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument
2020-12-06 14:59 ` Lars Ingebrigtsen
@ 2020-12-06 22:40 ` Dmitry Gutov
0 siblings, 0 replies; 3+ messages in thread
From: Dmitry Gutov @ 2020-12-06 22:40 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 16496-done
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!
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-12-06 22:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-19 16:19 bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument Dmitry Gutov
2020-12-06 14:59 ` Lars Ingebrigtsen
2020-12-06 22:40 ` Dmitry Gutov
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).