unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: djcb.bulk@gmail.com, emacs-devel@gnu.org, eric@ericabrahamsen.net
Subject: Re: message-mode completion broken
Date: Wed, 16 Nov 2022 15:30:44 +0200	[thread overview]
Message-ID: <83cz9ngh6j.fsf@gnu.org> (raw)
In-Reply-To: <878rkbcj4z.fsf@gmail.com> (message from Robert Pluim on Wed, 16 Nov 2022 11:02:04 +0100)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org, Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Wed, 16 Nov 2022 11:02:04 +0100
> 
> >>>>> On Wed, 16 Nov 2022 10:16:57 +0200, "Dirk-Jan C. Binnema" <djcb.bulk@gmail.com> said:
> 
>     Dirk-Jan> On Tuesday Nov 15 2022, Eric Abrahamsen wrote:
> 
>     >> Hi,
>     >> 
>     >> Since the recent change to message-mode and EUDC, message-mode
>     >> completion fails. I noticed this with EBDB, and there's been a report on
>     >> gnus.general that BBDB fails as well.
>     >> 
>     >> completion-at-point-functions looks like:
>     >> 
>     >> (eudc-capf-complete message-completion-function t)
>     >> 
>     >> eudc-capf-complete produces "No matches", and
>     >> message-completion-function never gets called.
> 
>     Dirk-Jan> We ran into that same problems with mu4e's completion:
>     Dirk-Jan>   https://github.com/djcb/mu/issues/2363
> 
> Please report this as a bug with M-x report-emacs-bug

Yes, and preferably with a recipe that doesn't require 3rd-party
packages to reproduce the problems.

TIA



  reply	other threads:[~2022-11-16 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 21:38 message-mode completion broken Eric Abrahamsen
2022-11-16  8:16 ` Dirk-Jan C. Binnema
2022-11-16 10:02   ` Robert Pluim
2022-11-16 13:30     ` Eli Zaretskii [this message]
2022-11-16 14:16 ` Thomas Fitzsimmons
2022-11-16 17:59   ` Eric Abrahamsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83cz9ngh6j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=djcb.bulk@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=rpluim@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).