Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: "Can't read partial active file"
Date: Fri, 09 Jan 2004 12:38:42 -0500	[thread overview]
Message-ID: <zncxrpi5.fsf@boost-consulting.com> (raw)
In-Reply-To: <ptdtqgfk.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> After updating Gnus from CVS this morning and byte-recompiling it with
> Gnu Emacs, when I start it up I get the following sequence of messages
> in my *messages* buffer:
>
>   Compiling format specs...
>   Compiling user specs...done
>   Reading c:/cygwin/home/dave/.newsrc.eld...
>   Reading active file from www.stlport.com via nnimap...
>   Cannot read partial active file from nnimap server.
>   Reading active file from news.rcn.com via nntp...
>   Opening nntp server on news.rcn.com...done
>   Cannot read partial active file from nntp server.
>   Reading active file from news.gmane.org via nntp...
>   Opening nntp server on news.gmane.org...done
>   Cannot read partial active file from nntp server.
>   Checking new news...done
>   No gnus is bad news
>   No more unread newsgroups
>
> And the groups display comes up looking wrong (lots of *s in the
> left-hand column).  Any clues?

Note: this makes Gnus completely unusable under Gnu emacs; I can't
enter any groups.  It works great under XEmacs, though.  What could
the problem be?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




  reply	other threads:[~2004-01-09 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 15:39 David Abrahams
2004-01-09 17:38 ` David Abrahams [this message]
2004-01-09 20:50   ` Steve Youngs
2004-01-10  1:36     ` David Abrahams
2004-01-10  2:10       ` Jesper Harder

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=zncxrpi5.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    /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).