Re: [gmane.emacs.devel] gnus-read-mark not preserved

[Katsumi Yamaoka <yamaoka@jpl.org>]

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Hi,

Doesn't your problem apply to this case?  I tried using unpatched
Gnus v5.11 for a couple of these days to read and post mail and news
articles as usual, however I didn't encounter any other trouble.

>>>>> Katsumi Yamaoka wrote:

> The prerequisites to cause this bug are:

> 1. You have persistent (i.e., cached, marked with `*') articles
>    that you have read (or marked as ticked) in a group.

> 2. Some or all of those articles have been expired in the server.

> 3. You have ever performed `gnus-agent-expire' or
>    `gnus-agent-regenerate', or have ever simply deleted the
>    ~/News/agent/ directory.  (In the last case, the directory
>    and files are regenerated automatically.)

> In that case, some or all of persistent articles that have been
> expired in the server are recognized as unfetched articles,
> because the Agent cannot fetch those headers from the server.
> And then, they are all marked as unread when you run the `c'
> command (`gnus-summary-catchup-and-exit'), that recognizes
> unfetched articles as unread articles.

[...]

> The patch for Gnus v5.11 is here:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 561 bytes --]

--- gnus-sum.el~	2007-06-06 15:39:11 +0000
+++ gnus-sum.el	2007-07-04 09:02:52 +0000
@@ -10514,7 +10514,8 @@
 		      (gnus-sorted-nunion
                        (gnus-sorted-intersection gnus-newsgroup-unreads
 						 gnus-newsgroup-downloadable)
-                       gnus-newsgroup-unfetched)))
+		       (gnus-sorted-difference gnus-newsgroup-unfetched
+					       gnus-newsgroup-cached))))
 	    ;; We actually mark all articles as canceled, which we
 	    ;; have to do when using auto-expiry or adaptive scoring.
 	    (gnus-summary-show-all-threads)