unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: RE: Describing local-map/keymap in overlays/text properties
Date: Sat, 6 Jul 2013 13:18:53 -0700 (PDT)	[thread overview]
Message-ID: <430694bb-b123-40cc-bbd9-34a8f8761438@default> (raw)
In-Reply-To: <87mwpzveef.fsf@building.gnus.org>

> > 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?
> 
> If you're pushing `C-h b', you want to know what commands are available
> for you.  That's the point of the command.  The commands that are
> available in the local text properties are the ones that matter to you
> most, because you moved the cursor there.

No, that's one use case of `C-h b', and yes, it ignores text-property
bindings.

If you make `C-h b' take into account `point' then it no longer shows
you binding information about the current context (buffer) in general.

If `a' is bound in the current buffer/mode to `self-insert-command',
but there is a text-property binding of `a' to `ignore', then `C-h b'
output will show only the latter.  You lose the general info.

Or if you choose to show both, and the fact that the text-property
bindings shadow other bindings, then why privilege text-property
bindings this way?  We don't do that in `C-h b' for other bindings
that override bindings.

`C-h b' does not currently tell you, for example, that `a' is bound
in the `global-map' to `self-insert-command' AND that it is bound in
the current local keymap to `foobar' AND that it is bound in the
currently active minor mode `toto' to `toto-go-fish'... AND give you
information about the various binding shadowings.  It simply gives
you the current effective binding of `a'.



  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 [this message]
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=430694bb-b123-40cc-bbd9-34a8f8761438@default \
    --to=drew.adams@oracle.com \
    --cc=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).