all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: Juri Linkov <juri@jurta.org>, 13333@debbugs.gnu.org
Subject: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Thu, 05 May 2022 14:16:39 +0200	[thread overview]
Message-ID: <874k24rx7c.fsf@gnus.org> (raw)
In-Reply-To: <ba9bdda48f092779dbd5@heytings.org> (Gregory Heytings's message of "Wed, 25 Aug 2021 12:25:08 +0000")

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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-05 12:16 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 [this message]
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=874k24rx7c.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=13333@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=juri@jurta.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.