From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: In-buffer completion of EBDB mail addresses with corfu
Date: Wed, 18 Oct 2023 21:14:18 -0700 [thread overview]
Message-ID: <87bkcv9rl1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2y1fzk7b5.fsf@macmutant.fritz.box>
Arash Esbati <arash@gnu.org> writes:
> Hi all,
>
> almost a year ago, I asked here about using corfu for in-buffer
> completion of mail addresses in BBDB database. I got that working
> somehow, bug now I switched to EBDB (soley because it has a manual ;-)
:)
I believe there are more advantages, but yes this is the primary one.
> and now I have the same problem: Does anybody has a working solution how
> to get in-buffer completion working in Message mode? In a *unsent mail*
> buffer, I want:
>
> To: <Point-here-hit-TAB offers mail addresses with corfu>
>
> It seems EBDB works in general; if I go to the "To: " header and do
>
> M-x edbd-complete-mail RET
>
> I get a *Completions* buffer where I can choose from.
Address completion in message-mode is messy. There are a couple of
different places where EBDB can insinuate itself into the completion
mechanism: the one that happens by default shadows `message-expand-name'
with `ebdb-complete-mail', which runs its own live-search completion
function, you've seen that above.
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!
next prev parent reply other threads:[~2023-10-19 4:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:24 Arash Esbati
2023-10-19 4:14 ` Eric Abrahamsen [this message]
2023-10-19 7:14 ` Arash Esbati
2023-10-19 14:29 ` Eric Abrahamsen
2023-10-20 6:41 ` Arash Esbati
2023-10-20 15:08 ` Eric Abrahamsen
2023-10-21 9:09 ` Arash Esbati
2023-10-21 18:32 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkcv9rl1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).