From: Nikolaus Rath <Nikolaus@rath.org>
To: Lars Ingebrigtsen <larsi@gnus.org>,20670@debbugs.gnu.org
Cc: ding@gnus.org
Subject: Re: bug#20670: [PATCH] nnimap: enable additional expunge options (v3)
Date: Tue, 24 Jan 2017 16:32:06 -0800 [thread overview]
Message-ID: <0C68B28B-69C6-4086-AA99-14A7829695FE@rath.org> (raw)
In-Reply-To: <87r33s9edg.fsf@gnus.org>
On January 24, 2017 4:23:23 PM PST, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>>> There was a bug in the patch, so I've reverted it for now.
>>>
>>> Here's the backtrace:
>>>
>>> Debugger entered--Lisp error: (error "Format specifier doesn’t match
>>> argument type")
>>> format("%d .*\n" (t ("OK" ("HIGHESTMODSEQ" "914696") "Expunge"
>>> "completed.") ("VANISHED" "1825937") ("0" "RECENT")))
>>> (looking-at (format "%d .*\n" sequence))
>>> (not (looking-at (format "%d .*\n" sequence)))
>>> (progn (while (and (not (bobp)) (progn (forward-line -1)
>(looking-at
>> [...]
>>
>> Can you tell me how to reproduce it? As I've said, it's been working
>> fine here for over a year.
>
>I just hit `g'. Whenever there's a new email that's split, it fails.
Uh, OK. That's gonna take me a while to understand and fix. If you or anyone else feels like fixing this up, I will not be offended. I hate the way Gnus represents a "parsed" server response.
Best,
Nikolaus
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-01-25 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <556538A5.3050302@rath.org>
2015-07-04 3:28 ` Nikolaus Rath
2017-01-24 19:35 ` bug#20670: " Lars Ingebrigtsen
2017-01-24 23:37 ` Nikolaus Rath
2017-01-24 23:46 ` Lars Ingebrigtsen
2017-01-25 0:18 ` Lars Ingebrigtsen
2017-01-25 0:22 ` Nikolaus Rath
2017-01-25 0:23 ` Lars Ingebrigtsen
2017-01-25 0:32 ` Nikolaus Rath [this message]
2017-01-25 16:45 ` Lars Ingebrigtsen
2019-09-26 23:41 ` Lars Ingebrigtsen
2017-01-25 0:24 ` npostavs
2017-01-25 0:25 ` Lars 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=0C68B28B-69C6-4086-AA99-14A7829695FE@rath.org \
--to=nikolaus@rath.org \
--cc=20670@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=larsi@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).