From: dme@dme.org
Subject: problems with nnvirtual and marks
Date: Thu, 03 Jan 2002 13:18:40 +0000 [thread overview]
Message-ID: <x8ecy9jf1sjz.fsf@pantalamion.dme.org> (raw)
Recently I've been playing with reading most of my (new) mail/news
through nnvirtual groups. The behaviour of ticked articles in these
groups seems erratic.
Some times I can enter an nnvirtual group where there should be 2
ticked articles (I ticked them and the group list shows me that there
are two ticked), but none of the ticked articles are listed. If I
exit the summary the ticked article count in the group list goes to
zero.
In some cases I can now quit and restart gnus and the ticked articles
come back. Sometimes they don't.
Occasionally things go rather more wild, and a random selection of
articles get ticked, some previously seen articles are marked unseen
(and vice versa).
All in all, a disconcerting experience !
Any suggestions as to how to track down this problem ? Initially I
thought that perhaps it was because I had:
(gnus-demon-add-handler 'gnus-demon-scan-news 20 20)
in my .gnus.el (as the corruption somewhat coincided with me leaving
Summary buffers visible when new mail was incorporated). I turned
that off and things improved for a while, but it's doing it again now.
I tried:
(setq nnml-marks-is-evil t)
but that didn't seem to have any effect.
Configuration:
- GNU Emacs 21.1.2 (i386-debian-linux-gnu, X toolkit) of
2001-10-22 on peppermint
- Oort Gnus v0.05 (cvs update this morning)
- mail in nnml groups
- news on a local nntp server (leafnode).
Any suggestions as to possible causes or how to debug ? The fact that
I can run for a few days without seeing the problem is making it
frustrating.
dme.
next reply other threads:[~2002-01-03 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 13:18 dme [this message]
2002-01-07 16:24 ` dme
2002-01-19 19:45 ` Lars Magne Ingebrigtsen
2002-01-21 22:31 ` Paul Jarc
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=x8ecy9jf1sjz.fsf@pantalamion.dme.org \
--to=dme@dme.org \
/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).