unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: 48134@debbugs.gnu.org
Subject: bug#48134: When sitting on top of a M-x item in the manual
Date: Sun, 02 May 2021 10:09:12 -0400	[thread overview]
Message-ID: <lyfsz59qif.fsf@Lumet2.home> (raw)
In-Reply-To: <87fsz73t9z.8.fsf@jidanni.org>


Lars Ingebrigtsen <larsi@gnus.org> writes:

> This is how Emacs works all over the place -- `M-n' should get you the
> suggestion.  Making all prompts tell you about this standard feature
> would be less than optimal, so I don't think there's anything to fix
> here, and I'm closing this bug report.

I suggest making this standard feature a little more
explicit in the emacs manual.  I think it's only mentioned
in the Minibuffer History node (in Emacs 27) which is fine,
but the only index entry for this is "future history for
file names".  I think it would be better to also (or just)
index "future history" in the previous paragraph.

Also a sentence explaining how this standard feature
commonly behaves would help.  Something like:

This is often a value at point relevant to the command such
as a symbol, word, file name or color.

(with perhaps a mention of thing-at-point)

-- 

Howard






  reply	other threads:[~2021-05-02 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  5:41 bug#48134: When sitting on top of a M-x item in the manual 積丹尼 Dan Jacobson
2021-05-01  8:59 ` Kévin Le Gouguec
2021-05-01 12:15   ` 積丹尼 Dan Jacobson
2021-05-02  7:14     ` Lars Ingebrigtsen
2021-05-02 14:09       ` Howard Melman [this message]
2021-05-02 16:09       ` Kévin Le Gouguec
2021-05-03  9:00         ` Lars Ingebrigtsen
2021-05-01 14:01 ` bug#48134: [External] : " Drew Adams
2021-05-01 14:35   ` Eli Zaretskii
2021-05-01 16:28     ` Drew Adams
2021-05-01 20:09   ` Juri Linkov
2021-05-01 23:23     ` Drew Adams
2021-05-02 20:52       ` Juri Linkov
2021-05-03  0:35         ` Drew Adams

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=lyfsz59qif.fsf@Lumet2.home \
    --to=hmelman@gmail.com \
    --cc=48134@debbugs.gnu.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).