Gnus development mailing list
 help / color / mirror / Atom feed
From: Karra <karra@cs.utah.edu>
Subject: Marks woes on upgrade from oort 0.03 -> 0.04.
Date: Thu, 03 Jan 2002 16:43:18 +0530	[thread overview]
Message-ID: <87666jpu0h.fsf@cs.utah.edu> (raw)


On upgrading, I found that the read marks are all gone.  I believe I
read another report on this before.  But the wierdness does not end
there.  Let me explain:

(a) I installed 0.04 and started emacs.  I started gnus with M-x
    gnus-unpluged RET
(b) A gory sight greeted me --- a gazillion unread messages.
(c) I thought for a second and quickly pressed 'q' to quit from.
(d) After a few deep breaths, I did the M-x gnus-unplugged RET
    routine, and lo and behold!!  things were as they should have
    been.
(e) I repeated the above steps (from starting emacs) to confirm this
    behaviour.
(f) In one pass, during the second gnus invocation, I entered a group
    and changed some marks, 's'ed in *Group* buffer and quit emacs.
    Then I restarted Emacs.  Again all groups showed unread messages
    _except_ the group I had just edited.
(g) I restarted Emacs and did (setq nnml-marks-is-evil t) and life
    appeared normal.

Is there a fix for this in CVS?

-- 
"Have you ever fought an IDEA, Picard?"
      -- Gowron, Star Trek TNG.



             reply	other threads:[~2002-01-03 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 11:13 Karra [this message]
2002-01-05 16:23 ` Lars Magne Ingebrigtsen
2002-01-13  0:16   ` Karra
2002-01-13  4:05     ` Paul Jarc
2002-01-19 22:10     ` 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=87666jpu0h.fsf@cs.utah.edu \
    --to=karra@cs.utah.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).