From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 14248@debbugs.gnu.org
Subject: bug#14248: 24.3.50; crappy error: "Wow, indirect keymap entry!!"
Date: Mon, 10 Feb 2014 11:43:10 -0800 (PST) [thread overview]
Message-ID: <e6e528b8-391a-48da-a3d0-3414873cdd0c@default> (raw)
In-Reply-To: <jwv8uti3iag.fsf-monnier+emacsbugs@gnu.org>
> Maintainers also deserve better. E.g. they deserve to know what you
> did to trigger that error.
I'm sorry, but I don't recall from a year ago. And it's possible
that I was not aware at the time just what triggered the error.
As you know, when I can provide a how-it-happened I typically do.
But perhaps the code can tell you how this error is triggered?
And regardless of how the error was raised, why such a message?
next prev parent reply other threads:[~2014-02-10 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 16:25 bug#14248: 24.3.50; crappy error: "Wow, indirect keymap entry!!" Drew Adams
2014-02-10 6:46 ` Lars Ingebrigtsen
2014-02-10 16:44 ` Stefan Monnier
2014-02-10 17:06 ` Drew Adams
2014-02-10 19:00 ` Stefan Monnier
2014-02-10 19:43 ` Drew Adams [this message]
2014-02-11 3:48 ` Stefan Monnier
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=e6e528b8-391a-48da-a3d0-3414873cdd0c@default \
--to=drew.adams@oracle.com \
--cc=14248@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).