From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Phil Sainty <psainty@orcon.net.nz>
Cc: "53935@debbugs.gnu.org" <53935@debbugs.gnu.org>
Subject: bug#53935: [External] : bug#53935: 27.2; [PATCH] ecomplete.el: Auto-select when there is only a single option
Date: Sun, 13 Feb 2022 17:24:18 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488EEA4FE13CA08C64F5550F3329@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87v8xjyyi3.fsf@gnus.org>
> > I probably didn't pick a good name for the option, though. In
> > hindsight something like `ecomplete-display-matches-auto-choose' is
> > probably better. Or `ecomplete-display-matches-choose-dwim', given
> > that it's a DWIM-ish behaviour?
>
> The latter sounds better to me.
FWIW:
1. Icicles has had such an option since 2007:
`icicle-top-level-when-sole-completion-flag'
Non-nil means to return to top level if only
one matching completion. The sole completion
is accepted.
And there's a companion option:
`icicle-top-level-when-sole-completion-delay'
Number of secs to wait to return to top level
if only one completion. This has no effect if
`icicle-top-level-when-sole-completion-flag' is
nil. Editing the completion (typing or deleting
a character) before the delay expires prevents
its automatic acceptance.
Do not set this to 0.0. Set it to slightly
more than zero if you want instant action.
Maybe something like "accept-sole-completion"
would be a good name for your option? (Emacs
no longer respects RMS's convention of `-flag'
for Boolean-valued vars).
2. Drop "-dwim-" from the name of your option.
That adds nothing but noise. Meaningless, if
not misleading.
And does this really have anything to do with
_displaying matches_? IIUC, it doesn't.
So far, the names proposed don't seem to
convey what (I think) this option does.
prev parent reply other threads:[~2022-02-13 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 2:47 bug#53935: 27.2; [PATCH] ecomplete.el: Auto-select when there is only a single option Phil Sainty
2022-02-11 6:30 ` Lars Ingebrigtsen
2022-02-11 8:28 ` Phil Sainty
2022-02-11 10:24 ` Phil Sainty
2022-09-08 12:53 ` Lars Ingebrigtsen
2022-02-12 6:49 ` Lars Ingebrigtsen
2022-02-12 10:27 ` Phil Sainty
2022-02-13 8:14 ` Lars Ingebrigtsen
2022-02-13 17:24 ` Drew Adams [this message]
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=SJ0PR10MB5488EEA4FE13CA08C64F5550F3329@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=53935@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=psainty@orcon.net.nz \
/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).