From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Pipe message/attachement to shell command
Date: Mon, 12 Nov 2007 09:55:54 -0800 [thread overview]
Message-ID: <1194889791-sup-3292@south> (raw)
In-Reply-To: <1194622205-sup-2949@tomsk>
Excerpts from Marcus Williams's message of Fri Nov 09 07:33:35 -0800 2007:
> William, in the code it says that message.raw_message is slow but
> thats the only way I could do it without creating a string via
> each_raw_message_line. Is there a better way than this?
Hey, this is another reason to use open3 instead of Session. You need to
have access to use the stdin filehandle in order to use
#each_raw_message_line. (There's no speed difference for IMAP, but for
Maildir and mbox, it's quite large. Maildir could be sped up, but mbox
fundamentally not.)
BTW, that first argument to BufferManager#ask should ideally be a symbol
of some sort rather than nil. History is shared amongst all invocations
with the same symbol.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-11-12 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:33 Marcus Williams
2007-11-12 17:55 ` William Morgan [this message]
2007-11-12 22:06 ` Marcus Williams
2007-11-13 11:58 ` Marcus Williams
2007-11-14 9:40 ` Marcus Williams
2007-11-26 20:57 ` Marcus Williams
2007-11-26 21:01 ` Marcus Williams
2007-12-10 6:24 ` William Morgan
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=1194889791-sup-3292@south \
--to=wmorgan-sup@masanjin.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