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: Fri, 03 Feb 2023 12:04:29 +0100 [thread overview]
Message-ID: <86o7qbau2q.fsf@gnu.org> (raw)
In-Reply-To: <874js3tiv6.fsf@free.fr> (Julien Cubizolles's message of "Fri, 03 Feb 2023 06:31:41 +0100")
Julien Cubizolles <j.cubizolles@free.fr> writes:
> Arash Esbati <arash@gnu.org> writes:
>
>> So you have to tweak the regexp to something like this:
>>
>> "^\\([^ :]*-\\)?\\(To\\|[BG]?Cc\\|From\\|Reply-to\\|Mail-Followup-To\\|Mail-Copies-To\\):"
>
> I understand that this would attempt to use eudc-capf-complete in the
> Gcc field but it wouldn't get a match with the gnus group name since
> it's supposed to look for email addresses, right ?
I didn't test the suggestion above, so chances are high that it breaks
other things.
> Also, do you need to remove 'message-completion-function from
> completion-at-point-functions to get eudc-capf-completion to work ? In
> my case this is not necessary.
The main reason for me to remove `message-completion-function' was that
it kicked in without asking (i.e., hitting TAB and such) and raised a
completion buffer where I wanted in-buffer completion. I didn't dig
deeper to find out why. I just removed it and it worked for me.
In summary, I think the behavior of `eudc-capf-complete' was improved in
the bug report mentioned by Eric, and the original problem is solved.
But I still have to keep my setup because of the other issue mentioned
above.
Best, Arash
next prev parent reply other threads:[~2023-02-03 11:05 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
2023-02-02 9:48 ` Arash Esbati
2023-02-03 5:31 ` Julien Cubizolles
2023-02-03 11:04 ` Arash Esbati [this message]
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=86o7qbau2q.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).