From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: C-g on IMAP and no such article
Date: Wed, 20 Oct 2010 12:32:41 +0200 [thread overview]
Message-ID: <sa3lj5txigm.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <m3lj5v9s7i.fsf@quimbies.gnus.org>
On Mon, Oct 18 2010, Lars Magne Ingebrigtsen wrote:
> There's two ways: Binding `inhibit-quit', and using a `condition-case'
> that ignores `quit'. So doing a `debug-on-entry' on, say,
> `nnimap-request-article', and you'll see the call tree, and then you can
> inspect the tree for those forms...
Well, anyhow I've found part of the problem.
First, I've set nnimap-fetch-partial-articles and there was a bug I
fixed in commit eb6b2e4e9bff924ab4f864323acf973b25643460.
Then, there seems to be some… race condition. I can bypass the bug in
the debugger, but not without it. When it raises that:
Debugger entered--entering a function:
* nnimap-get-response(1762)
nnimap-command("UID FETCH %d (%s %s)" 26382 "BODY.PEEK[HEADER]" "BODY.PEEK[1]")
nnimap-get-partial-article(26382 ("1") (("text" "plain" ("charset"
"us-ascii") nil nil "7bit" 2 1 nil "1" nil nil) [...] )
...
It *seems* that if I wait for the *nnimap* buffer to show the OK
response line, the code works fine. However, if I don't, therefore if
I'm not in the debugger, it hangs for ever. Note that the
nnimap-wait-response loop seems OK since I hitted search-backward a
couple of times with it returning nil, and then returning an integer and
I was available to execute the whole things without a problem.
So far I'm stuck.
Another thing I noticed while I'm at it. The message I used to test was
compose of a text/plain and a message/rfc822. I had
nnimap-fetch-partial-articles set to "text/", and all I got was an empty
message, since the sender did not write anything. But I did not had any
MIME part buttons, so it was hard to know there was another mime part
which was a message/ one. I've added message/ to the
nnimap-fetch-partial-articles regexp so I can see it.
Maybe there is some code thinking it's useless to show button for such a
mime part since we used to always show them inline? I don't know.
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
next prev parent reply other threads:[~2010-10-20 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 15:34 Julien Danjou
2010-10-18 19:21 ` Lars Magne Ingebrigtsen
2010-10-18 19:56 ` Julien Danjou
2010-10-18 19:58 ` Lars Magne Ingebrigtsen
2010-10-18 20:05 ` Julien Danjou
2010-10-18 20:11 ` Lars Magne Ingebrigtsen
2010-10-20 10:32 ` Julien Danjou [this message]
2010-10-21 1:26 ` Lars Magne Ingebrigtsen
2010-10-21 9:17 ` Julien Danjou
2010-10-21 16:00 ` Lars Magne Ingebrigtsen
2010-10-21 16:21 ` Julien Danjou
2010-10-21 16:25 ` 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=sa3lj5txigm.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--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).