From: Joel Mayes <j.mayes@optushome.com.au>
Subject: Re: how to view all headers?
Date: 17 Aug 2002 13:52:46 +1000 [thread overview]
Message-ID: <87k7mq9m5t.fsf@bluebird.zenith> (raw)
In-Reply-To: <87k7mqz22w.fsf@gnulinux.org.mx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Edgar Antonio Luna Díaz <kheb@gnulinux.org.mx> writes:
>
> t runs the command gnus-summary-toggle-header
Perfect, Thank you :)
- --
Sourcemage GNU/Linux /~\ ASCII Ribbon campaign
Linux so advanced it may as well be magic \_/ stop HTML mail and news
x11 & doc section maintainer / \
http://search.keyserver.net:11371/pks/lookup?op=vindex&search=0x47856819
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE9XciMWxU5n0eFaBkRAqf7AKCMWqS/t4O7bfQca9SZhOuRNEwOOQCfTVtX
V4BuxwSUV/WQvpch9wTJPr0=
=Bxyv
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-08-17 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vg6affrz.fsf@bluebird.zenith>
2002-08-17 1:49 ` Edgar Antonio Luna Díaz
2002-08-17 3:52 ` Joel Mayes [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=87k7mq9m5t.fsf@bluebird.zenith \
--to=j.mayes@optushome.com.au \
/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).