Gnus development mailing list
 help / color / mirror / Atom feed
From: Arash Esbati <arash@gnu.org>
To: ding@gnus.org
Subject: Re: In-buffer completion of BBDB mail addresses with corfu
Date: Wed, 26 Oct 2022 13:10:06 +0200	[thread overview]
Message-ID: <8635bazvqp.fsf@gnu.org> (raw)
In-Reply-To: <87r0yulx46.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 26 Oct 2022 11:04:09 +0100")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> 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.

Thanks for checking.

> 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.

Just to wrap this up, this is what I'm doing now:

  (setq eudc-server-hotlist '(("localhost" . bbdb)))

  (add-hook 'message-mode-hook
            (lambda ()
              (setq-local completion-at-point-functions
                          (delq 'message-completion-function
                                completion-at-point-functions))))

A strange *complition* buffer popped up for me after the first
completion in the header field, so I remove
`message-completion-function' from `completion-at-point-functions'.  I
didn't try to find out why, maybe later.

Best, Arash


  reply	other threads:[~2022-10-26 11:10 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
2022-10-26 11:10           ` Arash Esbati [this message]
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=8635bazvqp.fsf@gnu.org \
    --to=arash@gnu.org \
    --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).