From: Sebastian Urban <mrsebastianurban@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
"積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: Stefan Kangas <stefan@marxist.se>, 36525@debbugs.gnu.org
Subject: bug#36525: M-x default when cursor on top of a M-x command in INFO
Date: Mon, 15 Jul 2019 10:43:09 +0200 [thread overview]
Message-ID: <1d81428d-9f03-8b87-110a-2f97a1b9d05b@gmail.com> (raw)
In-Reply-To: <87y317mm4n.fsf@tcd.ie>
> Yes, and I don't think it is warranted, so I think this report
> should be closed as notabug/wontfix.
I'm a bit late to the party, but... perhaps doing it how "describe"
commands do it would be better, i.e. in minibuffer:
M-x (default list-coding-systems) |
where '|' is cursor position. No evasive manoeuvres to avoid
automatic inserting, no deleting if we want to run different command,
no additional key (like 'M-n') - just RET if you agree, or write
different command. But I must say that it looks a bit stranger than
in case of "describe" commands. Maybe just make it optional
behaviour, controlled by variable (nil/t). Of course, in this case,
'M-n' should avoid first value, because it'll be inside parentheses,
and skip to the next one.
next prev parent reply other threads:[~2019-07-15 8:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 11:17 bug#36525: M-x default when cursor on top of a M-x command in INFO 積丹尼 Dan Jacobson
2019-07-06 15:55 ` Drew Adams
2019-07-07 0:25 ` 積丹尼 Dan Jacobson
2019-07-07 22:43 ` Juri Linkov
2019-07-08 0:27 ` Drew Adams
2019-07-08 20:58 ` Juri Linkov
2019-07-08 21:37 ` Drew Adams
2019-07-09 20:09 ` Juri Linkov
2019-07-09 21:07 ` Drew Adams
2019-07-07 13:55 ` Basil L. Contovounesios
2019-07-09 8:52 ` 積丹尼 Dan Jacobson
2019-07-09 10:55 ` Stefan Kangas
2019-07-09 11:10 ` 積丹尼 Dan Jacobson
2019-07-09 12:24 ` Stefan Kangas
2019-07-09 12:24 ` Basil L. Contovounesios
2019-07-15 8:43 ` Sebastian Urban [this message]
2019-07-09 12:24 ` Basil L. Contovounesios
2019-10-14 20:53 ` Lars Ingebrigtsen
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=1d81428d-9f03-8b87-110a-2f97a1b9d05b@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=36525@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.org \
--cc=stefan@marxist.se \
/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.