From: Julien Cubizolles <j.cubizolles@free.fr>
To: ding@gnus.org
Subject: Re: completion no more working with latest HEADs (emacs and bbdb)
Date: Tue, 31 Jan 2023 13:46:05 +0100 [thread overview]
Message-ID: <878rhieusy.fsf@free.fr> (raw)
In-Reply-To: <86r0vk3y7x.fsf@gnu.org>
Arash Esbati <arash@gnu.org> writes:
> (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))
> (add-to-list 'completion-at-point-functions
> #'eudc-capf-complete)))
I noticed that this setup, while working for bbdb completions in the To: field,
breaks it for completing groups in the Gcc: field.
I get both completions working with:
--8<---------------cut here---------------start------------->8---
(add-hook 'message-mode-hook
(lambda ()
(add-to-list 'completion-at-point-functions
#'eudc-capf-complete)))
--8<---------------cut here---------------end--------------->8---
--
Julien Cubizolles
next prev parent reply other threads:[~2023-02-01 21:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 13:29 Peter Münster
2022-11-15 17:04 ` Peter Münster
2022-11-15 21:31 ` Eric Abrahamsen
2022-11-16 7:48 ` Arash Esbati
2022-11-16 8:46 ` Peter Münster
2022-11-16 8:58 ` Arash Esbati
2022-11-16 10:05 ` Peter Münster
2022-11-16 11:43 ` Arash Esbati
2022-11-16 16:17 ` Eric Abrahamsen
2023-01-23 9:34 ` Julien Cubizolles
2023-01-23 14:05 ` Arash Esbati
2023-01-23 15:22 ` Arash Esbati
2023-01-23 23:14 ` Julien Cubizolles
2023-01-24 12:37 ` Arash Esbati
2023-01-25 21:09 ` Julien Cubizolles
2023-01-27 8:42 ` Arash Esbati
2023-01-27 18:45 ` Eric Abrahamsen
2023-01-31 12:46 ` Julien Cubizolles [this message]
2023-02-02 9:48 ` Arash Esbati
2023-02-03 5:31 ` Julien Cubizolles
2023-02-03 11:04 ` Arash Esbati
2023-02-13 17:29 ` Julien Cubizolles
2023-01-24 8:32 ` Julien Cubizolles
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=878rhieusy.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).