Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Problems with .newsrc.eld (aws: Re: self-contained nnml)
Date: Tue, 21 Aug 2001 14:13:43 -0400	[thread overview]
Message-ID: <m3g0alth5e.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0108211823260.25862-100000@slipsten.extundo.com> (Simon Josefsson's message of "Tue, 21 Aug 2001 18:31:23 +0200 (CEST)")

Simon Josefsson <jas@extundo.com> wrote:
> On Tue, 21 Aug 2001, Daniel Pittman wrote:
>> Well, group parameters such as the `to-list' and `to-address', I would
>> expect to transfer and back-up correctly. If I stopped backing up the
>> .eld file and they got lost, I would go find a corner and cry or
>> something. :)
> 
> Well, one point of the `.marks' file is that you don't need to backup
> .newsrc.eld at all, so I think it would be good to put more backend
> state in it.

The problem here is that there is no analogue of -request-set-mark for
group parameters.  If Gnus changes marks, then the backend finds out
via -request-set-mark.  So the next time Gnus asks for marks with
-request-update-info, the backend knows that its marks are at least as
accurate as Gnus's current marks, and it can assume any differences
are an inaccuracy in Gnus's marks and correct them.  But with group
parameters, the backend has no way to decide whether Gnus's current
parameters or the backend's stored parameters are more accurate.
-request-update-info is the only way the backend ever gets parameters
from Gnus, but also the only way it has to change Gnus's parameters.


paul


  reply	other threads:[~2001-08-21 18:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 11:34 self-contained nnml Simon Josefsson
2001-08-18 15:40 ` Kai Großjohann
2001-08-18 16:42   ` Simon Josefsson
2001-08-19  6:21     ` Daniel Pittman
2001-08-19  9:44       ` Simon Josefsson
2001-08-20  2:35         ` Problems with .newsrc.eld (aws: Re: self-contained nnml) Daniel Pittman
2001-08-20  3:18           ` Daniel Pittman
2001-08-20  9:23           ` Simon Josefsson
2001-08-21  5:07             ` Daniel Pittman
2001-08-21 16:31               ` Simon Josefsson
2001-08-21 18:13                 ` Paul Jarc [this message]
2001-08-21 20:30                   ` Simon Josefsson
2001-08-21 23:57                     ` Daniel Pittman
2001-08-21 23:56                 ` Daniel Pittman
2001-08-24 23:00 ` self-contained nnml Rob Browning
2001-08-25  0:20   ` Rob Browning
2001-08-25  0:58     ` Rob Browning
2001-08-25  2:11       ` ShengHuo ZHU
2001-08-26 18:15         ` Rob Browning
2001-08-25  9:43     ` Simon Josefsson
2001-08-26 15:29       ` Rob Browning
2001-08-26 16:32         ` Simon Josefsson
2001-08-26 18:28           ` Rob Browning

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=m3g0alth5e.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.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).