From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
"carlmarcos@tutanota.com" <carlmarcos@tutanota.com>
Cc: "56171@debbugs.gnu.org" <56171@debbugs.gnu.org>
Subject: bug#56171: Request for marking DEF entry when using completing-read
Date: Fri, 24 Jun 2022 16:14:49 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488041684050A2C5A39C0BAF3B49@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a6a2nkwh.fsf@gnus.org>
> > It is a different thing than that. I customarily using the `up' and
> > `down' key to move through the collection of entries. Could there be
> > some form of indicator (e.g. highlight, underline, some other means)
> > that will tell me that is was selected as the default by the package
> > designer? Currently I see no distinction, with all entries in
> > collection as just an entry like any other.
>
> Again, what's the use case? Why do you want the default to be singled
> out in some way?
I'm curious too. I don't say it couldn't be useful,
but I wonder what the aim is.
___
BTW, note that the default value (or even any of a
list of default values) provided need not be among
the candidates for completion, if completion is lax
(REQUIRE-MATCH = nil). E.g.:
(completing-read "q: " '("a" "b" "c" "d")
nil nil nil nil "e")
next prev parent reply other threads:[~2022-06-24 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 19:03 bug#56171: Request for marking DEF entry when using completing-read carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23 19:17 ` Drew Adams
2022-06-23 19:25 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23 22:08 ` Drew Adams
2022-06-24 9:40 ` Lars Ingebrigtsen
[not found] ` <87v8sqqu0y.fsf@gnus.org-N5K4ctK----2>
2022-06-24 15:11 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 15:25 ` Lars Ingebrigtsen
2022-06-24 16:14 ` Drew Adams [this message]
[not found] ` <SJ0PR10MB5488041684050A2C5A39C0BAF3B49@SJ0PR10MB5488.namprd10.prod.outlook.com-N5LUrHl----2>
2022-06-24 16:49 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 17:28 ` Drew Adams
2022-06-25 7:21 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 8:37 ` Lars Ingebrigtsen
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=SJ0PR10MB5488041684050A2C5A39C0BAF3B49@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=56171@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=larsi@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.
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).