From: Galen Boyer <galenboyer@hotpop.com>
Subject: Re: top & bottom posting
Date: 17 Dec 2002 21:20:14 -0600 [thread overview]
Message-ID: <u7ke796ww.fsf@hotpop.com> (raw)
In-Reply-To: <gcsmwwad4b.fsf@kobayashi.uits.iupui.edu>
On Tue, 17 Dec 2002, me@privacy.net wrote:
> ruhl@4dv.net (Robert Uhl <ruhl@4dv.net>) writes:
>
>> This whole discussion has ignored one very important thing:
>> top-posting is to be _very_ strongly discouraged. It is _poor_
>> style, hard to read, difficult to understand and leads to over-long
>> posts--and thus, wastes of bandwidth. It has no good points. So if
>> gnus makes it difficult, this is actually a Good Thing, believe it or
>> not.
>
> Does Gnus have any predefined capacity to invert top-posted threads?
> I *hate* trying to read backwards through a long discussion from a
> group of Outlook users. I've tried gnus-outlook-deuglify-article, but
> it doesn't usually do much.
I started using this a few weeks ago.
(setq gnus-treat-hide-citation t)
Collapses all cited text to a [+]. You need to then have `W W c` handy
to uncollapse. You could make gnus notice you are in a group with
mainly outlook users and this would come in "real" handy.
--
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.
next prev parent reply other threads:[~2002-12-18 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 8:19 Sivaram Neelakantan
2002-12-16 10:07 ` Kai Großjohann
[not found] ` <87n0n52yb1.fsf@kuntu.zangpo.org>
[not found] ` <yy7on0n5qj4i.fsf@css.css.sfu.ca>
[not found] ` <87el8h2g5b.fsf@kuntu.zangpo.org>
[not found] ` <m3y96o3d7v.fsf@latakia.dyndns.org>
2002-12-17 15:17 ` Andrew J. Korty
2002-12-18 3:20 ` Galen Boyer [this message]
2002-12-18 16:13 ` Dave Bennett
2002-12-17 20:57 ` Dave Bennett
2002-12-18 18:14 ` Robert Uhl <ruhl@4dv.net>
[not found] ` <a7043d61.0212162056.fa92f39@posting.google.com>
[not found] ` <84y96png7m.fsf@lucy.cs.uni-dortmund.de>
2002-12-18 13:01 ` Sivaram Neelakantan
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=u7ke796ww.fsf@hotpop.com \
--to=galenboyer@hotpop.com \
/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).