From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mime button keys not in describe-bindings
Date: Sun, 23 Feb 2003 01:47:51 +0100 [thread overview]
Message-ID: <m3isvb9614.fsf@quimbies.gnus.org> (raw)
In-Reply-To: m3znonc2v7.fsf@quimbies.gnus.org
bugs@gnus.org (Lars Magne Ingebrigtsen) writes:
> That is, if there is text under point with the `keymap' text property
> set, then these keys should also be listed by `C-h b', I think. And
> preferably first.
Never mind; this works perfectly in the current Emacs pretest.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-02-23 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873cmmcqjb.fsf@jidanni.org>
2003-02-22 23:27 ` mime button keys not in describe-bindings Lars Magne Ingebrigtsen
2003-02-23 0:47 ` Lars Magne Ingebrigtsen [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=m3isvb9614.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).