Re: In-buffer completion of EBDB mail addresses with corfu

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Arash Esbati <arash@gnu.org> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> The other option is to set (the variable) `ebdb-complete-mail' to the
>> symbol 'capf. This will put a pre-defined list of "name <email>" strings
>> into the completion-at-point-functions hook. Then TAB should offer those
>> strings for completion, using corfu.
>>
>> The search is less powerful because it doesn't use a dynamic lookup, but
>> it should still be fine to use.
>>
>> Let me know how that works!
>
> Thanks for your response.  I added
>
>   (setq ebdb-complete-mail 'capf)
>
> to my .gnus, but I think this is not enough.  IIUC, I need:
>
>   (setq ebdb-complete-mail 'capf)
>   (require 'ebdb-message)
>
> Then this is the value of `completion-at-point-functions' in this
> buffer:
>
>   completion-at-point-functions is a variable defined in ‘minibuffer.el’.
>
>   Its value is
>   (ebdb-mail-dwim-completion-at-point-function
>    message-completion-function t)
>
> Now I hit 'C-c C-f C-t' and enter ', TAB' after your "name <email>" and
> get some space added with "No match" in the echo area.  So it doesn't
> seem to work.  Or am I missing something?

I'm not completely clear what you're doing here -- you enter a full name
and email, then a comma, then TAB? EBDB will only look back as far as
the nearest comma for completion. In this case it will send in a blank
string, which should offer all emails in your EBDB database for
completion. Have you created any records? Are there strings in
`ebdb-dwim-completion-cache'?

> And while we're at it: I suggest to autoload the functions
> `ebdb-insinuate-message', `ebdb-insinuate-mail' and
> `ebdb-message-auto-update' and let users add things like:
>
>   (add-hook 'message-mode-hook #'ebdb-insinuate-message)
>   (add-hook 'message-send-hook #'ebdb-message-auto-update)
>
>   (add-hook 'mail-setup-hook #'ebdb-insinuate-mail)
>   (add-hook 'mail-send-hook #'ebdb-message-auto-update)
>
> to their init file, depending on what they're using.

That's not a bad idea. Having them `require' libraries to activate
behavior isn't very Emacsy. That would be a pretty annoying change for
existing users, though...