Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill White <billw@wolfram.com>
Subject: documentation bug in 0.96
Date: 30 Aug 1999 11:10:35 -0500	[thread overview]
Message-ID: <ruod7w5xn9g.fsf@g.wolfram.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

Pterodactyl Gnus v0.96

See info node Gnus -> The Summary Buffer -> Article Treatment ->
Article Washing. The command 'W q' is listed for
'gnus-article-fill-long-lines', then it's listed a few items later for
'gnus-article-de-quoted-unreadable'. The first listing should be 'W
Q'. 

,----
| `W q'
|      Fill long lines (`gnus-article-fill-long-lines').
| 
| <snip>
| 
| `W q'
|      Treat quoted-printable (`gnus-article-de-quoted-unreadable').
|      Quoted-Printable is one common MIME encoding employed when sending
|      non-ASCII (i. e., 8-bit) articles.  It typically makes strings like
|      `déjà vu' look like `d=E9j=E0 vu', which doesn't look very
|      readable to me.  Note that the this is usually done automatically
|      by Gnus if the message in question has a
|      `Content-Transfer-Encoding' header that says that this encoding
|      has been done.
`----

Here's a patch:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch for documentation W-q bug --]
[-- Type: text/x-patch, Size: 405 bytes --]

--- gnus.texi	Mon Aug 30 11:06:05 1999
+++ gnus.texi~	Fri Aug 27 08:17:19 1999
@@ -6727,9 +6727,9 @@
 You can give the command a numerical prefix to specify the width to use
 when filling.
 
-@item W Q
-@kindex W Q (Summary)
-@findex gnus-article-fill-long-lines 
+@item W q
+@kindex W q (Summary)
+@findex gnus-article-fill-long-lines
 Fill long lines (@code{gnus-article-fill-long-lines}).
 
 @item W C

[-- Attachment #3: Type: text/plain, Size: 81 bytes --]


Cheers -

bw
-- 
Bill White . billw@wolfram.com . http://members.wri.com/billw


                 reply	other threads:[~1999-08-30 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ruod7w5xn9g.fsf@g.wolfram.com \
    --to=billw@wolfram.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).