Gnus development mailing list
 help / color / mirror / Atom feed
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, 24 Jan 2023 00:14:36 +0100	[thread overview]
Message-ID: <87y1pszvvn.fsf@free.fr> (raw)
In-Reply-To: <86k01dtgw6.fsf@gnu.org>

Arash Esbati <arash@gnu.org> writes:

> Sorry for the confusion, but I have to take back my last proposal;
> `eudc-capf-message-expand-name' works as expected, it is just
> case-sensitive when it comes to TAB-completion.  `bbdb-complete-mail'
> seems to be case-insensitive.
>
> Julien, can you try it again and start typing names exactly as you have
> them in your bbdb file and then hit TAB?

I did several tests, all starting from emacs -Q.

First of all by default 'completion-at-point-functions is set to
(message-completion-function t). With that, TAB completes correctly
incomplete names from bbdb, case insensitive, and offers several
candidates:

with point after "fan" in the To: field, TAB completes to "fanton", and
a second TAB offers to choose between several bbdb entries with the
surname fanton.

In that case the completion is done by 'bbdb-complete-name not
'eudc-expand-inline.


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

fan TAB displays "Multiple matches found: choose one", TAB then offers to
choose between all the bbdb entries with "fan" either in the name, the
email adress. This time, it's 'eudc-expand-inline doing.

The previous attempts were without corfu. With:

--8<---------------cut here---------------start------------->8---
(package-initialize)
(use-package corfu)
(global-corfu-mode)
--8<---------------cut here---------------end--------------->8---

it gets weird. Both 'eudc-expand-inline and 'bbdb-complete-name act as
they did previously but somehow TAB doesn't execute either of them, even
though it's bound to 'message-tab' (according to 'describe-key) and
'message-tab does execute 'bbdb-complete-name' or 'eudc-expand-inline'
as it should.

I checked the value of completion-at-point-functions in message-mode,
and it's set to (message-completion-function t), with no mention of
eudc-capf-message-expand-name.

Following your recipe, I tried:

--8<---------------cut here---------------start------------->8---

(add-hook 'message-mode-hook
          (lambda ()
            (setq-local completion-at-point-functions
                        (delq 'message-completion-function
                              completion-at-point-functions)
			)))
--8<---------------cut here---------------end--------------->8---


and:

--8<---------------cut here---------------start------------->8---
(add-hook 'message-mode-hook
          (lambda ()
            (setq-local completion-at-point-functions
                        (append '(eudc-capf-message-expand-name) (delq 'message-completion-function
                              completion-at-point-functions)
			))))
--8<---------------cut here---------------end--------------->8---

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 hope these tests are what you had in mind and can be of use to
you. Please let me know what else I can try.

Thanks for your help

-- 
Julien Cubizolles



  reply	other threads:[~2023-01-23 23:15 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 [this message]
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
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=87y1pszvvn.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).