Gnus development mailing list
 help / color / mirror / Atom feed
From: Nevin Kapur <nevin@jhu.edu>
Subject: Losing marks in (agentized) nnimap groups
Date: Mon, 14 Jan 2002 12:35:59 -0500	[thread overview]
Message-ID: <m3n0zgna54.fsf@fermat.mts.jhu.edu> (raw)

Hi, I'm running latest Oort and am seeing this problem:

Each time I get new mail in an nnimap group, all my tick marks are
getting lost in that group.  Previously, I was running Oort from about
a week ago and did not see this problem.  I'll try and do a regression.

cvs up -D '7 days ago' does not show this problem.
cvs up -D '3 days ago' does not show this problem.
cvs up -D '1 day ago' does show this problem.
cvs up -D '2 days ago' does not show this problem.
cvs up -D '1 day 12 hours ago' does show this problem.
cvs up -D '1 day 18 hours ago' does show this problem.
cvs up -D '1 day 23 hours ago' does not show this problem.

OK, so here's the diff on the Changelog.  For what it's worth, my
nnimap group *is* agentized.

Index: lisp/ChangeLog
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/ChangeLog,v
retrieving revision 6.1074
retrieving revision 6.1072
diff -u -r6.1074 -r6.1072
--- lisp/ChangeLog	2002/01/12 19:08:01	6.1074
+++ lisp/ChangeLog	2002/01/12 18:20:17	6.1072
@@ -1,12 +1,4 @@
-2002-01-12  ShengHuo ZHU  <zsh@cs.rochester.edu>
-
-	* gnus-agent.el (gnus-agent-retrieve-headers): Erase
-	nntp-server-buffer.
-
 2002-01-12  Lars Magne Ingebrigtsen  <larsi@gnus.org>
-
-	* mm-view.el (mm-display-inline-fontify): Require font-lock to
-	avoid unbinding shadowed variables.
 
 	* gnus-art.el (gnus-picon-databases): Moved here.
 	(gnus-picons-installed-p): Moved here.


-- 
Nevin



                 reply	other threads:[~2002-01-14 17:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3n0zgna54.fsf@fermat.mts.jhu.edu \
    --to=nevin@jhu.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).