From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: In-buffer completion of BBDB mail addresses with corfu
Date: Wed, 26 Oct 2022 11:04:09 +0100 [thread overview]
Message-ID: <87r0yulx46.fsf@ucl.ac.uk> (raw)
In-Reply-To: <865yg72bze.fsf@gnu.org>
On Wednesday, 26 Oct 2022 at 11:03, Arash Esbati wrote:
> (setq eudc-server-hotlist '(("localhost" . bbdb)))
I had this already. And, you're right, no need for explicit setting of
eudc-protocol.
I think I need a thorough cleanup of my configuration files as I cannot
get the cap framework to work just as I want it. For message mode
buffers, I will stick to company for the near term.
Thank you,
eric
--
Eric S Fraga via gnus (Emacs 29.0.50 2022-10-25) on Debian 11.4
next prev parent reply other threads:[~2022-10-26 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 14:43 Arash Esbati
2022-10-25 16:04 ` Eric S Fraga
2022-10-26 7:01 ` Arash Esbati
2022-10-26 7:58 ` Eric S Fraga
2022-10-26 9:03 ` Arash Esbati
2022-10-26 10:04 ` Eric S Fraga [this message]
2022-10-26 11:10 ` Arash Esbati
2022-10-26 14:38 ` Eric S Fraga
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=87r0yulx46.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).