Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 20670@debbugs.gnu.org
Cc: Nikolaus Rath <Nikolaus@rath.org>, ding@gnus.org
Subject: bug#20670: [PATCH] nnimap: enable additional expunge options (v3)
Date: Fri, 27 Sep 2019 01:41:42 +0200	[thread overview]
Message-ID: <87v9teeibt.fsf@gnus.org> (raw)
In-Reply-To: <87wpdk9em7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 25 Jan 2017 01:18:08 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 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))

I've now re-applied the patch and debugged a bit.  It was basically
nnimap-delete-article having some code paths that can't have been
exercised.  The function had an optional SYNC parameter, but
nnimap-command was called (which is not asynchronous and does not return
any sequence numbers), and then these non-sequences were being waited
for.

I've now pushed the patch to the trunk, I've used it and send and
received some messages, and things seem to work fine.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-09-26 23:41 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
2017-01-25 16:45               ` Lars Ingebrigtsen
2019-09-26 23:41         ` Lars Ingebrigtsen [this message]
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=87v9teeibt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=20670@debbugs.gnu.org \
    --cc=Nikolaus@rath.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).