unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Barry Fishman <barry@ecubist.org>, emacs-devel@gnu.org
Subject: RE: "whether the global keymap C-x 4 will be replaced by a command,"
Date: Sun, 19 Jul 2020 17:45:04 +0000 (UTC)	[thread overview]
Message-ID: <cb1e2dca-20da-4e6d-a748-ffc75d9eed72@default> (raw)
In-Reply-To: <7n5zajfpdl.fsf@ecube.ecubist.org>

> > `C-h r C-h' already lists all of the `C-x 4' keys
> > and their commands.  And choosing any of those
> > then shows you its complete help.
> 
> If you mean "C-x 4 C-h", yes 

Yep.  Finger-flunked; sorry.

> but, "C-h k C-x 4" is left waiting for further input
> and "C-h k C-x 4 C-h" just says there is no binding for it.

> There is no universal way to get further information at that point.

I guess the info you want at that point is the
info you'd get from `C-x 4 C-h'.  Is that right?

> If "C-h k" had a solution it would apply uniformly and not require mucking
> about which changing any (other) key bindings.

OK.

> Should there be a general rule than any partial key sequence have "C-h"
> show the possible options?

Maybe.

Have you really found this to be a problem?

I haven't.  But I know that some users don't
know about using `C-h' after a prefix key.

And I do get your point, about not wanting to
abandon `C-h k C-x 4' and use `C-x 4 C-h' at
that point.  That doesn't bother me, but OK.

> And if so wouldn't it be more straight
> forward to not have to manually define for each possible key sequence,
> but still have any exi[s]ting such binding still work?

Definitely.  But only if implementing that
doesn't remove/break something else (unlike
what's being proposed in this thread).

No one has to explicitly define a binding for
`C-h' after a prefix key, for example.  (And
as you point out, there is in fact _no_ such
key binding.)  Yes, the same should apply for
what you suggest.

But I don't think the overall discussion is
really about `C-h k' and its getting to the
help for a prefix key (e.g. help like what
`C-h 4 C-h' shows).

But if it were, then my reply would be (besides
perhaps doing something such as you suggest -
which AFAIK doesn't require changes such as
those proposed), to instead provide something
like the help that key completion (library
Key See or Icicles) or `which-key' provides.

https://www.emacswiki.org/emacs/KeySee

https://www.emacswiki.org/emacs/Icicles

https://github.com/justbur/emacs-which-key

Those all, like an appended `C-h', let you see
the keys that complete a prefix key, as well
as their commands.  And unlike `C-h', they
don't interrupt use of the prefix key.

(In addition, Icicles lets you get the full
doc string for any such completing key.)




      reply	other threads:[~2020-07-19 17:45 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
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 [this message]

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=cb1e2dca-20da-4e6d-a748-ffc75d9eed72@default \
    --to=drew.adams@oracle.com \
    --cc=barry@ecubist.org \
    --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).