From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: How to get this debugged (pressing g fails)
Date: Fri, 27 Sep 2013 07:50:10 +0900 [thread overview]
Message-ID: <b4mtxh7p599.fsf@jpl.org> (raw)
In-Reply-To: <87ioxngx9b.fsf@newsguy.com>
Harry Putnam wrote:
> After loading gnus-group.el and pressing 'g' I just get
> the same exact debugger output:
> Debugger entered: nil
> gnus-group-get-new-news(nil)
> call-interactively(gnus-group-get-new-news nil nil)
Uhm, I have no idea of how such an taciturn message is made.
> Maybe the bit from Messages buffer will help... Going to debugger
> always happens after scanning nndraft active file.
> from Messages buffer
,----
| Checking new news...
| nnimap read 2k from imap.gmail.com
| Reading active file via nnml...
| Reading incoming mail from directory...
| Wrote /home/reader/Mail/mail_cron_tr/30553
| Wrote /home/reader/Mail/mail_rsnap_tr/13838
| Reading incoming mail from file...
| nnml: Reading incoming mail (2 new)...done
| Reading active file via nnml...done
| Reading active file from archive via nnfolder...done
| Reading active file via nndraft...done
| Gnus timed out.
^^^^^^^^^^^^^^
| Entering debugger...
`----
Grep doesn't hit such a words combination in the Gnus source or
the Emacs source, but Google does. For instance, bitbucket[1]
shows this:
(defadvice gnus-group-get-new-news (around gnus-timeout activate)
"Timeout for Gnus."
(with-timeout
(5 (message "Gnus timed out.") (debug))
ad-do-it))
Do you have the one like that in your ~/.gnus.el file? If so,
too small timeout seconds (5 in that case) may cause the problem.
[1] <https://bitbucket.org/kindahero/emacsd/src/9a4c7b1e85a3ee9e80ca53f32260a6bc36e90f8a/init-gnus.el>
next prev parent reply other threads:[~2013-09-26 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 0:01 Harry Putnam
2013-09-26 0:50 ` Katsumi Yamaoka
2013-09-26 20:10 ` Harry Putnam
2013-09-26 22:50 ` Katsumi Yamaoka [this message]
2013-09-27 21:23 ` Harry Putnam
2013-10-01 14:56 ` Harry Putnam
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=b4mtxh7p599.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).