From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: RE: "whether the global keymap C-x 4 will be replaced by a command,"
Date: Tue, 14 Jul 2020 15:55:29 -0700 (PDT) [thread overview]
Message-ID: <fe5b882d-aae6-46b6-8648-9ebb0352f2eb@default> (raw)
In-Reply-To: <87wo353f77.fsf@mail.linkov.net>
> >> This means that after binding the current ctl-x-4-map in Emacs core
> >> to the other-window command, 'C-h k C-x 4' will display the help for
> >> that command, not for the whole sequence 'C-h k C-x 4 C-f'.
> >
> > I don't think we can/should make `C-h k` read all of `C-x 4 C-f`,
> indeed.
> > But maybe we could make the following work: `C-x 4 C-h k C-f`.
>
> Would it be more expected for `C-x 4 C-h k C-f` to show the help buffer
> about `C-f` (forward-char) in another window?
>
> The prefix `C-x 4` says "show the output of the next command in
> another window" where the next command is `C-h k C-f`.
Par exemple. Good point.
Scratch a bit more, and I won't be surprised if we
stumble on other such dilemmas/surprises.
next prev parent reply other threads:[~2020-07-14 22:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1juSI3-0005ai-6j@fencepost.gnu.org>
[not found] ` <83ft9woo68.fsf@gnu.org>
2020-07-13 2:52 ` "whether the global keymap ‘C-x 4’ will be replaced by a command," Richard Stallman
2020-07-13 23:58 ` "whether the global keymap C-x 4 " Juri Linkov
2020-07-14 4:19 ` Drew Adams
2020-07-14 5:55 ` Stefan Monnier
2020-07-14 14:41 ` Drew Adams
2020-07-14 14:48 ` Stefan Monnier
2020-07-14 15:28 ` Drew Adams
2020-07-14 15:35 ` John Yates
2020-07-14 14:51 ` Eli Zaretskii
2020-07-14 15:15 ` Stefan Monnier
2020-07-14 16:29 ` Eli Zaretskii
2020-07-15 4:06 ` Stefan Monnier
2020-07-15 14:16 ` Eli Zaretskii
2020-07-15 23:54 ` Juri Linkov
2020-07-16 4:07 ` Stefan Monnier
2020-07-16 22:57 ` Juri Linkov
2020-07-17 2:56 ` Stefan Monnier
2020-07-17 0:56 ` Richard Stallman
2020-07-14 22:27 ` Juri Linkov
2020-07-14 22:55 ` Drew Adams [this message]
2020-07-15 4:06 ` Stefan Monnier
2020-07-16 3:21 ` Richard Stallman
2020-07-16 15:05 ` Eli Zaretskii
2020-07-16 23:05 ` Juri Linkov
2020-07-17 2:10 ` Drew Adams
2020-07-18 1:57 ` Richard Stallman
2020-07-18 16:23 ` Sean Whitton
2020-07-18 17:00 ` Drew Adams
2020-07-19 2:28 ` Richard Stallman
2020-07-19 15:28 ` Drew Adams
2020-07-21 0:22 ` Sean Whitton
2020-07-18 1:54 ` Richard Stallman
2020-07-18 23:21 ` Juri Linkov
2020-07-19 0:11 ` Drew Adams
2020-07-19 3:38 ` Stefan Monnier
2020-07-19 22:07 ` Juri Linkov
2020-07-20 3:09 ` Stefan Monnier
2020-07-20 20:50 ` Juri Linkov
2020-07-20 2:39 ` Richard Stallman
2020-07-20 3:13 ` Stefan Monnier
2020-07-15 3:32 ` Richard Stallman
2020-07-19 13:00 ` Barry Fishman
2020-07-19 15:38 ` Drew Adams
2020-07-19 16:20 ` Barry Fishman
2020-07-19 17:45 ` 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=fe5b882d-aae6-46b6-8648-9ebb0352f2eb@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).