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: Lars Ingebrigtsen <larsi@gnus.org>,
"56171@debbugs.gnu.org" <56171@debbugs.gnu.org>
Subject: bug#56171: Request for marking DEF entry when using completing-read
Date: Sat, 25 Jun 2022 09:21:58 +0200 (CEST) [thread overview]
Message-ID: <N5M2S_L----2@tutanota.com> (raw)
In-Reply-To: <SJ0PR10MB54884191061EAF2682A605AAF3B49@SJ0PR10MB5488.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Jun 24, 2022, 17:28 by drew.adams@oracle.com:
>> Wouldn't one normally associate a default with
>> some sensible setting worth looking into most times?
>> Perhaps this could be a user setting.
>>
>
> I see. So the use case is to be able to check what
> the default value is, so you can try to understand
> why it's considered particularly useful.
>
Correct
> For that, I'd think that `M-n' suffices, to see
> what the default value is (the first default value,
> if there are several).
>
> Again, the default value need not even be one of
> the choices (completion candidates), in the case of
> lax completion (e.g. `C-x b'). I'd think that the
> best way to find out what the default is would be
> `M-n'.
>
If not one of the choices, then there will be no indicator on any
entry in the collection.
I think it usually takes some time to discover the `M-n' way.
> (Just one opinion, and I may still be missing something.)
>
It is just an observation. Another way is to depend on the designer
describing typical use if attentive enough to include that information.
I think that the suggestion could make one's acquaintance with the package
speedier if there are suggestions on well designed settings.
[-- Attachment #2: Type: text/html, Size: 2302 bytes --]
next prev parent reply other threads:[~2022-06-25 7:21 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
[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 [this message]
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=N5M2S_L----2@tutanota.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56171@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=drew.adams@oracle.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).