Re: Completion functions in message-mode

[Stefan Monnier <monnier@iro.umontreal.ca>]

> message-mode adds message-expand-group and message-tab-body-function to
> `completion-at-point-functions'. Both of these functions check if
> they're in an appropriate location, and bail if not, allowing other
> functions to do their thing.

I think it's OK for Gnus to keep using message-completion-alist, but
message-expand-name should use a completion table which can be extended,
so EUDC, BBDB, ecomplete, and YouNameIt can add themselves to it.

> Packages such as EUDC and BBDB put their own functions in
> `completion-at-point-functions' (in the message-mode hook).

That doesn't sound right: the code which decides if we're inside
a message header, and which header contains email addresses, and how
they're separated (i.e. the code which knows about the format of
messages) should squarely belong to message-mode and not to
BBDB/EUDC/...

Instead these backends should only provide completion tables that
provide user names, email addresses, or such data.

I.e. the completion-at-point-function should come from message.el and
the completion-tables it returns should come from BBDB/EUDC/...


        Stefan