Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Mon, 16 Aug 2004 17:31:06 +0200	[thread overview]
Message-ID: <ilud61r3xs5.fsf@latte.josefsson.org> (raw)
In-Reply-To: <jk4oelbqg7c.fsf@W003275.na.alarismed.com>

"Steven E. Harris" <seh@panix.com> writes:

>> For flags, syncing ~/News/marks/ should suffice, if the marks stuff
>> is working for nntp.
>
> Looking in some of the .marks files under my ~/[News]/marks directory,
> I see that there is a "read" sexp with ranges that match .newsrc. So
> perhaps .marks is /all/ I need to sync NNTP.
>
> Can anyone comment on how Gnus reconciles differences between the
> .marks files and .newsrc[.eld]? Which ones will take precedence?

.marks will take precedence, that was the reason for introducing the
"marks" backend interface.  I.e., to allow backends to override what
Gnus knows about groups (from newsrc.eld).  Nnimap uses this to tell
Gnus about flag changes on the server.  Later it was realized that
nnml and nnfolder could benefit from the same interface, to allow
synchronization of nnml/nnfolder's to carry flags with them.

>> Can anyone comment on how Gnus reconciles differences between the
>> .marks files and .newsrc[.eld]? Which ones will take precedence?
>
> Following up to myself, I just tried an experiment. I exited Gnus and
> manually edited one of my .marks files to back off the read range by a
> single message, leaving the corresponding entries in .newsrc and
> .newsrc.eld untouched. Upon restarting Gnus, the Group and Summary
> buffer reflected that I had not read the last article in the edited
> group.
>
> So it does seem that if NNTP can be synced with the .marks files, and
> IMAP groups don't need .newsrc.eld, then I can stop syncing .newsrc
> and .newsrc.eld -- topic changes notwithstanding.

Yup.

> Are there any files that nnimap groups do need synced, or can they
> recover /everything/ Gnus knows about them from the server?

Some esoteric things aren't synced via the server.  For example:
bookmarks, group parameters (but use `gnus-parameters' instead),
topics.  I think we've eliminated all major values.

To see what is stored in .newsrc.eld for a group, type `G E' on it.
Anything there you don't see in .marks won't be synced.




  parent reply	other threads:[~2004-08-16 15:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson [this message]
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris
2004-08-16 19:54         ` Steven E. Harris
2004-08-17 11:39         ` Steinar Bang

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=ilud61r3xs5.fsf@latte.josefsson.org \
    --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).