From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/1479 Path: news.gmane.org!not-for-mail From: Paul Moore Newsgroups: gmane.emacs.gnus.user Subject: Write the raw text of an article to a pipe Date: Sun, 17 Nov 2002 19:09:49 +0000 Message-ID: <7kfcj9mq.fsf@morpheus.demon.co.uk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668239 11442 80.91.229.2 (31 Jan 2006 00:43:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:43:59 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:29:13 2006 Original-Path: quimby.gnus.org!news.ccs.neu.edu!news.dfci.harvard.edu!news.cis.ohio-state.edu!news.ems.psu.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: morpheus.demon.co.uk Original-X-Trace: news.demon.co.uk 1037565005 3416 158.152.8.30 (17 Nov 2002 20:30:05 GMT) Original-X-Complaints-To: abuse@demon.net Original-NNTP-Posting-Date: Sun, 17 Nov 2002 20:30:05 +0000 (UTC) Cancel-Lock: sha1:6aMcnoRKJKlERSecwL3MyuXYdTM= User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.5 (brussels sprouts, i586-pc-win32) Hamster/1.3.23.191 Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:1619 Original-Lines: 21 X-Gnus-Article-Number: 1619 Tue Jan 17 17:29:13 2006 Xref: news.gmane.org gmane.emacs.gnus.user:1479 Archived-At: I want to write the current message out to a program. The "|" command doesn't quite do it, because as far as I can tell, it writes the currently *displayed* article text out, not the raw article. So it is affected by such things as "t" (toggle headers). The other output commands (such as "O m") seem to output the raw header. Is there anything I can do to get this behaviour for a pipe? I notice that gnus-original-article-buffer has the original of the article currently being displayed - but I'm after the original of the article selected in the summary buffer (with all the usual process mark stuff, etc) so that's not quite what I'm after) Thanks, Paul PS I've looked at the code, and I can't see what makes | act differently from O m. I'm guessing it's something simple, but I can't see it... -- This signature intentionally left blank