From: "B.V. Raghav" <bvraghav@iitk.ac.in>
To: Kevin Brubeck Unhammer <unhammer@fsfe.org>
Cc: info-gnus-english@gnu.org
Subject: Re: gnus-range-difference((nil . 95923) nil) → (wrong-type-argument number-or-marker-p nil)
Date: Sat, 09 Apr 2016 11:33:13 +0530 [thread overview]
Message-ID: <87y48n2uam.fsf@ram.bvr.dp.lan> (raw)
In-Reply-To: <87vb3tlvub.fsf@fsfe.org> (Kevin Brubeck Unhammer's message of "Thu, 07 Apr 2016 09:30:20 +0200")
Kevin Brubeck Unhammer <unhammer@fsfe.org> writes:
>
> "commits" is a dovecot IMAP folder, synced by offlineimap to fastmail. My workaround is to delete
>
> ("commits" (3 . 8) ((1 . 95923)) ((unexist (1 . 75894) (75896... [SNIPPED]
>
> From .newsrc.eld, but it keeps coming back. I've also tried deleting
> "commits" from .newsrc, to no avail. It seems like a bug in gnus (though
Thanks Kevin for the direction.
In my case, it is the another remote imap server `nnimap:r-bvr' and one
of the folder pops out with an error in the debugger. I do not know
why, or cant predict which one?
I took the deleted part from .newsrc.eld in two subsequent runs, and
ediff-ed it. Following were the observations (n, m, a1, a2, b all are
numbers):
1. there is a difference in the `modseq' cdr. For example,
(modseq . "n") changes to (modseq . "m")
or
(modseq . "n") changes to (modseq) - or vice versa
2. there is a difference in active cdr. For example,
(active a1 . b) changes to (active a2 . b)
Does that ring any bell?
r
--
(B.V. Raghav)
Ph.D. Student,
Design Programme, IIT Kanpur
next prev parent reply other threads:[~2016-04-09 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 7:30 Kevin Brubeck Unhammer
2016-04-08 12:29 ` B.V. Raghav
2016-04-08 13:26 ` Kevin Brubeck Unhammer
2016-04-14 9:40 ` Kevin Brubeck Unhammer
2016-04-09 6:03 ` B.V. Raghav [this message]
2016-04-09 8:54 ` Kevin Brubeck Unhammer
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=87y48n2uam.fsf@ram.bvr.dp.lan \
--to=bvraghav@iitk.ac.in \
--cc=info-gnus-english@gnu.org \
--cc=unhammer@fsfe.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).