unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: master f0cd91067d: Improve `C-h b' output for remapped commands.
Date: Fri, 10 Jun 2022 14:07:24 +0200	[thread overview]
Message-ID: <87ilp8n2mb.fsf@web.de> (raw)
In-Reply-To: CADwFkmmQMn+PUuDbhuzBSq8Hrpzzd+bGQuNq_PYgLysieXXhMw@mail.gmail.com

Stefan Kangas <stefan@marxist.se> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Hm...  What about just flipping things around and using our words?  That
> > would also make the lines shorter.  I.e.,
> >
> >      C-x 4 C-o     ido-display-buffer
> >        (Remapped via <remap> <display-buffer>.)
>
> To avoid saying "remap" twice, how about:
>
>        (Remapped from display-buffer.)

I would prefer

  (via <remap> <display-buffer>)

instead if we want to get rid of the doubled word "remap".  For some
reason I find your version harder to understand.

Maybe because there are a lot of components involved: the explained key
binding, the remapping key binding, the command remapped, and the
"target" command - and it's not trivial to get them into the right order
in my head to understand what is going on.

Michael.




  reply	other threads:[~2022-06-10 12:07 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 [this message]
2022-06-10 13:02           ` Po Lu
2022-06-10 13:13             ` Michael Heerdegen
2022-06-11 10:36               ` Lars Ingebrigtsen
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

  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=87ilp8n2mb.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@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).