From: jvinson@cheux.ecs.umass.edu (Jack Vinson)
Subject: Re: Articles spuriously marked as read?
Date: 19 Mar 1996 09:04:30 -0500 [thread overview]
Message-ID: <wo4trli3gx.fsf@cheux.ecs.umass.edu> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 19 Mar 1996 02:24:52 +0100
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
LMI> So I've started to suspect that Gnus is marking unread articles as
LMI> read.
I usually credit this to the nature of the Usenet. Sometimes followups to
articles appear before the original, and sometimes articles expire locally
before I ever see the original.
I've actually noticed the reverse situation, though. There are articles
(Usenet, never mail) that I am s\b_u\b_r\b_e\b_ I have read once that I see
again. This usually happens in the larger groups that I read, so it is
entirely possible that people are reposting the same articles because they
didn't see their words immediately.
--
Jack Vinson jvinson@cheux.ecs.umass.edu
"Narf!" - Pinky <http://www.cis.upenn.edu/~vinson/home.html>
next prev parent reply other threads:[~1996-03-19 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-19 1:24 Lars Magne Ingebrigtsen
1996-03-19 13:47 ` David C Worenklein
1996-03-19 20:55 ` Lars Magne Ingebrigtsen
1996-03-19 14:04 ` Jack Vinson [this message]
1996-03-19 17:31 ` Per Persson
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=wo4trli3gx.fsf@cheux.ecs.umass.edu \
--to=jvinson@cheux.ecs.umass.edu \
/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).