From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: RE: Describing local-map/keymap in overlays/text properties
Date: Sat, 6 Jul 2013 13:18:23 -0700 (PDT) [thread overview]
Message-ID: <20f7f954-3d6d-496a-b346-4a4c13e36775@default> (raw)
In-Reply-To: <87y59jzp8l.fsf@building.gnus.org>
> >> Is there a different command to see text property key bindings?
> >
> > C-u C-x =
>
> That's kinda obscure. Anybody mind if I alter `C-h m' and `C-h b'
> to display text prop keymaps (first)?
Yes, I mind. (But please submit an enhancement request via
`report-emacs-bug', if you like.)
`C-h m' is already very long, even for a short major-mode doc string.
This does not belong there at all, IMO.
`C-h b' is another story, but it refers to the current context (e.g.
buffer) generally, not only to a specific position.
(I assume you are speaking generally, and not just about the doc
for some particular mode.)
Better than messing with `C-h m' or `C-h b' might be to provide a
new command that lists only the text-property bindings at point.
(But that could also be said for other parts of the `C-u C-x =' output:
it is a mix of different kinds of info. One could imagine several
separate commands for the different kinds of info.)
My general reaction to your proposal is YAGNI. `C-u C-x =' is fine.
prev parent reply other threads:[~2013-07-06 20:18 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
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 [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=20f7f954-3d6d-496a-b346-4a4c13e36775@default \
--to=drew.adams@oracle.com \
--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).