From: Howard Melman <hmelman@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13333@debbugs.gnu.org
Subject: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Fri, 6 May 2022 09:40:59 -0400 [thread overview]
Message-ID: <C85426FF-0D9E-43FF-88F6-BEC6AE2F88AC@gmail.com> (raw)
In-Reply-To: <87h763neqr.fsf@gnus.org>
On May 6, 2022, at 6:21 AM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Howard Melman <hmelman@gmail.com> writes:
>
>> 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.
>
> Sure, makes sense. Could you come up with a patch for this?
I'm sorry no, I don't build my own emacs, don't have the source,
and haven't signed copyright over. It should just be a couple
of @cindex calls in mini.texi
@cindex future history
@cindex minibuffer suggestions
Howard
next prev parent reply other threads:[~2022-05-06 13:40 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
2022-05-06 10:21 ` Lars Ingebrigtsen
2022-05-06 13:40 ` Howard Melman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C85426FF-0D9E-43FF-88F6-BEC6AE2F88AC@gmail.com \
--to=hmelman@gmail.com \
--cc=13333@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.