From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Describing local-map/keymap in overlays/text properties
Date: Sat, 06 Jul 2013 19:25:40 +0300 [thread overview]
Message-ID: <838v1jy7sr.fsf@gnu.org> (raw)
In-Reply-To: <87fvvrwtsy.fsf@building.gnus.org>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
> Date: Sat, 06 Jul 2013 18:13:17 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Then how is that different from "C-u C-x ="?
>
> It's different in that people hit `C-h b' to learn what keystrokes are
> available to them. `C-u C-x =' is a relatively obscure command, and
> having to use both commands for doing something as basic as this is
> pretty nonsensical.
Pushing the normal output of "C-h b" further down the buffer doesn't
make sense, either. How about a new "C-h" command, or perhaps an
argument to "C-h b" that would trigger this new display?
next prev parent reply other threads:[~2013-07-06 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 19:04 Describing local-map/keymap in overlays/text properties Lars Magne Ingebrigtsen
2013-07-05 9:01 ` Andreas Schwab
2013-07-06 15:23 ` Lars Ingebrigtsen
2013-07-06 15:46 ` Eli Zaretskii
2013-07-06 15:56 ` Lars Ingebrigtsen
2013-07-06 16:02 ` Eli Zaretskii
2013-07-06 16:13 ` Lars Ingebrigtsen
2013-07-06 16:25 ` Eli Zaretskii [this message]
2013-07-06 16:31 ` Lars Ingebrigtsen
2013-07-06 17:42 ` Eli Zaretskii
2013-07-08 14:14 ` Lars Magne Ingebrigtsen
2013-07-08 14:40 ` Lars Magne Ingebrigtsen
2013-07-06 20:06 ` Stephen Leake
2013-07-06 20:18 ` Drew Adams
2013-07-06 19:47 ` James Cloos
2013-07-07 6:43 ` Andreas Schwab
2013-07-07 19:20 ` James Cloos
2013-07-06 20:18 ` 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=838v1jy7sr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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).