Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Partial IMAP article fetch
Date: Wed, 29 Sep 2010 19:58:29 +0200	[thread overview]
Message-ID: <87y6ak8m9m.fsf@dod.no> (raw)
In-Reply-To: <m37hi44mys.fsf@quimbies.gnus.org>

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Julien Danjou <julien@danjou.info> writes:
>> Same here, with a mail on this list

> With that backtrace, I was able to reproduce the bug, and it's possibly
> fixed now.

It doesn't crash for me anymore on the LinkedIn article, but what shows
up in the *Article* buffer is this:

7169	LinkedIn Network Updates, 9/28/2010 	LinkedIn Updates <updates@linkedin.com> 	Tue, 28 Sep 2010 07:40:57 -0700 (PDT) 	<213149815.58720010.1285684857650.JavaMail.app@ech3-cdn43.prod>		16003	69		Id: 	Ip: 	Queue: 	
pp

This is also the content of the file
 ~/News/agent/nnimap/privat/dod/7169

If I press `A C' the article appears (the text/plain part I
think... maybe... I'm trying to suppress HTML as much as possible, but
with the new HTML support I'm not really sure what's happening).

But the agent article isn't updated.  It still contains the text above.
Probably not much good when offlined...? :-)

Do you need the article to test with?







  reply	other threads:[~2010-09-29 17:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 16:12 Lars Magne Ingebrigtsen
2010-09-25 17:11 ` Lars Magne Ingebrigtsen
2010-09-26 20:41 ` Dan Christensen
2010-09-27 18:27   ` Lars Magne Ingebrigtsen
2010-09-27 18:45     ` Dan Christensen
2010-09-27 18:49       ` Dan Christensen
2010-09-27 19:25         ` Lars Magne Ingebrigtsen
2010-09-28  1:18           ` Dan Christensen
2010-09-28 16:05             ` Steinar Bang
2010-09-28 16:14               ` Steinar Bang
2010-09-28 16:16               ` Julien Danjou
2010-09-29 14:56                 ` Lars Magne Ingebrigtsen
2010-09-29 17:58                   ` Steinar Bang [this message]
2010-09-29 19:04                     ` Lars Magne Ingebrigtsen
2010-09-29 19:16                       ` Steinar Bang
2010-09-29 19:30                         ` Lars Magne Ingebrigtsen
2010-09-29 19:55                           ` Steinar Bang
2010-09-29 20:12                             ` Lars Magne Ingebrigtsen
2010-09-29 20:24                               ` Steinar Bang
2010-09-29 22:10                                 ` Lars Magne Ingebrigtsen
2010-09-29 22:11                                 ` Lars Magne Ingebrigtsen
2010-09-29 22:15                                   ` Lars Magne Ingebrigtsen
2010-09-30 18:42                                     ` Steinar Bang
2010-09-29 21:21                           ` Andreas Schwab
2010-09-29 21:23                             ` Lars Magne Ingebrigtsen
2010-09-29 22:45                               ` Andreas Schwab
2010-09-29 18:43                   ` Julien Danjou
2010-09-29 18:59                     ` Lars Magne Ingebrigtsen
2010-09-26 20:45 ` Dan Christensen
2010-09-26 20:55   ` Lars Magne Ingebrigtsen
2010-09-27  7:43   ` Steinar Bang
2010-09-27 18:35     ` Lars Magne Ingebrigtsen
2010-09-27 15:19   ` Richard Riley
2010-09-27 18:35     ` 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=87y6ak8m9m.fsf@dod.no \
    --to=sb@dod.no \
    --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).