Gnus development mailing list
 help / color / mirror / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: ding@gnus.org
Subject: Re: completion no more working with latest HEADs (emacs and bbdb)
Date: Tue, 24 Jan 2023 13:37:22 +0100	[thread overview]
Message-ID: <86r0vk3y7x.fsf@gnu.org> (raw)
In-Reply-To: <87y1pszvvn.fsf@free.fr> (Julien Cubizolles's message of "Tue, 24 Jan 2023 00:14:36 +0100")

Julien Cubizolles <j.cubizolles@free.fr> writes:

> The first one sets completion-at-point-functions to t, and the second
> one sets it to (eudc-capf-message-expand-name t). Both fail to use a
> corfu completion menu when using TAB on "fan" and go back to the
> dialogues previously provided if I'm using (bbdb-complete-name) or
> (eudc-expand-inline).

I can more or less reproduce what you described about
`bbdb-complete-name' and others.  With Corfu, this is my entire
configuration:

(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)))

Note that the function is called `eudc-capf-complete' which in return
calls `eudc-capf-message-expand-name' after some checks.  With this
setup, Corfu works here and I can hit TAB to get in-buffer completion
for names from BBDB.  The only thing I have to do is being
case-sensitive reg. the names I'm typing.

I hope this helps you get your system running as well.

Best, Arash


  reply	other threads:[~2023-01-24 12:38 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 [this message]
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
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=86r0vk3y7x.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=ding@gnus.org \
    --cc=j.cubizolles@free.fr \
    /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).