From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Florian Beck <fb@miszellen.de>, 8297@debbugs.gnu.org
Subject: bug#8297: Request: Better Emacs self-documentation for customization
Date: Tue, 22 Mar 2011 07:59:10 +0100 [thread overview]
Message-ID: <AANLkTin9e9wuPD81+x_A7wjy6oenjMBx6WCjoeHM4VLT@mail.gmail.com> (raw)
In-Reply-To: <jwvtyewgn3a.fsf-monnier+emacs@gnu.org>
On Mon, Mar 21, 2011 at 11:00 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>
>> - `describe-key' only provides a link to the function, not to the place the
>> key was defined.
>
> That's also more difficult because OT1H `define-key' does not get much
> information (it can check load-file-name, but it doesn't know the line
> number, nor the name of the map it receives and neither does it know
> reliably what the key description looks like in the source file, so it's
> hard to do a regexp-search), and OTOH there's no place currently to
> store that information, tho I guess we could keep it in some side
> hash-table.
That would be good.
I have a hack that at least try to guess the map where a key is
defined. This is the function `describe-key-and-map-briefly' in
ourcomments-util.el in nXhtml. (It is a replacement for
`describe-key-briefly'.)
next prev parent reply other threads:[~2011-03-22 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 0:07 bug#8297: Request: Better Emacs self-documentation for customization Florian Beck
2011-03-21 22:00 ` Stefan Monnier
2011-03-22 6:59 ` Lennart Borgman [this message]
2011-03-23 8:59 ` Florian Beck
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=AANLkTin9e9wuPD81+x_A7wjy6oenjMBx6WCjoeHM4VLT@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=8297@debbugs.gnu.org \
--cc=fb@miszellen.de \
--cc=monnier@iro.umontreal.ca \
/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).