From: kbk@shore.net (Kurt B. Kaiser)
Subject: Re: Show Raw Article
Date: Tue, 30 Apr 2002 13:41:24 GMT [thread overview]
Message-ID: <m3pu0hpafh.fsf@float.attbi.com> (raw)
In-Reply-To: <vpqit697gpk.fsf@montrose.imag.fr>
Matthieu Moy <MatthieuNOSPAM.Moy@imag.fr.invalid> writes:
> kbk@shore.net (Kurt B. Kaiser) writes:
>
> > Um, how do I show the raw text of an article with all headers which
> > were in the _body_ of the article? (This has to do with sending headers
> > to an abuse address)
>
> C-u g shows the raw article.
Thanks to you and ireneo.funes! That is exactly what I was looking for.
I guess I didn't expect to find the docs for this in the "Scrolling
the Article (Paging the Article)" node, and hidden as a prefix switch.
The "Choosing Articles" node might be more appropriate. There are a
couple of other neat things in the Scrolling node, like the s and h
commands, which save a couple of keystrokes ;)
> `t' shows all the headers, but not in the body, but with C-o to
> shows the structure of the message,
C-o ?
> select the forwarded message, and then, `t', it works.
>
> > I sent an article to myself using S o m, it looked nice with all
> > headers in the body but when I received it they were "gone".
>
> Be carefull to the fact that this removes some headers (see
> message-forward-ignored-headers)
Yes. I guess the default ignored ones aren't too important.
Regards, KBK
next prev parent reply other threads:[~2002-04-30 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3elgyq77o.fsf@float.attbi.com>
2002-04-30 8:07 ` Matthieu Moy
2002-04-30 13:41 ` Kurt B. Kaiser [this message]
[not found] ` <yobofg1p949.fsf@panix1.panix.com>
[not found] ` <vpqwuup448b.fsf@montrose.imag.fr>
2002-04-30 15:32 ` BreadWithSpam
[not found] ` <lylmb5vywm.fsf@gfn.org>
[not found] ` <vafu1prvv6k.fsf@lucy.cs.uni-dortmund.de>
2002-05-02 18:50 ` Scott Gifford
[not found] ` <lmb2wepc.fsf@random.localnet.UnwiredUniverse.com>
2002-05-03 7:49 ` those who know me have no need of my name
[not found] ` <vafelgtjy9w.fsf@lucy.cs.uni-dortmund.de>
2002-05-03 19:04 ` Scott Gifford
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=m3pu0hpafh.fsf@float.attbi.com \
--to=kbk@shore.net \
/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).