From: "Stefan Reichör" <xsteve@riic.at>
Subject: Problems, getting new news
Date: Mon, 23 Aug 2004 14:56:56 +0200 [thread overview]
Message-ID: <w4disbanhbb.fsf@nanni.riic.uni-linz.ac.at> (raw)
Hi!
I use the developer version of gnus.
Since some time I get no new news for some groups.
I use the agent to download the articles.
When I fetch the articles, only some groups are considerd.
In the other groups I get no indication, that there are new articles
available.
See the messages for a fetching session:
Fetching headers for comp.lang.lisp...
Fetching articles for comp.lang.lisp...
Fetching headers for comp.lang.python...
Fetching articles for comp.lang.python...
Fetching headers for de.comp.text.tex...
Fetching articles for de.comp.text.tex...
Finished fetching articles into the Gnus agent
The articles in the above groups are correctly fetched.
But there are some other groups, where I didn't get new data since
some months.
Any ideas, how to debug that situation?
I'd really like to read gnu.emacs.gnus, comp.emacs and others again!
I experimented a bit and found out, that I can subscribe new groups
and everything works with the new subscribed groups.
I have some ticked articles in my already subscribed (no longer
working) groups. It would be fine, if I could keep that old articles
and could start reading that groups again.
How can I debug that situation?
Stefan.
reply other threads:[~2004-08-23 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=w4disbanhbb.fsf@nanni.riic.uni-linz.ac.at \
--to=xsteve@riic.at \
/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).