From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: current mail filename
Date: Wed, 11 Jun 2003 09:30:36 +0200 [thread overview]
Message-ID: <v9adcpxe8z.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <j665nej6z6.fsf@explicit.atdesk.com>
On Tue, Jun 10 2003, Chris Uzdavinis wrote:
> I receive some emails using nnml that need an external program to
> process, and would like to setup a key-binding that spawns a shell and
> passes the current mail filename to that script.
Maybe it's good enough to pipe the article to the external program?
Then you can use `|' or `C-u |':
,----[ C-h f gnus-summary-pipe-output RET ]
| gnus-summary-pipe-output is an interactive compiled Lisp function in
| `gnus-sum'.
| (gnus-summary-pipe-output &optional ARG HEADERS)
|
| Pipe the current article to a subprocess.
| [...]
| If HEADERS (the symbolic prefix), include the headers, too.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2003-06-11 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 15:19 Chris Uzdavinis
2003-06-11 6:19 ` Kai Großjohann
2003-06-11 7:30 ` Reiner Steib [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=v9adcpxe8z.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).