From: John Magolske <listmail@b79.net>
To: ding@gnus.org
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: writing a function that pipes the html mime part to an external script
Date: Fri, 20 Jan 2017 12:04:51 -0800 [thread overview]
Message-ID: <87o9z1fqfw.fsf@b79.net> (raw)
In-Reply-To: <87vat9zjtv.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 20 Jan 2017 10:07:24 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> John Magolske <listmail@b79.net> writes:
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> Write a function that calls mm-pipe-part directly.
>>
>> This is where I'm stuck... I believe there should be something like
>>
>> (mm-pipe-part HANDLE "~/bin/pipe_to_tmp")
>>
>> in the function, but I can't figure out exactly what should go in the
>> place of HANDLE here.
>
> You can get the various article part handles with
> `gnus-article-mime-handles', is that what you were looking for?
I just tried that in an article buffer, got this:
((1 #<buffer *mm*> ("text/html" (charset . "UTF-8"))
quoted-printable nil nil nil nil nil))
and am wondering which part of that is HANDLE ...
I tried:
Eval: (mm-pipe-part "text/html" "~/bin/pipe_to_tmp")
(wrong-type-argument listp "text/html") in eval
Eval: (mm-pipe-part ("text/html" (charset . "UTF-8")) "~/bin/pipe_to_tmp")
(invalid-function "text/html") in mm-pipe-part
John
--
John Magolske
http://b79.net/contact
next prev parent reply other threads:[~2017-01-20 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 6:59 John Magolske
2017-01-20 10:41 ` Andreas Schwab
2017-01-20 15:56 ` John Magolske
2017-01-20 17:51 ` Andreas Schwab
2017-01-20 18:24 ` John Magolske
2017-02-02 8:33 ` John Magolske
2017-01-20 18:07 ` Eric Abrahamsen
2017-01-20 20:04 ` John Magolske [this message]
2017-01-20 20:34 ` 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=87o9z1fqfw.fsf@b79.net \
--to=listmail@b79.net \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).