Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: keramida@ceid.upatras.gr (Giorgos Keramidas)
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Katsumi Yamaoka <yamaoka@jpl.org>,
	ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Mon, 08 Jul 2013 20:24:28 +0200	[thread overview]
Message-ID: <8738ro52qr.fsf@randomsample.de> (raw)
In-Reply-To: <67um8ry59hnqe3.fsf@saturn.laptop> (Giorgos Keramidas's message of "Mon, 08 Jul 2013 15:16:20 +0200")

Giorgos Keramidas writes:
> The messages logged point to 'unexist' for all the groups:

[...]

> Does `unexist' mean that the group does not exist locally? 

No. It means the 'unexist' range is missing, which makes Gnus think this
Group was never synced before.

> I see a few lines above that we check (and active uidvalidity unexist)
> but if 'unexist' means that the groups does not exist in
> `.newsrc.eld', then we are not reading the .newsrc.eld contents
> correctly.

The 'unexist' range contains article numbers which are no longer in the
group (because they were moved or deleted).

First, please make double sure that you are using at least Emacs trunk
rev. 113257, or the latest Gnus from git.

Then, to debug this further: If you hit 'G E' on a group, you see all
the group info with the different ranges. You should see 'unexist' there
somewhere, which can be empty or contain some article numbers or ranges.

When you exit Gnus, this information should be written to the file
newsrc.eld. Unfortunately, that file is barely human readable, but you
can restart Emacs and load it through

(load-file "~/.newsrc.eld")

and then look at the variable `gnus-newsrc-alist'. Do the groups still
have the 'unexist' ranges?

-David




  reply	other threads:[~2013-07-08 18:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 10:40 Katsumi Yamaoka
2013-07-02 16:52 ` Giorgos Keramidas
2013-07-06 15:21   ` Lars Ingebrigtsen
2013-07-06 15:44     ` David Engster
2013-07-06 18:45       ` David Engster
2013-07-06 20:03         ` David Engster
2013-07-07 13:27           ` Giorgos Keramidas
2013-07-07 13:24       ` Giorgos Keramidas
2013-07-07 19:51         ` David Engster
2013-07-08 13:16           ` Giorgos Keramidas
2013-07-08 18:24             ` David Engster [this message]
2013-07-09 11:08               ` Giorgos Keramidas
2013-07-09 15:34                 ` David Engster
2013-07-09 18:16                   ` Giorgos Keramidas
2013-07-09 19:33                     ` David Engster
2013-07-09 19:39                       ` Ted Zlatanov
2013-07-09 20:41                       ` Giorgos Keramidas
2013-07-09 21:42                         ` David Engster
2013-07-10 15:32                           ` Ted Zlatanov
2013-07-10 19:17                           ` David Engster
2013-07-11 17:12                             ` Giorgos Keramidas
2013-07-18 13:31                           ` Lars Magne Ingebrigtsen
2013-07-18 15:42                             ` Giorgos Keramidas
2013-07-18 16:55                               ` David Engster
2013-07-18 17:15                                 ` Giorgos Keramidas
2013-07-30 14:56                               ` Lars Magne Ingebrigtsen
2013-07-30 19:58                                 ` Giorgos Keramidas

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=8738ro52qr.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=keramida@ceid.upatras.gr \
    --cc=larsi@gnus.org \
    --cc=yamaoka@jpl.org \
    /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).