From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Juri Linkov <juri@jurta.org>
Cc: "13333@debbugs.gnu.org" <13333@debbugs.gnu.org>
Subject: bug#13333: [External] : Re: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Mon, 23 Aug 2021 15:33:24 +0000 [thread overview]
Message-ID: <SJ0PR10MB548885397D654253132D0A9AF3C49@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <871r6krzot.fsf@gnus.org>
> I think this sounds like a good idea. "Future history" is cute and all,
> but it's not really helpful as a term -- especially when "suggestions"
> is as clear as it is.
>
> Anybody with any comments here?
You're asking for "more info" now?
I already commented on that suggestion, eight years
ago. Does that count?
I agree with your suggestion. But please propose
it to everyone at emacs-devel.
And please leave this bug open, unless you also
correct the problems it addresses.
(Yes, if your suggestion is implemented that will
change some of the text of this node. But let's
please get all of the problems mentioned taken
care of, whether or not the suggestion gets done.)
And the bug report itself (from me), does that count?
It details "multiple problems with this node."
next prev parent reply other threads:[~2021-08-23 15:33 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 ` Drew Adams [this message]
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
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=SJ0PR10MB548885397D654253132D0A9AF3C49@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=13333@debbugs.gnu.org \
--cc=juri@jurta.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.