From: Peter Davis <pd@world.std.com>
Subject: Re: Sending message from template?
Date: 15 Jan 2003 15:57:54 -0500 [thread overview]
Message-ID: <y95mi10t.fsf@bitstream.com> (raw)
In-Reply-To: <geg.y1yznq3s7yg.fsf@fly.verified.de>
Raymond Scholz <ray-2003@zonix.de> writes:
> * Peter Davis <pd@world.std.com> wrote:
>
> > That works pretty well, but I don't see any automatic way to insert
> > the contents of a file.
>
> (body (with-temp-buffer
> (insert-file-contents "foo.txt")
> (buffer-string)))
Works like a champ. Thanks!
I'm still not totally happy with using posting styles for this, but it
might be workable. I have to redo my splitting to put all and only
the messages I need to handle in this way in a separate group.
Thanks all!
-pd
--
--------
Peter Davis
Funny stuff at http://www.pfdstudio.com
The artwork formerly shown as prints
List of resources for children's writers and illustrators at:
http://www.pfdstudio.com/cwrl.html
prev parent reply other threads:[~2003-01-15 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 16:56 Peter Davis
[not found] ` <7kd736w4.fsf@hschmi22.userfqdn.rz-online.de>
[not found] ` <of6jo6c0.fsf@bitstream.com>
2003-01-14 22:05 ` Raymond Scholz
2003-01-15 20:57 ` Peter Davis [this message]
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=y95mi10t.fsf@bitstream.com \
--to=pd@world.std.com \
/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).