From: Simon Josefsson <jas@extundo.com>
Subject: Re: `gnus-unseen-mark' everywhere
Date: Thu, 03 Jan 2002 22:45:22 +0100 [thread overview]
Message-ID: <iluy9jfxg5p.fsf@extundo.com> (raw)
In-Reply-To: <m3y9jfdvka.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Thu, 03 Jan 2002 15:32:31 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
> Simon Josefsson <jas@extundo.com> wrote:
>> 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.
>
> You're making assumptions about how sharing can be done that happen to
> be false for nnmaildir. In a shared nnmaildir group, typically the
> marks are all not shared and only the messages are, but it's also
> possible to share some kinds of marks and not others.
This seems to be the same as for nnimap.
> If other backends cannot do this, then I think it should be those
> backends that decide to not store (nor update Gnus's copy of) the
> seen marks, rather than Gnus that assumes that backends are
> incapable of handling it properly.
Ah. Hm, I think I understand what you are saying. If the backend
doesn't support the distinction between per-user and global marks, it
should rely on .newsrc.eld and not touch the mark. Nnml/nnfolder would
not store seen in .marks, and would not reset the info handed to it
via nnchoke-request-update-info. I think I agree now. :-) It wouldn't
change how anything would work. Yes.
The gnus-article-unpropagatable-p etc stuff should be moved into
nnml/nnfolder (perhaps nnmail) then, because we wouldn't want `seen'
marks to be stored in nnml .marks. Hm, but this means the backends
has knowledge about the semantics of marks, which is wrong as well.
So, either Gnus assumes that backends should only handle global marks
(current solution), or the assumption is that backends need to be
aware that, e.g., seen marks should not be stored in the backend if it
can only provide global marks. It would be nice if the backend
wouldn't have to make that kind of distinction (because the backend
shouldn't have to "understand" all flags Gnus uses).
Ok, I now convinced myself that none of the solutions is good. Time
to sleep..
next prev parent reply other threads:[~2002-01-03 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 11:33 Robert Epprecht
2001-12-30 21:37 ` Lars Magne Ingebrigtsen
2001-12-31 7:11 ` Robert Epprecht
2001-12-31 7:37 ` Lars Magne Ingebrigtsen
2001-12-31 13:15 ` Simon Josefsson
2002-01-02 7:24 ` Robert Epprecht
2002-01-08 6:34 ` Maciej Matysiak
2002-01-03 19:53 ` Paul Jarc
2002-01-03 20:21 ` Simon Josefsson
2002-01-03 20:32 ` Paul Jarc
2002-01-03 21:45 ` Simon Josefsson [this message]
2002-01-03 21:59 ` Paul Jarc
2002-01-04 20:43 ` Simon Josefsson
2002-01-04 21:12 ` Paul Jarc
2002-01-04 21:27 ` Simon Josefsson
2002-01-04 22:01 ` Paul Jarc
2002-01-04 22:44 ` Simon Josefsson
2002-01-05 1:00 ` Paul Jarc
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=iluy9jfxg5p.fsf@extundo.com \
--to=jas@extundo.com \
/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).