Re: `gnus-unseen-mark' everywhere

[Simon Josefsson <jas@extundo.com>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

>>  ((seen 54 (74 . 75) 78 (86 . 88) 102 109 113 (118 . 119))
>
> [...]
>
>> from ~/Mail/Aljoscha-IN/.marks
>> ((tick 54 (74 . 75) 78 (86 . 88) 102 109 113)
>>  (read (1 . 117))
>>  (reply 54 76 (78 . 79) 82 85 (87 . 90) 95 (97 . 100) 103 (105 . 111)
>>   (113 . 116))
>>  (forward 78 93))
>
> So it would seem as if the `seen' marks don't land in .marks, and this
> makes all your mail appear as unseen.  I'm not really familiar with
> the .marks code, so could somebody else have a go at this?

This is intended as a feature -- Gnus (i.e. .newsrc.eld) remembers
`seen' marks.  Backends remembers `recent' marks.  If the backend
would remember `seen', it would make the two flags have the same
semantics. (I'd admit that the semantic difference between the two is
a little obscure, but I find the distinction useful.)  See below.

But the seen mark should go away once you have seen the message once.
(Assuming you don't use several Gnus installations or delete
.newsrc.eld, or something.)  Doesn't this happen?

;; Propagate flags to server, with the following exceptions:
;; `seen' is private to each gnus installation
;; `cache' is a internal gnus flag for each gnus installation
;; `download' is a agent flag private to each gnus installation
;; `unsend' are for nndraft groups only
;; `score' is not a proper mark
(defconst gnus-article-unpropagated-mark-lists
  '(seen cache download unsend score)
  "Marks that shouldn't be propagated to backends.
Typical marks are those that make no sense in a standalone backend,
such as a mark that says whether an article is stored in the cache
(which doesn't make sense in a standalone backend).")