From: carlmarcos--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "56171@debbugs.gnu.org" <56171@debbugs.gnu.org>
Subject: bug#56171: Request for marking DEF entry when using completing-read
Date: Thu, 23 Jun 2022 21:25:42 +0200 (CEST) [thread overview]
Message-ID: <N5H0k6e--3-2@tutanota.com> (raw)
In-Reply-To: <SJ0PR10MB5488BA2D3EB29EFAF31EFC2FF3B59@SJ0PR10MB5488.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Jun 23, 2022, 19:17 by drew.adams@oracle.com:
>> It would be valuable to mark the default entry
>> when users scroll through the options defined
>> for `completing-read` whenever a DEF is supplied.
>>
>
> I'm not sure what you mean.
>
> Is this about highlighting in `*Completions*' a
> completion that's the DEF?
>
Suppose one moves through the collection. There is no way
that identifies the entry as being a designated DEF.
> Is it about selecting (as the active region) the
> DEF value when you insert it with `M-n'?
>
I think M-n ensured you are refering to DEF.
> Something else?
>
> And is the request to be able do whatever-it-is
> _optionally_ or always?
>
Optionally is ok, but do not know the technical details. I do not think
doing it always would be a bad thing.
[-- Attachment #2: Type: text/html, Size: 1733 bytes --]
next prev parent reply other threads:[~2022-06-23 19:25 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 [this message]
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
[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=N5H0k6e--3-2@tutanota.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56171@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=drew.adams@oracle.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).