Gnus development mailing list
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: ding@gnus.org
Subject: Re: [PATCH] Use IMAP MOVE extension if available
Date: Mon, 20 Jul 2015 09:18:17 -0700	[thread overview]
Message-ID: <87wpxuerau.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <87y4ibf93c.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 20 Jul 2015 17:53:59 +0800")

On Jul 20 2015, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Nikolaus Rath <Nikolaus@rath.org> writes:
>
>> Hello,
>>
>> The attached revision fixes a small error when parsing the response to
>> the UID MOVE command. Previously, it would fail to find the COPYUID
>> response and fall back to using the message id to determine the UID of
>> the copied message.
>
> I'm running these patches locally, and (I think) seeing more hangs than
> I used to. This only happens on first startup of Gnus. I set
> toggle-debug-on-quit to t, and quit on the next hang -- see the
> traceback below.
>
> This is connecting to a dovecot server running on localhost. The first
> thing this tells me is that the MOVE capability (which dovecot provides)
> isn't getting noticed by Gnus -- as you noted in your previous exchange
> with Lars (was there no resolution to that?). That does need to get
> fixed, otherwise Gnus is missing a lot of added functionality.

I think I've addressed Lars' comments, so for me the proper resolution
would be for someone to apply the patch :-).


> The other thing is this hang. I'm not immediately inclined to blame Gnus
> for this, but the fact is that this a local connection and there
> shouldn't be anything stalling it. If anyone has any bright ideas...
>
>   nnimap-wait-for-response(85)
>   nnimap-get-response(85)
>   nnimap-command("UID STORE %s +FLAGS.SILENT (\\Deleted)" "")
>   nnimap-delete-article(nil t)

What's the content of the " *nnimap..." buffer at this point? (note the
leading space).


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«



  reply	other threads:[~2015-07-20 16:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  0:29 Nikolaus Rath
2015-07-16  9:00 ` Eric Abrahamsen
2015-07-20  9:53 ` Eric Abrahamsen
2015-07-20 16:18   ` Nikolaus Rath [this message]
2015-07-27  4:36     ` Eric Abrahamsen
2015-07-27 16:10       ` Nikolaus Rath
2015-08-02  5:56         ` Eric Abrahamsen
2015-08-02 23:36           ` Nikolaus Rath
2015-08-03  0:40             ` Eric Abrahamsen
2015-08-03  1:08             ` Dan Christensen
2015-08-03  8:17               ` Steinar Bang
2015-08-03 17:18                 ` Nikolaus Rath
2015-08-04  3:17                   ` Eric Abrahamsen
2015-08-04 17:28                     ` Nikolaus Rath
2015-08-05  1:53                       ` Eric Abrahamsen
  -- strict thread matches above, loose matches on Subject: below --
2015-05-25 19:59 Nikolaus Rath
2015-07-07  2:59 ` Eric Abrahamsen
2015-07-07  3:05 ` Eric Abrahamsen
2015-07-09  2:13   ` Nikolaus Rath
2015-07-09  2:18     ` Eric Abrahamsen

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=87wpxuerau.fsf@thinkpad.rath.org \
    --to=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).