From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: hit r on message you haven't opened yet, go ahead, do it, just do it
Date: Fri, 17 Jan 2003 17:36:49 -0500 [thread overview]
Message-ID: <m31y3bqu7y.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <yqradhzzv9b.fsf@cs.york.ac.uk>
Kester Clegg <kester@RemoveThisBit.cs.york.ac.uk> writes:
> It might be nice though to have an option that turned off seeing *all*
> the headers, which is a bit more information than you generally need.
I prefer the appearance of the *Article* buffer to the raw article
that Gnus provides by default. You can try the following:
(gnus-add-configuration
'(reply
(vertical 1.0
(article 0.5) (message 1.0 point))))
-Nevin
next parent reply other threads:[~2003-01-17 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bs2h2b3j.fsf@jidanni.org>
[not found] ` <yqradhzzv9b.fsf@cs.york.ac.uk>
2003-01-17 22:36 ` Nevin Kapur [this message]
2003-01-19 3:11 Dan Jacobson
2003-01-21 4:43 ` Lars Magne Ingebrigtsen
2003-01-26 4:53 Dan Jacobson
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=m31y3bqu7y.fsf@fermat.mts.jhu.edu \
--to=nevin@jhu.edu \
/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).