Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gnus mailing list <ding@gnus.org>
Subject: Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")
Date: Wed, 02 Mar 2011 20:24:17 +0100	[thread overview]
Message-ID: <87lj0x72ce.fsf@member.fsf.org> (raw)
In-Reply-To: <m2d3m94ab1.fsf@igel.home> (Andreas Schwab's message of "Wed, 02 Mar 2011 20:00:34 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

>> But I'm still interested what that number actually means?
>
> This is an opaque (unsigned 64-bit) value updated by the server
> whenever a metadata item is modified (RFC4551).

That's a bit unfortunate.  Today I've encountered 2 of these values that
were too big to be `read' by emacs.

Looking at `nnimap-parse-flags' I can see that the value of UIDVALIDITY
is extracted by string-matching and stored as string, because it might
be bigger than an emacs integer.  Probably the same has to be done for
the FETCH lines.

Here's the offending code:

--8<---------------cut here---------------start------------->8---
	  (while (re-search-forward "^\\* [0-9]+ FETCH " start t)
	    (setq elems (read (current-buffer)))
	    (push (cons (cadr (memq 'UID elems))
			(cadr (memq 'FLAGS elems)))
		  articles))
--8<---------------cut here---------------end--------------->8---

Of course, it is convenient to `read' the complete list in lines like

  * 2971 FETCH (FLAGS (%Recent) UID 12509 MODSEQ (13419098521433281274))

but it fails for large numbers.  And if the RFC says those are 64bit
unsigned ints, well, then Gnus has to handle those.

Bye,
Tassilo

  ...who wonders why he got this error twice today after using Gnus with
  IMAP servers (including that problematic one) for several years with
  no such issue at all...



  reply	other threads:[~2011-03-02 19:24 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 [this message]
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
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=87lj0x72ce.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.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).