Gnus development mailing list
 help / color / mirror / Atom feed
From: Vin Shelton <acs@xemacs.org>
Subject: Piping article + header
Date: Wed, 03 Jul 2002 12:40:16 -0400	[thread overview]
Message-ID: <545vg7wwyrz.fsf@icd.teradyne.com> (raw)

I need to be able to save an article as a file with a name based on
its message-id.  In order to do this, I wrote a simple filter (in
*gasp* perl - I know, I should probably turn in my XEmacs decoder ring
for not using elisp, but I thought it would be cool to have something
that worked from the shell command line).  The filter extracts the
message-id from the header and saves the message to a file name based
on the message-id.  This works fine standalone, but when I try to use
gnus-summary-pipe-output, the Message-id: header has been elided from
the article.  If I add 'Message-id' to gnus-visible-headers, my filter
works fine, but that's a pretty yucky solution, 'cause most of the
time I don't want to see the message-id.

Basically what I need is a way to make all headers visible before
calling gnus-summary-pipe-output.  I tried using advice to do this:

  (defadvice gnus-summary-pipe-output
    (around acs::show-all-headers-visible activate)
    "Make all headers visible before piping the message to a program"
    (let ((gnus-show-all-headers t))
          ad-do-it))

but it appears that gnus-show-all-headers must be non-nil _at the time
the article is displayed_.  Essentially, my advice had no effect.

Is there any way to make the entire article (header + body) available
to my filter?  Does anyone have any thoughts, comments or suggestions?

TIA,
  Vin

-- 
In a minute there is time
For decisions and revisions which a minute will reverse.         T.S. Eliot
[URL: http://www.cs.amherst.edu/~ccm/prufrock.html]



             reply	other threads:[~2002-07-03 16:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-03 16:40 Vin Shelton [this message]
2002-07-03 16:49 ` Kai Großjohann
2002-07-03 17:07   ` Vin Shelton
2002-07-03 20:59     ` Kai Großjohann
2002-07-03 22:15       ` Frank Schmitt
2002-07-04  7:55         ` Sean Neakums
2002-07-04 10:28         ` Kai Großjohann
2002-07-04 10:34           ` Sean Neakums
2002-07-04 11:44             ` Kai Großjohann
2002-07-04 12:29               ` Sean Neakums
2002-12-30 19:29                 ` Lars Magne Ingebrigtsen
     [not found]       ` <m24rffubnf.fsf@tnuctip.rychter.com>
2002-07-04 10:29         ` Kai Großjohann

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=545vg7wwyrz.fsf@icd.teradyne.com \
    --to=acs@xemacs.org \
    /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).