From: David Moore <dmoore@UCSD.EDU>
Subject: Re: Danger! Danger!
Date: 26 Nov 1996 11:18:43 -0800 [thread overview]
Message-ID: <rvpw108y24.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Steven L Baur's message of 26 Nov 1996 10:07:58 -0800
Steven L Baur <steve@miranova.com> writes:
> >>>>> "Samuel" == Samuel Tardieu <sam@inf.enst.fr> writes:
> >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>
> Lars> It seems like Red Gnus 0.71 (and possibly previous versions as
> Lars> well) is removing ticks from articles. This has dramatic
> Lars> consequences if you're using total-expiry on some of your mail
> Lars> groups.
>
> Samuel> I can confirm this: this has been present in the last versions, and I
> Samuel> had to retick almost everything by hand.
>
> Ouch. I'm noticing a different effect. I'm having some messages that
> are counted as unread in the *Group* buffer disappear into the ether.
I used to notice this occasionally, and thought it was related
to crossposts or duplication or NoCeM. But in 0.70 it's happening _a
lot_. Also now sometimes when I enter a group, read all of the articles
and exit, the group buffer will say '1' instead of '0', but when I go
into it, nothing's there of course.
But definitely with 0.70, I'm seeing that if I Gcc myself
something and also get the same message via mail, the odds seem high of
that thing showing up as 'already read'. But I think it's also
happening with other incoming mail, so it's probably not just a gcc
problem.
nnmail-split-history and the 'j' command in the summary window
helps me track down these errant messages, but I might be missing a lot
too.
--
David Moore <dmoore@ucsd.edu> | Computer Systems Lab __o
UCSD Dept. Computer Science - 0114 | Work: (619) 534-8604 _ \<,_
La Jolla, CA 92093-0114 | Fax: (619) 534-1445 (_)/ (_)
<URL:http://oj.egbt.org/dmoore/> | Solo Furnace Creek 508 -- 1996!
next prev parent reply other threads:[~1996-11-26 19:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-26 17:12 Lars Magne Ingebrigtsen
1996-11-26 17:23 ` Samuel Tardieu
1996-11-26 18:07 ` Steven L Baur
1996-11-26 19:18 ` David Moore [this message]
1996-11-26 20:02 ` Sudish Joseph
1996-11-26 21:18 ` Per Abrahamsen
1996-11-26 22:42 ` Steven L Baur
1996-11-26 22:52 ` Sudish Joseph
1996-11-26 22:48 ` Steven L Baur
1996-11-26 23:18 ` Sudish Joseph
1996-11-26 23:57 ` Steven L Baur
1996-11-27 2:15 ` Lars Magne Ingebrigtsen
1996-11-27 16:36 ` Steven L Baur
1996-11-27 1:54 ` Lars Magne Ingebrigtsen
1996-11-27 10:31 ` Hrvoje Niksic
1996-11-27 11:47 ` Lars Magne Ingebrigtsen
1996-11-27 14:26 ` Karl Kleinpaste
1996-11-27 12:22 ` Karl Kleinpaste
1996-11-27 1:49 ` Lars Magne Ingebrigtsen
1996-11-27 3:07 ` David Moore
1996-11-27 5:54 ` Mark Boyns
1996-11-29 8:26 ` Lars Magne Ingebrigtsen
1996-11-27 10:12 ` Steinar Bang
1996-11-26 19:39 ` Samuel Tardieu
1996-11-26 19:53 ` Per Abrahamsen
1996-11-26 20:20 ` David Moore
1996-11-27 2:18 ` Lars Magne Ingebrigtsen
1996-11-27 10:11 ` Steinar Bang
1996-11-27 10:23 ` Lars Magne Ingebrigtsen
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=rvpw108y24.fsf@sdnp5.ucsd.edu \
--to=dmoore@ucsd.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).