Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Gnus 5.10.2 - agent and lost marks
Date: Sun, 18 May 2003 19:40:37 -0400	[thread overview]
Message-ID: <u1xyvq0wa.fsf@boost-consulting.com> (raw)


I've been noticing recently that often I'll mark a message as
expirable or read or I'll use gnus-summary-kill-thread, and then do a
gnus-summary-rescan-group and the message comes back.  For a while I
thought I was hallucinating, or that it was only happening to messages
whose bodies had not been downloaded yet.  Today I got a message from
RMS about an elisp patch I posted to the emacs.devel NG, and no matter
what I do to it, it keeps coming back.  It's spooky!  Are messages
from RMS given some special status in emacs?

Seriously, though: this is pretty weird.  This is happening in my
agentized nnimap inbox.  Is there something I can/should do about
it?  I'm happy to run a few experiments if it will be useful...

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




             reply	other threads:[~2003-05-18 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 23:40 David Abrahams [this message]
2003-05-19  4:12 ` Kevin Greiner

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=u1xyvq0wa.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    /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).