From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")
Date: Fri, 04 Mar 2011 08:59:32 -0600 [thread overview]
Message-ID: <87hbbj7wyz.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxlcpqs9.fsf@member.fsf.org>
On Thu, 03 Mar 2011 09:11:18 +0100 Tassilo Horn <tassilo@member.fsf.org> wrote:
TH> I've now combined both approaches. A condition-case handler simply
TH> deletes the big number and `read's again. That fixes the issue for me.
TH> I added a FIXME and comment, too. Maybe Lars has some better idea how
TH> to deal with that.
Cool, thanks.
TH> Since that number occurs as value of MODSEQ (which Gnus doesn't use), is
TH> the HIGHESTMODSEQ (which Gnus reads and stores as number) also a
TH> candidate for overflowing? It probably is, so it might be better to
TH> handle it as string just like the UIDVALIDITY.
I agree and would suggest at this point a generic Gnus approach to
reading large numbers rather than one-off hacks.
Ted
next prev parent reply other threads:[~2011-03-04 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 15:28 Tassilo Horn
2011-03-02 17:52 ` Tassilo Horn
2011-03-02 19:00 ` Andreas Schwab
2011-03-02 19:24 ` Tassilo Horn
2011-03-02 20:17 ` Ted Zlatanov
2011-03-02 20:36 ` Tassilo Horn
2011-03-02 20:52 ` Andreas Schwab
2011-03-02 21:02 ` Tassilo Horn
2011-03-02 20:56 ` Ted Zlatanov
2011-03-03 8:11 ` Tassilo Horn
2011-03-04 14:59 ` Ted Zlatanov [this message]
2011-03-05 10:52 ` Lars Magne Ingebrigtsen
2011-03-05 10:55 ` Lars Magne Ingebrigtsen
2011-03-07 17:29 ` Ted Zlatanov
2011-03-15 16:50 ` Lars Magne Ingebrigtsen
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=87hbbj7wyz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).