From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Partial IMAP article fetch
Date: Sun, 26 Sep 2010 16:41:25 -0400 [thread overview]
Message-ID: <87lj6oi6fe.fsf@uwo.ca> (raw)
In-Reply-To: <m3y6apztsq.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I've now implemented IMAP particle article fetch. That took a lot
> more code than I thought.
>
> (setq nnimap-fetch-partial-articles "text/")
>
> to test.
I tried
(setq gnus-fetch-partial-articles "text/")
and got the following on an article with a text part, a pdf part and
then a text part. (This in the only article I tried.)
Dan
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
nnimap-insert-partial-structure((("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "1" NIL NIL) ("application" "pdf" NIL NIL NIL "base64" 213264 NIL ("attachment" ...) "2" NIL) ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "3" NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL) (("3" "\nMore text.\n") ("1" "Some text.\n\n")))
nnimap-convert-partial-article((("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "1" NIL NIL) ("application" "pdf" NIL NIL NIL "base64" 213264 NIL ("attachment" ...) "2" NIL) ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "3" NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL))
nnimap-get-partial-article(5723 ("1" "3") (("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "1" NIL NIL) ("application" "pdf" NIL NIL NIL "base64" 213264 NIL ("attachment" ...) "2" NIL) ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 14 2 NIL "3" NIL NIL) "mixed" ("boundary" "=-=-=") NIL NIL NIL))
nnimap-request-article(5723 "INBOX" "rocky" #<buffer *Article nnimap+rocky:INBOX*>)
gnus-request-article(5723 "nnimap+rocky:INBOX" #<buffer *Article nnimap+rocky:INBOX*>)
gnus-request-article-this-buffer(5723 "nnimap+rocky:INBOX")
gnus-article-prepare(5723 nil)
gnus-summary-display-article(5723 nil)
gnus-summary-select-article(nil nil pseudo)
gnus-summary-scroll-up(1)
call-interactively(gnus-summary-scroll-up nil nil)
next prev parent reply other threads:[~2010-09-26 20:41 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 [this message]
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
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=87lj6oi6fe.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).