From: Aric <aorchid@mac.com>
To: ding@gnus.org
Subject: Re: Unable to View Messages from NNTP Server
Date: Tue, 25 Jan 2011 20:50:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20110125T214117-856@post.gmane.org> (raw)
In-Reply-To: <864o8wafe4.fsf@mac.com>
Aric Gregson <aorchid <at> mac.com> writes:
>
> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
> > Try `(setq debug-on-quit t)' and post the backtrace you get when it
> > hangs.
>
> Oddly enough, this morning the nntp function is working for the first
> time in over three weeks! Maybe setting the above function in the .gnus
> file did the trick. ;p Either way, I am happy with it for now.
Now I feel odd. Must be intermittent. Immediately after posting the above
message the nntp function started to have trouble. Here is the debug output:
ebugger entered--Lisp error: (quit)
signal(quit nil)
byte-code("H\302V\203^H^@\303^Q\304\305\303\"\207" [tries gnus-async-current-
prefetch-article 3 nil signal quit] 3)
gnus-async-wait-for-article(75957)
gnus-async-request-fetched-article("nntp
+news.gmane.org:gmane.emacs.gnus.general" 75957 #<buffer *Article nntp
+news.gmane.org:gmane.emacs.gnus.general*>)
gnus-request-article-this-buffer(75957 "nntp
+news.gmane.org:gmane.emacs.gnus.general")
gnus-article-prepare(75957 nil)
gnus-summary-display-article(75957)
gnus-summary-next-article(t nil)
gnus-summary-next-unread-article()
call-interactively(gnus-summary-next-unread-article nil nil)
recursive-edit()
byte-code("\306^P @\307=\203!^@\310\311\312\"\210\313\311!
\211^ZA@)\242\314=\203!^@\310\315\312\"\210\316!\210\317 \210\320 !\210\f
\203d^@\321ed\"^MV\203W^@eb\210\322
\245y\210`^^^[db\210\322
\245
Zy\210^N^[`|\210)\323c\210eb\210\324\325\326 \"\210\327\306!\210\324\330!
\210\331\312^^^\^^^\324\330!\210\212\332 \210+\331\207" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1
debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode
debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string kill-
emacs "" nil recursive-edit middlestart buffer-read-only standard-output] 4)
debug(error (void-function nnimap))
(nnimap "Mednet" (nnimap-address "mail.mednet.ucla.edu") (nnimap-stream ssl)
(nnimap-inbox "INBOX") (nnimap-expunge-on-close t) (nnimap-split-methods nnmail-
split-fancy) (nnimap-split-crosspost nil))
(setq gnus-secondary-select-methods (quote (... ... ...)) (nnimap
"Speakeasy" (remove-prefix "INBOX.") (nnimap-address "mail.speakeasy.net")
(nnimap-stream ssl) (nnimap-inbox "INBOX") (nnimap-expunge-on-close t) (nnimap-
split-methods nnmail-split-fancy) (nnimap-split-crosspost nil)) (nnimap
"Mednet" (nnimap-address "mail.mednet.ucla.edu") (nnimap-stream ssl) (nnimap-
inbox "INBOX") (nnimap-expunge-on-close t) (nnimap-split-methods nnmail-split-
fancy) (nnimap-split-crosspost nil)))
eval-buffer(#<buffer *load*> nil "/fitz/home/aorchid/.gnus" nil t) ;
Reading at buffer position 1862
load-with-code-conversion("/fitz/home/aorchid/.gnus" "/fitz/home/
aorchid/.gnus" nil t)
load("~/.gnus" nil t)
gnus-read-init-file()
gnus-1(nil nil nil)
gnus(nil)
call-interactively(gnus t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
next prev parent reply other threads:[~2011-01-25 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 20:43 Aric
2011-01-02 4:56 ` Lars Magne Ingebrigtsen
2011-01-04 1:53 ` Aric
2011-01-04 9:14 ` Steinar Bang
2011-01-04 19:47 ` Aric
2011-01-11 19:34 ` Lars Magne Ingebrigtsen
2011-01-11 21:29 ` Aric
2011-01-22 19:41 ` Lars Ingebrigtsen
2011-01-25 20:37 ` Aric Gregson
2011-01-25 20:50 ` Aric [this message]
2011-01-27 0:54 ` Lars Ingebrigtsen
2011-01-27 1:34 ` Aric
2011-01-27 1:40 ` Lars Ingebrigtsen
2011-01-27 16:54 ` Aric
2011-01-28 1:08 ` Lars Ingebrigtsen
2011-01-29 0:42 ` Aric
2011-01-29 1:20 ` Lars Ingebrigtsen
2011-01-31 20:56 ` Aric
2011-02-01 1:25 ` Lars 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=loom.20110125T214117-856@post.gmane.org \
--to=aorchid@mac.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).