Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: gnus from cvs and leafnode
Date: Wed, 03 Aug 2005 11:39:19 +1000	[thread overview]
Message-ID: <873bprlry0.fsf@rimspace.net> (raw)
In-Reply-To: <m3u0iamy2r.fsf@alienoid.is.ua>

Ruslan Spivak <rspivak@nuxeo.com> writes:

> I have following problem with latest emacs + gnus from cvs + leafnode:
> when i enter summary buffer for 2 of subscribed
> groups on localhost served by leafnode nntp server
> (gmane.comp.web.zope.zope3 and gmane.comp.web.zope.zope3.cvs) there are
> leafnode placeholders for every article in the group and number of
> articles in group buffer for those 2 groups are incorrect.

[...]

> Version of leafnode is 1.11.3

I run the same versions of Gnus and Leafnode, under XEmacs, and don't
see this issue.  I don't read those specific gmane groups, but do read
others (like this one) that way.

So, it is probably a somewhat local (or Emacs specific) issue.
    Daniel





      reply	other threads:[~2005-08-03  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 22:04 Ruslan Spivak
2005-08-03  1:39 ` Daniel Pittman [this message]

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=873bprlry0.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    /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).