From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: [patch] gnus.texi (Article Washing, Customizing Articles)
Date: Tue, 18 Feb 2003 20:20:40 +0100 [thread overview]
Message-ID: <v9heb1mm47.fsf@marauder.physik.uni-ulm.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi,
a user in the German Gnus newsgroup had problems with the manual
concerning washing. He considered the following patch as helpful.
Could somebody commit it?
--8<---------------cut here---------------start------------->8---
2003-02-18 Reiner Steib <Reiner.Steib@gmx.de>
* gnus.texi (Article Washing): Mention `g'.
(Customizing Articles): Added cross reference.
--8<---------------cut here---------------end--------------->8---
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus.texi.washing.patch --]
[-- Type: text/x-patch, Size: 988 bytes --]
--- gnus.texi.~6.422.~ Thu Feb 13 13:58:25 2003
+++ gnus.texi Tue Feb 18 14:20:23 2003
@@ -8277,6 +8277,13 @@
you type this, you see the article exactly as it exists on disk or on
the server.
+@item g
+Force redisplaying of the current article
+(@code{gnus-summary-show-article}). This is also not really washing.
+If you type this, you see the article without any previously applied
+interactive Washing functions but with all default treatments
+(@pxref{Customizing Articles}).
+
@item W l
@kindex W l (Summary)
@findex gnus-summary-stop-page-breaking
@@ -10692,7 +10699,8 @@
@cindex article customization
A slew of functions for customizing how the articles are to look like
-exist. You can call these functions interactively, or you can have them
+exist. You can call these functions interactively
+(@pxref{Article Washing}), or you can have them
called automatically when you select the articles.
To have them called automatically, you should set the corresponding
[-- Attachment #3: Type: text/plain, Size: 116 bytes --]
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
reply other threads:[~2003-02-18 19:20 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=v9heb1mm47.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--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).