unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Adam Funk <a24061@yahoo.com>
Subject: Re: How to pipe text or load a file directly into mail-mode?
Date: Wed, 3 May 2006 20:05:49 +0100	[thread overview]
Message-ID: <dhbni3-bbt.ln1@news.ducksburg.com> (raw)
In-Reply-To: 86psivug6u.fsf@gothmog.pc

On 2006-05-03, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> On Wed, 3 May 2006 16:05:54 +0100, Adam Funk <a24061@yahoo.com> wrote:
>> On 2006-05-03, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
>>> On Wed, 3 May 2006 12:29:03 +0100, Adam Funk <a24061@yahoo.com> wrote:
>>>> I'd like the output of a Perl program to end up in an Emacs mail-mode
>>>> buffer, ready to proofread, edit and then send with C-c C-c.  I don't
>>>> mind whether my program
>>>>
>>>> 1. pipes the output to an emacs command, or
>>>>
>>>> 2. saves the output in a temp file and opens it with an emacs command.
>>
>> I forgot to make something clear: emacs is *not* running when the Perl
>> program starts.  The Perl program generates the unedited message and
>> then launches emacs.
>
> Oh!  I misunderstood you then.  Sorry.

To me it seemed perfectly obvious what I meant, if you know what I
mean.  That's why I get other people to proofread bigger things!


> This is kind of backwards.  I usually let Emacs start other programs as
> inferior processes, instead of the other way around.  Perhaps someone
> more experienced with Emacs can help you with this (i.e. you could write
> a function that can be called with:
>
>     perl script.pl | emacs --batch -f foo-function
>
> and let `foo-function' read from the standard input stream.  But I know
> far too little to do that myself.

I'll look at from that angle and see if I can come up with something
(but my elisp is really bad).

Thanks.

  reply	other threads:[~2006-05-03 19:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 11:29 How to pipe text or load a file directly into mail-mode? Adam Funk
2006-05-03 14:26 ` Giorgos Keramidas
2006-05-03 15:05   ` Adam Funk
2006-05-03 18:16     ` Giorgos Keramidas
2006-05-03 19:05       ` Adam Funk [this message]
2006-05-03 20:35 ` Ralf Fassel
2006-05-04  4:24   ` Giorgos Keramidas
2006-05-04 10:49     ` Adam Funk
2006-05-04 13:16       ` Peter Dyballa
2006-05-04 16:43       ` Ralf Fassel
2006-05-04 19:46         ` Adam Funk
2006-05-04 20:49           ` Giorgos Keramidas
2006-05-05  8:36             ` Adam Funk
2006-05-05 14:26               ` Giorgos Keramidas
2006-05-05 11:17             ` Reiner Steib
2006-05-05 13:54             ` Adam Funk
2006-05-05 12:13           ` Ralf Fassel
2006-05-04 17:13       ` Paul Lalli
2006-05-04 19:27         ` Adam Funk
2006-05-05 21:39       ` John Sullivan
2006-05-09 11:00 ` Adam Funk
2006-05-09 11:48   ` Ralf Fassel
2006-05-09 12:15     ` Adam Funk
2006-05-09 14:16     ` Adam Funk
2006-05-09 14:30       ` Ralf Fassel
2006-05-10  8:23         ` Adam Funk
2006-05-10 12:11           ` Ralf Fassel
2006-05-10 12:22             ` Adam Funk

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dhbni3-bbt.ln1@news.ducksburg.com \
    --to=a24061@yahoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).