Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [Q]: What can cause a nntp server closure ?
Date: Wed, 13 Oct 2004 00:48:23 +0200	[thread overview]
Message-ID: <plop87hdoz364o.fsf@gnu-rox.org> (raw)

Hello,

As it seems nobody has answered to my previous message concerning
a problem when trying to display an article, I try again here to
see if I can fix something in my configuration.

SO the question is simple: what can cause this:

,----
| Debugger entered--Lisp error: (error "Server closed connection")
|   signal(error ("Server closed connection"))
|   error("Server closed connection")
|   apply(error "Server closed connection")
|   nntp-report("Server closed connection")
|   nntp-accept-process-output(nil)
|   byte-code("\b	=ƒ%
|   gnus-async-wait-for-article(15742)
|   gnus-async-request-fetched-article("nntp+gnu-rox.org:gnus.ding" 15742 #<buffer *Article*>)
|   gnus-request-article-this-buffer(15742 "nntp+gnu-rox.org:gnus.ding")
|   gnus-article-prepare(15742 nil)
|   gnus-summary-display-article(15742 nil)
|   gnus-summary-select-article(nil nil pseudo)
|   gnus-summary-scroll-up(1)
|   call-interactively(gnus-summary-scroll-up)
`----

I really don't see what in my configuration could be tweaked to
fix this problem.

Thank you for your answer.
-- 
Hito no kokoro wa kawareru mono




             reply	other threads:[~2004-10-12 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 22:48 Xavier Maillard [this message]
2004-10-13  7:11 ` [IGNORE] (was: [Q]: What can cause a nntp server closure ?) Xavier Maillard
2004-10-13  9:05   ` password for cancel (was: [IGNORE]) Reiner Steib
2004-10-13 14:56     ` Xavier Maillard
2004-10-13 22:47       ` password for cancel Katsumi Yamaoka
2004-10-14  8:34         ` Reiner Steib
2004-10-14 11:43           ` Katsumi Yamaoka
2004-10-15 17:52             ` Reiner Steib
2004-10-17 22:43               ` Katsumi Yamaoka
2004-10-14 21:38           ` Xavier Maillard
2004-10-15  9:23             ` Cheng Gao

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=plop87hdoz364o.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.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).