From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Define-keys overriden
Date: Thu, 21 Jul 2011 02:20:38 +0200 [thread overview]
Message-ID: <87hb6gbi21.fsf@gmail.com> (raw)
First, I apologize in advance for the poor quality of this report, I
can't seem to reproduce this bug reliably.
Sometimes (sorry I can't be more precise, I can't find a pattern), when
I M-x gnus again (ie there was a previous instance that was killed off),
the define-keys I have in my .gnus are ignored. I'm talking about stuff
like
(define-key gnus-group-mode-map (kbd "j") 'gnus-group-toggle-unsubscribed)
(where gnus-group-toggle-unsubscribed is some function of mine). In this
example, "j" gets bound to the default binding for "j" (jump to group)
instead of gnus-group-toggle-unsubscribed. It just happened to me, so I
tried bisecting my .gnus, ie killing gnus, moving the (define-key)
around in the config file, and M-x gnus again. I traced the bug back to
an advice I have to prevent gnus from inflooping
(defadvice gnus-group-get-new-news (around gnus-demon-timeout activate)
"Timeout for Gnus."
(with-timeout
(5 (message "Gnus timed out."))
ad-do-it))
which I got off somewhere in emacswiki, I believe. Placing the
define-key after the defadvice resulted in "j" being defined as
gnus-group-toggle-unsubscribed, placing it before resulted in the
default value (jump to group) being assigned. Then, as fun bugs often
do, it disappeared, preventing me from debugging further.
Any pointers as to why this can happen, or suggestions of things to look
for next time it happens?
next reply other threads:[~2011-07-21 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 0:20 Antoine Levitt [this message]
2011-08-21 3:46 ` Lars Magne Ingebrigtsen
2011-08-21 9:45 ` Antoine Levitt
2011-09-10 22:53 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hb6gbi21.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=ding@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.
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 NNTP newsgroup(s).