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?