From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>, 48134@debbugs.gnu.org
Subject: bug#48134: When sitting on top of a M-x item in the manual
Date: Mon, 03 May 2021 11:00:44 +0200 [thread overview]
Message-ID: <87zgxcchtv.fsf@gnus.org> (raw)
In-Reply-To: <875z01jewz.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sun, 02 May 2021 18:09:32 +0200")
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> I see that (info "(emacs) Minibuffer History") mentions its DWIM
> behaviour and gives examples for filename prompts, but given how
> ubiquitous and useful M-n is, I wonder if we couldn't do more to
> advertise it.
Yeah, it is perhaps a too-hidden feature.
> I realize that this would probably not be trivial to implement though.
> Looking up "future history in minibuffer input" in the Elisp manual
> brought me to (info "(elisp) Text from Minibuffer"), which lured me into
> thinking that this hypothetical hint could simply be added in
> read-from-minibuffer, by looking at the DEFAULT argument; a stroll
> through read-extended-command taught me that some functions compute
> their "future history" dynamically with minibuffer-default-add-function,
> which I guess complicates things a bit?
Yes, in general we don't really know whether we have anything in the
future history until the user hits `M-n', I think? We could say
something in the instances where we do know in advance, but users might
infer from that that there's nothing in `M-n' if the message doesn't
appear. And saying "M-n might reveal something" isn't very helpful
either.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-03 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 5:41 bug#48134: When sitting on top of a M-x item in the manual 積丹尼 Dan Jacobson
2021-05-01 8:59 ` Kévin Le Gouguec
2021-05-01 12:15 ` 積丹尼 Dan Jacobson
2021-05-02 7:14 ` Lars Ingebrigtsen
2021-05-02 14:09 ` Howard Melman
2021-05-02 16:09 ` Kévin Le Gouguec
2021-05-03 9:00 ` Lars Ingebrigtsen [this message]
2021-05-01 14:01 ` bug#48134: [External] : " Drew Adams
2021-05-01 14:35 ` Eli Zaretskii
2021-05-01 16:28 ` Drew Adams
2021-05-01 20:09 ` Juri Linkov
2021-05-01 23:23 ` Drew Adams
2021-05-02 20:52 ` Juri Linkov
2021-05-03 0:35 ` Drew Adams
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=87zgxcchtv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48134@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=kevin.legouguec@gmail.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).