From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master f0cd91067d: Improve `C-h b' output for remapped commands.
Date: Sat, 11 Jun 2022 12:36:48 +0200 [thread overview]
Message-ID: <877d5ntrjz.fsf@gnus.org> (raw)
In-Reply-To: <87czfgmzk0.fsf@web.de> (Michael Heerdegen's message of "Fri, 10 Jun 2022 15:13:35 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I'm also ok with Lars' version - would remove the the final dot though,
> like
>
> C-x 4 C-o ido-display-buffer
> (Remapped via <remap> <display-buffer>)
> C-x 5 C-o ido-display-buffer-other-frame
> (Remapped via <remap> <display-buffer-other-frame>)
I've now gone with this. I agree with Stefan that it would be nice to
avoid the repetition of "remap", but the variants suggested all seem a
bit obscure to me -- i.e., they don't really explain what we're trying
to convey unless you already know about remapped commands, while
spelling it out in this way should give the users a hint they can look
up in the manual.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-11 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165478576035.737.9544262446139689575@vcs2.savannah.gnu.org>
[not found] ` <20220609144240.9D08DC01682@vcs2.savannah.gnu.org>
2022-06-09 16:44 ` master f0cd91067d: Improve `C-h b' output for remapped commands Stefan Monnier
2022-06-09 17:45 ` [External] : " Drew Adams
2022-06-10 9:07 ` Lars Ingebrigtsen
2022-06-10 11:23 ` Stefan Kangas
2022-06-10 12:07 ` Michael Heerdegen
2022-06-10 13:02 ` Po Lu
2022-06-10 13:13 ` Michael Heerdegen
2022-06-11 10:36 ` Lars Ingebrigtsen [this message]
2022-06-10 13:01 ` Stefan Monnier
2022-06-11 10:48 ` 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=877d5ntrjz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=michael_heerdegen@web.de \
/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.