From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Piping article + header
Date: Thu, 04 Jul 2002 12:29:44 +0200 [thread overview]
Message-ID: <vaflm8rhjl3.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m24rffubnf.fsf@tnuctip.rychter.com> (Jan Rychter's message of "Thu, 04 Jul 2002 10:42:44 +0200")
Jan Rychter <jan@rychter.com> writes:
>>>>>> "Kai" == Kai Gro <Kai.Grossjohann@CS.Uni-Dortmund.DE>:
> Kai> Vin Shelton <acs@xemacs.org> writes:
> >> D'oh! Yes, that seems pretty simple.
>
> Kai> It's only a workaround, though. Hm. It's not clear to me whether
> Kai> the headers should be there or not. It seems easy enough to
> Kai> decide what to pass to the shell command by hitting `t' or `C-u g'
> Kai> or suchlike first, but it's so _manual_. Hm.
>
> Kai> Does anyone have an idea what should happen?
>
> Why would you ever want to pipe an article *without* headers?
Note that `|' pipes the headers you see, instead of no headers at all.
People might have been doing `| lpr', and surely there it makes sense
to pipe only the displayed (presumably, the important) headers,
instead of all headers.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
prev parent reply other threads:[~2002-07-04 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 16:40 Vin Shelton
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 [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=vaflm8rhjl3.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).