[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16496: 24.3.50; Some completion functions in Emacs still return a fu
From: |
Lars Ingebrigtsen |
Subject: |
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 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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
- bug#16496: 24.3.50; Some completion functions in Emacs still return a function of no argument,
Lars Ingebrigtsen <=