Re: `gnus-unseen-mark' everywhere

[Simon Josefsson <jas@extundo.com>]

prj@po.cwru.edu (Paul Jarc) writes:

> Simon Josefsson <jas@extundo.com> wrote:
>> 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 still disagree on that.  It seems to me that the semantic difference
> is only a matter of where changes are initiated for each mark.  This
> ought to be orthogonal to how the marks are stored.

Hm, yes, but I think the issue is mixed if you consider multi-user
scenarios.  Consider a nnml folder which two persons access.  The
recent mark, maintained by nnml.el, is the same for both persons (now,
actually, nnml doesn't set the recent mark, but for sake of argument).
The seen mark however cannot be stored in the backend because they
would become the same for both persons.  The seen mark should be a
kind of "local" seenedness, and "recent" a remote/backend seenedness.

I guess the problem is that the marks are not divided between one set
of global marks that apply to all users of the backend and one local
set of user-specific marks.  Renaming "seen" to "seen-<username>"
would solve that, but perhaps keeping "seen" in .newsrc.eld and
"recent" in the backend is good enough.

Do you see the problem I think I see?