From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] EUDC email addresses via completion-at-point in message-mode
Date: Sun, 17 Apr 2022 18:21:51 +0100 [thread overview]
Message-ID: <87czhffwwg.fsf@ucl.ac.uk> (raw)
In-Reply-To: m3zgkjlsln.fsf@fitzsim.org
On Sunday, 17 Apr 2022 at 09:58, Thomas Fitzsimmons wrote:
> Interesting idea of multiple keybindings for different completions.
Yes. The combination works because (a) abbrev is for those very
commonly used addresses so having them expand on , or SPC means no
thought at all, (b) ecomplete shows possibilities as I type so I will
hit M-n if/when I see what I want, and (c) eudc (TAB) works any time to
complete by typing incrementally.
> If EUDC includes the other sources, do you foresee using just EUDC? Or
> do you think keeping the extra keys will give better usability?
Not yet sure; my initial view had been that TAB completion (i.e. via
EUDC) would be what I needed for all cases but I'm actually quite
comfortable with what I've ended up with. However, given that I use tab
completion everywhere else, it probably will be better to have
everything as an option via eudc.
> What do you think the "out-of-the-box" behavior should be? Should the
> following:
>
> "emacs -Q"
> C-x m
> TAB
>
> say "no completions found; to start adding contacts, do <something>".
No, I would expect it to provide all my possible email addresses: union
of bbdb, abbrevs, and ecomplete, just as M-x does for me right now with
selectrum+consult, with most recently used or most popular first.
> (in *scratch*) emacs-devel@gnu.org
> C-x m
> TAB
>
> expand to emacs-devel@gnu.org via dabbrev-expand?
Ummm, interesting. No idea what I would expect!
--
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.3
next prev parent reply other threads:[~2022-04-17 17:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 16:24 [PATCH] EUDC email addresses via completion-at-point in message-mode Alexander Adolf
2022-04-12 21:12 ` Thomas Fitzsimmons
2022-04-13 14:44 ` Alexander Adolf
2022-04-14 0:26 ` Thomas Fitzsimmons
2022-04-15 21:23 ` Alexander Adolf
2022-04-14 13:02 ` Eric S Fraga
2022-04-14 13:27 ` Thomas Fitzsimmons
2022-04-14 13:52 ` Eric S Fraga
2022-04-15 21:39 ` Alexander Adolf
2022-04-17 12:12 ` Eric S Fraga
2022-04-15 21:35 ` Alexander Adolf
2022-04-17 12:20 ` Eric S Fraga
2022-04-17 13:58 ` Thomas Fitzsimmons
2022-04-17 17:21 ` Eric S Fraga [this message]
2022-04-14 14:02 ` Stefan Monnier
2022-04-15 21:58 ` Alexander Adolf
2022-04-15 22:57 ` Eric Abrahamsen
2022-04-14 1:44 ` Eric Abrahamsen
2022-04-14 13:04 ` Eric S Fraga
2022-04-14 15:17 ` Eric Abrahamsen
2022-04-14 15:26 ` Stefan Monnier
2022-04-15 16:31 ` Eric Abrahamsen
2022-04-15 17:17 ` Stefan Monnier
2022-04-15 22:30 ` Alexander Adolf
2022-04-15 22:16 ` Alexander Adolf
2022-04-15 22:58 ` Stefan Monnier
2022-04-26 14:39 ` Alexander Adolf
2022-04-26 18:58 ` Filipp Gunbin
2022-04-28 17:15 ` Alexander Adolf
2022-04-29 14:43 ` Thomas Fitzsimmons
2022-05-02 17:10 ` Alexander Adolf
2022-05-03 18:03 ` Thomas Fitzsimmons
2022-05-05 16:32 ` Alexander Adolf
2022-05-05 16:57 ` Thomas Fitzsimmons
2022-05-10 21:16 ` Thomas Fitzsimmons
2022-05-16 12:35 ` Alexander Adolf
2022-04-29 23:04 ` Filipp Gunbin
2022-05-02 21:38 ` Alexander Adolf
2022-05-02 22:32 ` Filipp Gunbin
2022-05-03 16:18 ` Alexander Adolf
2022-05-03 16:22 ` Alexander Adolf
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=87czhffwwg.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-devel@gnu.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.
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).