unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 08:59:39 +0000	[thread overview]
Message-ID: <ba9bdda48f2339a63f78@heytings.org> (raw)
In-Reply-To: <871r6krzot.fsf@gnus.org>


>>> You can think of this as moving through the "future history" list.
>>
>> "future history" is a misnomer.
>>
>>> There is no logical connection between the set of default values
>>
>> "default values" is a misnomer.
>>
>> There can be only one default value that it used when the user enters 
>> empty input in the minibuffer.  Other values are not "defaults".
>>
>> In most applications similar functionality is called "suggestions" 
>> where a drop-down list of suggestions is displayed while the user types 
>> a query into a text box.  This feature is documented at 
>> http://en.wikipedia.org/wiki/Search_suggest_drop-down_list
>>
>> Thus I propose to enhance the documentation by replacing the term 
>> DEFAULTS with (DEFAULT . SUGGESTIONS) where DEFAULT will retain its 
>> original meaning of the value returned for empty input and SUGGESTIONS 
>> is a list of suggestions available via `M-n'.
>
> 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?
>

FWIW, I do not think this is a good idea.

Emacs is the only application I know which has a unified way to interact 
with history of past actions and suggestions for future actions.  The name 
"future history" is not only cute, it is also an excellent one, from a 
mnemonical viewpoint, to remember that the M-n is the key binding that 
should be used to access those suggestions.  What I would suggest instead 
is to add an explanation between parentheses that "future history" is what 
is called in some other applications "suggestions" (and possibly update 
the glossary accordingly).

The idea of replacing DEFAULT with (DEFAULT . SUGGESTIONS) is also not 
really optimal IMO.  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.  What I would suggest instead is to replace DEFAULTS with 
FUTURE-HISTORY, with an explanation that the first element of 
FUTURE-HISTORY is used when the user hist RET with an empty input.





  parent reply	other threads:[~2021-08-25  8:59 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 [this message]
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

  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=ba9bdda48f2339a63f78@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).