From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")
Date: Sat, 05 Mar 2011 11:55:05 +0100 [thread overview]
Message-ID: <m3vczxsupi.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87lj0x4k59.fsf@fastmail.fm>
Tassilo Horn <tassilo@member.fsf.org> writes:
> * 2971 FETCH (FLAGS (%Recent) UID 12509 MODSEQ (13419098521433281274))
I think the best way to handle this is to make the MODSEQ into a string
if it's more than mumble number of characters long.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-03-05 10:55 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
2011-03-05 10:52 ` Lars Magne Ingebrigtsen
2011-03-05 10:55 ` Lars Magne Ingebrigtsen [this message]
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=m3vczxsupi.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).