From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Doc. bugs Node: Hiding Headers etc.
Date: 15 Mar 2001 23:03:47 +0100 [thread overview]
Message-ID: <vafwv9qsn98.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <yz5ae6nd9vv.fsf@burn.cs.utah.edu> (Sriram Karra's message of "14 Mar 2001 19:49:24 -0700")
On 14 Mar 2001, Sriram Karra wrote:
> Is someone (or group) into actively maintaining the gnus manual? I
> was wondering if some simple corrections to the manual would be
> acceptable here?
You can also make bug reports for this kind of thing. Thanks for this
report.
> I would try this time anyways:
>
> (1) In the node `Hiding Headers', there is a mention of the variable
> gnus-treat-hide-boring-header , when it should actually be
> gnus-treat-hide-boring-headers.
Thanks, fixed.
> (2) In the same node, a little below that, it says
> "To include the four three elements, you could say something
> like;" - needs fixing?
Thanks, fixed.
> (3) In the node `Group Parameters', would it not be nice to have a
> pointer to gnus-group-edit-group-parameters, or a word about how
> exactly one goes about setting these parameters - I mean, this
> node has great visibility, by showing up on the Top node of
> gnus. So I would guess a lot of people would start here on
> Group Parameters...
Fwiw, I see some mention of `G p' and `G c' near the bottom of that
node. Is this the case in your version, too?
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-03-15 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 2:49 Sriram Karra
2001-03-15 22:03 ` Kai Großjohann [this message]
2001-03-15 23:15 ` Sriram Karra
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=vafwv9qsn98.fsf@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).