From: Francisco Solsona <flsc@hp.fciencias.unam.mx>
Subject: Re: New posted unread articles Marked as read automatically.
Date: 04 May 2000 10:56:52 -0500 [thread overview]
Message-ID: <m1bt2mgvgb.fsf@biblio08.fciencias.unam.mx> (raw)
In-Reply-To: Shigeki Uno's message of "04 May 2000 06:43:18 +0900"
Shigeki Uno <shigeki@mediawars.ne.jp> writes:
> Some of them(* mark) _never show up_ in groups buffer even when new
> articles are posted by someone. At first I didn't know what's going on
> and had been thought that no articles were posted. But I happened to
> check old news articles typing "C-u space" and found that articles
> were _posted_. :-( they were _marked as read automatically_ regardless
> of existence of unread articles, so I couldn't read new ones. This
> happens every day and on cvs-5.8.5/5.8.6/5.8.7.
>
> Is this a bug ? Or am I wrong ?
I'm not sure if this is a bug or not, the same happened to me
a few days ago, and it turned out that I had bogus read ranges stored
somewhere in mi .newsrc.*. I had to `M-c'¹ on each of those groups to
solve the problem. I never found the source of the problem, though.
Have you switched NNTP servers recently? Does this help?
Francisco
Footnotes:
¹ M-c is bounded to:
,---------- Function: gnus-group-clear-data ----------
| `gnus-group-clear-data' is an interactive compiled Lisp function
| -- loaded from "gnus-group"
| (gnus-group-clear-data &optional ARG)
|
| Documentation:
| Clear all marks and read ranges from the current group.
`--------------------
next prev parent reply other threads:[~2000-05-04 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 21:43 Shigeki Uno
2000-05-04 15:56 ` Francisco Solsona [this message]
2000-05-05 18:29 ` New posted unread articles marked " Shigeki Uno
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=m1bt2mgvgb.fsf@biblio08.fciencias.unam.mx \
--to=flsc@hp.fciencias.unam.mx \
/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).