From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13333@debbugs.gnu.org
Subject: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Wed, 25 Aug 2021 12:25:08 +0000 [thread overview]
Message-ID: <ba9bdda48f092779dbd5@heytings.org> (raw)
In-Reply-To: <87r1ehlr7y.fsf@gnus.org>
>> The idea of replacing DEFAULT with (DEFAULT . SUGGESTIONS) is also not
>> really optimal IMO.
>
> I think the suggestion was replacing DEFAULTS with (DEFAULT .
> SUGGESTIONS), though...
>
Yes, sorry, that was a typo, I meant "replacing DEFAULTS with (DEFAULT .
SUGGESTIONS).
>> The problem is that DEFAULT would not only be the value that is used
>> when the user hits RET with an empty input, it is also the first value
>> inserted when hitting M-n, that is, it is also the first SUGGESTION.
>
> I guess you could look at it that way... but I'd say that the first
> `M-n' gives you the default, and then you get the suggestions.
>
Isn't the default already part of the suggestions? Unless I'm missing
something, it's a suggested default. The current distinction between
(past) "history" and "future history", where the first item of the future
history is the default, and in which you can freely navigate back and
forth with M-p and M-n is, much clearer IMO than a distinction between
three kinds of items, (past) "history", default and suggestions. In fact,
I don't understand what problem this would solve.
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.
next prev parent reply other threads:[~2021-08-25 12:25 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 [this message]
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
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=ba9bdda48f092779dbd5@heytings.org \
--to=gregory@heytings.org \
--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 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).