From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: [Q]: Long lines, wrapping ...
Date: Thu, 21 Oct 2004 14:29:18 +0200 [thread overview]
Message-ID: <v9wtxk1cgx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <plop877jpljx2q.fsf@gnu-rox.org>
On Wed, Oct 20 2004, Xavier Maillard wrote:
> I also have seen the variable `gnus-treat-fill-article' and
> `gnus-treat-fill-long-lines' which if I understand correctly tell
> over functions to do automatic processing on article.
>
> What is the best to use ?
It depends on the type of correction the article needs. Either `W Q'
or `W w' can be appropriate:
`W Q' is for article where the author has forgotten to hit return which will result in very very very loooooooooooooooooooong lines.
`W w' is
nice for strangely
formated stuff
like this.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
parent reply other threads:[~2004-10-21 12:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <plop877jpljx2q.fsf@gnu-rox.org>]
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=v9wtxk1cgx.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).