unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 13333@debbugs.gnu.org
Subject: bug#13333: 24.3.50; (emacs) `Minibuffer History'
Date: Fri, 6 May 2022 10:54:14 -0400	[thread overview]
Message-ID: <691C85CB-C07B-4C06-9704-BB6A79606D1E@gmail.com> (raw)
In-Reply-To: <831qx6227e.fsf@gnu.org>



> On May 6, 2022, at 9:57 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> Cc: 13333@debbugs.gnu.org
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Fri, 6 May 2022 09:40:59 -0400
>> 
>>> 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
> 
> That's not how good index entries are (or should be) added.  One needs
> to think of subjects potential readers will have in mind when they are
> looking for the indexed text.  With this in mind, I wonder who would
> think about "minibuffer suggestions" in conjunction with this
> material?  I wouldn't, because "minibuffer suggestions" tells nothing
> to me about what it alludes to.  "Suggestions" is not a good word to
> describe this feature.
> 
> As for "future history", if we want it, it should _replace_ the
> existing index entry, because they both lead to almost the same text,
> and it is not useful to have several index entries that begin with the
> same text and lead to the same page of the manual.

I disagree. I was responding to the previous comments in this bug
that:

> In most applications similar functionality is called "suggestions"


> "Future history" is cute and all, but it's not really helpful as a term -- 

> especially when "suggestions" is as clear as it is.


The original bug offered: "default input", "default input value" "default
minibuffer input" which I think are also good.

So while you might not think of "minibuffer suggestions" it seems others
would.  I would.

I'd mostly be fine with having these replace the existing index entries for:

@cindex future history for file names
@cindex minibuffer defaults for file names

but I would prefer they didn't.  Just because  they "begin with the same
text" doesn't mean they're useless.  They end with different text and when
one searches for "file name" in the index getting directed to either of 
these is quite useful.

TBH I think the text itself could be expanded a bit.  I'd like to see:

"Emacs tries fetching from a list of default arguments: values that you are 
likely to enter, typically text found near point."

Howard





      reply	other threads:[~2022-05-06 14:54 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
2022-05-06 13:57                   ` Eli Zaretskii
2022-05-06 14:54                     ` Howard Melman [this message]

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=691C85CB-C07B-4C06-9704-BB6A79606D1E@gmail.com \
    --to=hmelman@gmail.com \
    --cc=13333@debbugs.gnu.org \
    --cc=eliz@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).