Re: [PATCH] EUDC email addresses via completion-at-point in message-mode

[Thomas Fitzsimmons]

Hi Alexander,

Alexander Adolf <alexander.adolf@condition-alpha.com> writes:

> when switching to a new in-buffer completion user interface package
> which is solely based on completion-at-point, I observed that email
> address completion in message-mode happens in the minibuffer, regardless
> of what UI on top of completion-at-point I use. Also, EUDC's ability to
> aggregate search results from several servers, which was recently added
> with commit 0470a4a939772c4bd25123b15f5eadab41f8bee5, was not kicking
> in, i.e. I was presented results from a single EUDC server only.

I tested this patch with my current setup, and it doesn't break
anything, however I'm not using completion-at-point yet, see below.

Is there a way to implement eudc-capf-complete such that it doesn't need
eudc-capf-modes?  I don't like the fact that eudc-capf-modes would need
to be updated every time a new mode wants to use eudc-capf-complete.
What would go wrong if you just omitted the mode check?  (Maybe I'm
missing something about completion-at-point's design here.)

Can you add an example in message-mode's manual, for how to make use of
completion-at-point, even if it means mentioning a specific
completion-at-point UI package?

Currently I use:

     (with-eval-after-load "message"
       (define-key message-mode-map
        [(control ?c) (tab)]
        'eudc-expand-try-all))

as per the EUDC manual.  I shouldn't need that anymore with this patch,
correct?  What completion-at-point UI package should I install in order
to test this?

Thanks,
Thomas