From: Howard Melman <hmelman@gmail.com>
To: 13333@debbugs.gnu.org
Subject: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Thu, 05 May 2022 12:45:02 -0400 [thread overview]
Message-ID: <ly35hond2p.fsf@new-host-4.home> (raw)
In-Reply-To: <A64605487866469D901A64F9ACD0287D@us.oracle.com>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Gregory Heytings <gregory@heytings.org> writes:
>
>> I remember when I learned the concept of "future history" and its key
>> binding, it was a "wow!" effect. Because of that it's possibly the
>> only key binding I immediately remembered and never forgot. But
>> perhaps that's just me.
>
> I think the conclusion here is that there's no great enthusiasm for
> changing the terminology here (and we've been using the term "future
> history" slightly more actively in the last year), so I'm closing this
> bug report.
I think the emacs manual could be improved here.
"future history" should be in the index (currently only
"future history for file names" is) pointing to the
Minibuffer History node where it is defined.
Also perhaps "minibuffer suggestions", "minibuffer input
suggestions" or some equivalents could be indexed to point
to the same place to aid in people learning about this still
little-known "wow!" feature.
--
Howard
next prev parent reply other threads:[~2022-05-05 16:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 4:11 bug#13333: 24.3.50; (emacs) `Minibuffer History' Drew Adams
2013-01-02 4:15 ` Drew Adams
2013-01-03 0:17 ` Juri Linkov
2013-01-03 0:38 ` Drew Adams
2021-08-23 14:41 ` Lars Ingebrigtsen
2021-08-23 15:33 ` bug#13333: [External] : " Drew Adams
2021-08-25 8:59 ` Gregory Heytings
2021-08-25 11:05 ` Lars Ingebrigtsen
2021-08-25 12:25 ` Gregory Heytings
2022-05-05 12:16 ` Lars Ingebrigtsen
2022-05-05 16:45 ` Howard Melman [this message]
2022-05-06 10:21 ` Lars Ingebrigtsen
2022-05-06 13:40 ` Howard Melman
2022-05-06 13:57 ` Eli Zaretskii
2022-05-06 14:54 ` Howard Melman
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=ly35hond2p.fsf@new-host-4.home \
--to=hmelman@gmail.com \
--cc=13333@debbugs.gnu.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).