xemacs-beta: man/gnus.texi comparison

comparison man/gnus.texi @ 98:0d2f883870bc r20-1b1

Import from CVS: tag r20-1b1

author	cvs
date	Mon, 13 Aug 2007 09:13:56 +0200
parents	131b0175ea99
children	4be1180a9e89

comparison

equal deleted inserted replaced

-:498bf5da1c90
+:0d2f883870bc
 \input texinfo                  @c -*-texinfo-*-
-@setfilename ../info/gnus.info
+@setfilename gnus
-@settitle Gnus 5.2 Manual
+@settitle Gnus 5.4 Manual
 @synindex fn cp
 @synindex vr cp
 @synindex pg cp
 @iftex
 @finalout
 @iftex
 @iflatex
 \documentclass[twoside,a4paper,openright]{book}
 \usepackage[latin1]{inputenc}
-% \usepackage{fontenc}
-% \usepackage{babel}
 \usepackage{pagestyle}
 \usepackage{epsfig}
-% \usepackage{ifitricks}
 \fontfamily{bembo}\selectfont
 \makeindex
 \begin{document}
 \newcommand{\gnusampersand}{\&}
 \newcommand{\gnuspercent}{\%}
 \newcommand{\gnushash}{\#}
 \newcommand{\gnushat}{\symbol{"5E}}
 \newcommand{\gnusunderline}{\symbol{"5F}}
+\newcommand{\gnusnot}{$\neg$}
 \newcommand{\gnustilde}{\symbol{"7E}}
 \newcommand{\gnusless}{{$<$}}
 \newcommand{\gnusgreater}{{$>$}}
 \newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=gnus-head.eps,height=1cm}}}
 \newcommand{\gnusinteresting}{
 \marginpar[\hspace{2.5cm}\gnushead]{\gnushead}
 }
-\newcommand{\gnuschapter}[1]{
+\newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
+\newcommand{\gnuspagechapter}[1]{
+{\mbox{}}
+}
+\newdimen{\gnusdimen}
+\gnusdimen 0pt
+\newcommand{\gnuschapter}[2]{
+\gnuscleardoublepage
+\ifdim \gnusdimen = 0pt\setcounter{page}{1}\pagestyle{gnus}\pagenumbering{arabic} \gnusdimen 1pt\fi
+\chapter{#2}
 \renewcommand{\gnussectionname}{}
-\chapter{#1}
+\renewcommand{\gnuschaptername}{#2}
-\renewcommand{\gnuschaptername}{#1}
 \thispagestyle{empty}
-% \epsfig{figure=gnus-herd-\arabic{chapter}.eps,height=15cm}
+\hspace*{-2cm}
+\begin{picture}(500,500)(0,0)
+\put(0,0){\makebox(480,350)[tr]{#1}}
+\put(40,300){\makebox(500,50)[bl]{{\Huge\bf{#2}}}}
+\end{picture}
 \clearpage
 }
-\newcommand{\gnusitemx}[1]{\vspace{-\itemsep}\item#1}
+\newcommand{\gnusitemx}[1]{\mbox{}\vspace*{-\itemsep}\vspace*{-\parsep}\item#1}
 \newcommand{\gnussection}[1]{
 \renewcommand{\gnussectionname}{#1}
 \section{#1}
 }
 \newenvironment{emphlist}%
 {\begin{list}{}{
 }
 }{\end{list}}
-\newpagestyle{gnus}%
+\newlength\gnusheadtextwidth
+\setlength{\gnusheadtextwidth}{\headtextwidth}
+\addtolength{\gnusheadtextwidth}{1cm}
+\newpagestyle{gnuspreamble}%
 {
 {
 \ifodd\count0
 {
-\hspace*{-2ex}
+\hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\mbox{}}\textbf{\hfill\roman{page}}}
-\underline{
-\makebox[\headtextwidth]{
-\hspace*{-2.3ex}
-\textbf{\arabic{chapter}.\arabic{section}}
-\textbf{\gnussectionname\hfill\arabic{page}}
-}}
 }
 \else
 {
-\hspace*{-2.25cm}
+\hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\roman{page}\hfill\mbox{}}}
-\underline{
+}
-\hspace*{-2.3ex}
-\makebox[\headtextwidth]{
-\textbf{\arabic{page}\hfill\gnuschaptername}
-}}
 }
 \fi
 }
 }
 {
 \else
 \raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
 \hfill \mbox{}
 \fi
 }
-\pagestyle{gnus}
+\newpagestyle{gnusindex}%
+{
+{
+\ifodd\count0
+{
+\hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\gnuschaptername\hfill\arabic{page}}}}
+}
+\else
+{
+\hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
+}
+\fi
+}
+}
+{
+\ifodd\count0
+\mbox{} \hfill
+\raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
+\else
+\raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
+\hfill \mbox{}
+\fi
+}
+\newpagestyle{gnus}%
+{
+{
+\ifodd\count0
+{
+\hspace*{-0.23cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{chapter}.\arabic{section}} \textbf{\gnussectionname\hfill\arabic{page}}}}
+}
+\else
+{
+\hspace*{-3.25cm}\underline{\makebox[\gnusheadtextwidth]{\textbf{\arabic{page}\hfill\gnuschaptername}}}
+}
+\fi
+}
+}
+{
+\ifodd\count0
+\mbox{} \hfill
+\raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
+\else
+\raisebox{-0.5cm}{\epsfig{figure=gnus-big-logo.eps,height=1cm}}
+\hfill \mbox{}
+\fi
+}
+\pagenumbering{roman}
+\pagestyle{gnuspreamble}
 @end iflatex
 @end iftex
 @iftex
 @end ifinfo
 @tex
 @titlepage
-@title Gnus Manual
+@title Gnus 5.4 Manual
 @author by Lars Magne Ingebrigtsen
 @page
 @vskip 0pt plus 1filll
 You can read news (and mail) from within Emacs by using Gnus.  The news
 can be gotten by any nefarious means you can think of---@sc{nntp}, local
 spool or your mbox file.  All at the same time, if you want to push your
 luck.
+This manual corresponds to Gnus 5.4.
 @end ifinfo
 @iftex
 @iflatex
-\thispagestyle{empty}
+\tableofcontents
+\gnuscleardoublepage
 @end iflatex
 Gnus is the advanced, self-documenting, customizable, extensible
 unreal-time newsreader for GNU Emacs.
 * Appendices::            Terminology, Emacs intro, FAQ, History, Internals.
 * Index::                 Variable, function and concept index.
 * Key Index::             Key Index.
 @end menu
 @node Starting Up
 @chapter Starting Gnus
 @cindex starting up
 @kindex M-x gnus
 @menu
 * Finding the News::    Choosing a method for getting news.
 * The First Time::      What does Gnus do the first time you start it?
 * The Server is Down::  How can I read my mail then?
-* Slave Gnusii::        You can have more than one Gnus active at a time.
+* Slave Gnusae::        You can have more than one Gnus active at a time.
 * Fetching a Group::    Starting Gnus just to read a group.
 * New Groups::          What is Gnus supposed to do with new groups?
 * Startup Files::       Those pesky startup files---@file{.newsrc}.
 * Auto Save::           Recovering from a crash.
 * The Active File::     Reading the active file over a slow line Takes Time.
+* Changing Servers::    You may want to move from one server to another.
 * Startup Variables::   Other variables you might change.
 @end menu
 @node Finding the News
 @section Finding the News
+@cindex finding news
 @vindex gnus-select-method
 @c @head
 The @code{gnus-select-method} variable says where Gnus should look for
 news.  This variable should be a list where the first element says
 If this variable is not set, Gnus will take a look at the
 @code{NNTPSERVER} environment variable.  If that variable isn't set,
 Gnus will see whether @code{gnus-nntpserver-file}
 (@file{/etc/nntpserver} by default) has any opinions on the matter.  If
 that fails as well, Gnus will will try to use the machine that is
-running Emacs as an @sc{nntp} server.  That's a long-shot, though.
+running Emacs as an @sc{nntp} server.  That's a long shot, though.
 @vindex gnus-nntp-server
 If @code{gnus-nntp-server} is set, this variable will override
 @code{gnus-select-method}.  You should therefore set
 @code{gnus-nntp-server} to @code{nil}, which is what it is by default.
 for some reason or other.  If you decide to continue and have no foreign
 groups, you'll find it difficult to actually do anything in the group
 buffer.  But, hey, that's your problem.  Blllrph!
 @findex gnus-no-server
+@kindex M-x gnus-no-server
 @c @head
 If you know that the server is definitely down, or you just want to read
 your mail without bothering with the server at all, you can use the
 @code{gnus-no-server} command to start Gnus.  That might come in handy
-if you're in a hurry as well.
+if you're in a hurry as well.  This command will not attempt to contact
+your primary server---instead, it will just activate all groups on level
+1 and 2.  (You should preferably keep no native groups on those two
-@node Slave Gnusii
+levels.)
-@section Slave Gnusi�
+@node Slave Gnusae
+@section Slave Gnusae
 @cindex slave
 You might want to run more than one Emacs with more than one Gnus at the
-same time.  If you are using different @file{.newsrc} files (eg., if you
+same time.  If you are using different @file{.newsrc} files (e.g., if you
-are using the two different Gnusi� to read from two different servers),
+are using the two different Gnusae to read from two different servers),
 that is no problem whatsoever.  You just do it.
-The problem appears when you want to run two Gnusi� that use the same
+The problem appears when you want to run two Gnusae that use the same
 @code{.newsrc} file.
 To work around that problem some, we here at the Think-Tank at the Gnus
 Towers have come up with a new concept: @dfn{Masters} and
-@dfn{servants}.  (We have applied for a patent on this concept, and have
+@dfn{slaves}.  (We have applied for a patent on this concept, and have
 taken out a copyright on those words.  If you wish to use those words in
 conjunction with each other, you have to send $1 per usage instance to
 me.  Usage of the patent (@dfn{Master/Slave Relationships In Computer
 Applications}) will be much more expensive, of course.)
 Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or
-however you do it).  Each subsequent slave Gnusi� should be started with
+however you do it).  Each subsequent slave Gnusae should be started with
 @kbd{M-x gnus-slave}.  These slaves won't save normal @file{.newsrc}
-files, but instead save @dfn{slave files} that contains information only
+files, but instead save @dfn{slave files} that contain information only
 on what groups have been read in the slave session.  When a master Gnus
 starts, it will read (and delete) these slave files, incorporating all
 information from them.  (The slave files will be read in the sequence
 they were created, so the latest changes will have precedence.)
 Information from the slave files has, of course, precedence over the
-information in the normal (i. e., master) @code{.newsrc} file.
+information in the normal (i.e., master) @code{.newsrc} file.
 @node Fetching a Group
 @section Fetching a Group
+@cindex fetching a group
 @findex gnus-fetch-group
-It it sometime convenient to be able to just say ``I want to read this
+It it sometimes convenient to be able to just say ``I want to read this
 group and I don't care whether Gnus has been started or not''.  This is
 perhaps more useful for people who write code than for users, but the
 command @code{gnus-fetch-group} provides this functionality in any case.
 It takes the group name as a parameter.
 @node New Groups
 @section New Groups
 @cindex new groups
+@cindex subscription
+@vindex gnus-check-new-newsgroups
+If you are satisfied that you really never want to see any new groups,
+you can set @code{gnus-check-new-newsgroups} to @code{nil}.  This will
+also save you some time at startup.  Even if this variable is
+@code{nil}, you can always subscribe to the new groups just by pressing
+@kbd{U} in the group buffer (@pxref{Group Maintenance}).  This variable
+is @code{t} by default.  If you set this variable to @code{always}, then
+Gnus will query the backends for new groups even when you do the @kbd{g}
+command (@pxref{Scanning New Messages}).
+@menu
+* Checking New Groups::      Determining what groups are new.
+* Subscription Methods::     What Gnus should do with new groups.
+* Filtering New Groups::     Making Gnus ignore certain new groups.
+@end menu
+@node Checking New Groups
+@subsection Checking New Groups
+Gnus normally determines whether a group is new or not by comparing the
+list of groups from the active file(s) with the lists of subscribed and
+dead groups.  This isn't a particularly fast method.  If
+@code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
+server for new groups since the last time.  This is both faster and
+cheaper.  This also means that you can get rid of the list of killed
+groups altogether, so you may set @code{gnus-save-killed-list} to
+@code{nil}, which will save time both at startup, at exit, and all over.
+Saves disk space, too.  Why isn't this the default, then?
+Unfortunately, not all servers support this command.
+I bet I know what you're thinking now: How do I find out whether my
+server supports @code{ask-server}?  No?  Good, because I don't have a
+fail-safe answer.  I would suggest just setting this variable to
+@code{ask-server} and see whether any new groups appear within the next
+few days.  If any do, then it works.  If none do, then it doesn't
+work.  I could write a function to make Gnus guess whether the server
+supports @code{ask-server}, but it would just be a guess.  So I won't.
+You could @code{telnet} to the server and say @code{HELP} and see
+whether it lists @samp{NEWGROUPS} among the commands it understands.  If
+it does, then it might work.  (But there are servers that lists
+@samp{NEWGROUPS} without supporting the function properly.)
+This variable can also be a list of select methods.  If so, Gnus will
+issue an @code{ask-server} command to each of the select methods, and
+subscribe them (or not) using the normal methods.  This might be handy
+if you are monitoring a few servers for new groups.  A side effect is
+that startup will take much longer, so you can meditate while waiting.
+Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
+@node Subscription Methods
+@subsection Subscription Methods
 @vindex gnus-subscribe-newsgroup-method
 What Gnus does when it encounters a new group is determined by the
 @code{gnus-subscribe-newsgroup-method} variable.
 @table @code
 @item gnus-subscribe-zombies
 @vindex gnus-subscribe-zombies
-Make all new groups zombies.  You can browse the zombies later (with
+Make all new groups zombies.  This is the default.  You can browse the
-@kbd{A z}) and either kill them all off properly, or subscribe to them.
+zombies later (with @kbd{A z}) and either kill them all off properly
-This is the default.
+(with @kbd{S z}), or subscribe to them (with @kbd{u}).
 @item gnus-subscribe-randomly
 @vindex gnus-subscribe-randomly
 Subscribe all new groups randomly.
 @item gnus-subscribe-alphabetically
 @vindex gnus-subscribe-alphabetically
 Subscribe all new groups alphabetically.
 @item gnus-subscribe-hierarchically
 @vindex gnus-subscribe-hierarchically
 Subscribe all new groups hierarchically.  The difference between this
 function and @code{gnus-subscribe-alphabetically} is slight.
-@code{gnus-subscribe-alphabetically} will subscribe new groups in a
+@code{gnus-subscribe-alphabetically} will subscribe new groups in a strictly
-strictly alphabetical fashion, while this function will enter groups
+alphabetical fashion, while this function will enter groups into it's
-into it's hierarchy.  So if you want to have the @samp{rec} hierarchy
+hierarchy.  So if you want to have the @samp{rec} hierarchy before the
-before the @samp{comp} hierarchy, this function will not mess that
+@samp{comp} hierarchy, this function will not mess that configuration
-configuration up.  Or something like that.
+up.  Or something like that.
 @item gnus-subscribe-interactively
 @vindex gnus-subscribe-interactively
 Subscribe new groups interactively.  This means that Gnus will ask
 you about @strong{all} new groups.
 hierarchy or not.
 One common mistake is to set the variable a few paragraphs above to
 @code{gnus-subscribe-hierarchical-interactive}.  This is an error.  This
 will not work.  This is ga-ga.  So don't do it.
+@node Filtering New Groups
+@subsection Filtering New Groups
 A nice and portable way to control which new newsgroups should be
 subscribed (or ignored) is to put an @dfn{options} line at the start of
 the @file{.newsrc} file.  Here's an example:
 more for user fiddling.  By default this variable makes all new groups
 that come from mail backends (@code{nnml}, @code{nnbabyl},
 @code{nnfolder}, @code{nnmbox}, and @code{nnmh}) subscribed.  If you
 don't like that, just set this variable to @code{nil}.
-@vindex gnus-check-new-newsgroups
+New groups that match this regexp are subscribed using
-If you are satisfied that you really never want to see any new groups,
+@code{gnus-subscribe-options-newsgroup-method}.
-you could set @code{gnus-check-new-newsgroups} to @code{nil}.  This will
-also save you some time at startup.  Even if this variable is
-@code{nil}, you can always subscribe to the new groups just by pressing
+@node Changing Servers
-@kbd{U} in the group buffer (@pxref{Group Maintenance}).  This variable
+@section Changing Servers
-is @code{t} by default.
+@cindex changing servers
-Gnus normally determines whether a group is new or not by comparing the
+Sometimes it is necessary to move from one @sc{nntp} server to another.
-list of groups from the active file(s) with the lists of subscribed and
+This happens very rarely, but perhaps you change jobs, or one server is
-dead groups.  This isn't a particularly fast method.  If
+very flaky and you want to use another.
-@code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will ask the
-server for new groups since the last time.  This is both faster &
+Changing the server is pretty easy, right?  You just change
-cheaper.  This also means that you can get rid of the list of killed
+@code{gnus-select-method} to point to the new server?
-groups altogether, so you may set @code{gnus-save-killed-list} to
-@code{nil}, which will save time both at startup, at exit, and all over.
+@emph{Wrong!}
-Saves disk space, too.  Why isn't this the default, then?
-Unfortunately, not all servers support this command.
+Article numbers are not (in any way) kept synchronized between different
+@sc{nntp} servers, and the only way Gnus keeps track of what articles
-I bet I know what you're thinking now: How do I find out whether my
+you have read is by keeping track of article numbers.  So when you
-server supports @code{ask-server}?  No?  Good, because I don't have a
+change @code{gnus-select-method}, your @file{.newsrc} file becomes
-fail-safe answer.  I would suggest just setting this variable to
+worthless.
-@code{ask-server} and see whether any new groups appear within the next
-few days.  If any do, then it works.  If any don't, then it doesn't
+Gnus provides a few functions to attempt to translate a @file{.newsrc}
-work.  I could write a function to make Gnus guess whether the server
+file from one server to another.  They all have one thing in
-supports @code{ask-server}, but it would just be a guess.  So I won't.
+common---they take a looong time to run.  You don't want to use these
-You could @code{telnet} to the server and say @code{HELP} and see
+functions more than absolutely necessary.
-whether it lists @samp{NEWGROUPS} among the commands it understands.  If
-it does, then it might work.  (But there are servers that lists
+@kindex M-x gnus-change-server
-@samp{NEWGROUPS} without supporting the function properly.)
+@findex gnus-change-server
+If you have access to both servers, Gnus can request the headers for all
-This variable can also be a list of select methods.  If so, Gnus will
+the articles you have read and compare @code{Message-ID}s and map the
-issue an @code{ask-server} command to each of the select methods, and
+article numbers of the read articles and article marks.  The @kbd{M-x
-subscribe them (or not) using the normal methods.  This might be handy
+gnus-change-server} command will do this for all your native groups.  It
-if you are monitoring a few servers for new groups.  A side effect is
+will prompt for the method you want to move to.
-that startup will take much longer, so you can meditate while waiting.
-Use the mantra ``dingnusdingnusdingnus'' to achieve permanent bliss.
+@kindex M-x gnus-group-move-group-to-server
+@findex gnus-group-move-group-to-server
+You can also move individual groups with the @kbd{M-x
+gnus-group-move-group-to-server} command.  This is useful if you want to
+move a (foreign) group from one server to another.
+@kindex M-x gnus-group-clear-data-on-native-groups
+@findex gnus-group-clear-data-on-native-groups
+If you don't have access to both the old and new server, all your marks
+and read ranges have become worthless.  You can use the @kbd{M-x
+gnus-group-clear-data-on-native-groups} command to clear out all data
+that you have on your native groups.  Use with caution.
 @node Startup Files
 @section Startup Files
 @cindex startup files
 @cindex .newsrc
+@cindex .newsrc.el
+@cindex .newsrc.eld
 Now, you all know about the @file{.newsrc} file.  All subscription
 information is traditionally stored in this file.
 Things got a bit more complicated with @sc{gnus}.  In addition to
 @vindex gnus-save-killed-list
 If @code{gnus-save-killed-list} (default @code{t}) is @code{nil}, Gnus
 will not save the list of killed groups to the startup file.  This will
 save both time (when starting and quitting) and space (on disk).  It
-will also means that Gnus has no record of what groups are new or old,
+will also mean that Gnus has no record of what groups are new or old,
 so the automatic new groups subscription methods become meaningless.
 You should always set @code{gnus-check-new-newsgroups} to @code{nil} or
 @code{ask-server} if you set this variable to @code{nil} (@pxref{New
-Groups}).
+Groups}).  This variable can also be a regular expression.  If that's
+the case, remove all groups that do not match this regexp before
+saving.  This can be useful in certain obscure situations that involve
+several servers where not all servers support @code{ask-server}.
 @vindex gnus-startup-file
 The @code{gnus-startup-file} variable says where the startup files are.
 The default value is @file{~/.newsrc}, with the Gnus (El Dingo) startup
 file being whatever that one is with a @samp{.eld} appended.
 @code{gnus-save-newsrc-hook} is called before saving any of the newsrc
 files, while @code{gnus-save-quick-newsrc-hook} is called just before
 saving the @file{.newsrc.eld} file, and
 @code{gnus-save-standard-newsrc-hook} is called just before saving the
 @file{.newsrc} file.  The latter two are commonly used to turn version
-control on or off.  Version control is off by default when saving the
+control on or off.  Version control is on by default when saving the
-startup files.
+startup files.  If you want to turn backup creation off, say something like:
+@lisp
+(defun turn-off-backup ()
+(set (make-local-variable 'backup-inhibited) t))
+(add-hook 'gnus-save-quick-newsrc-hook 'turn-off-backup)
+(add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
+@end lisp
 @vindex gnus-init-file
-When Gnus starts, it will read the @code{gnus-init-file} file, which is
+When Gnus starts, it will read the @code{gnus-site-init-file}
-@file{~/.gnus.el} by default.  This is a normal Emacs Lisp file and can
+(@file{.../site-lisp/gnus.el} by default) and @code{gnus-init-file}
-be used to avoid cluttering your @file{.emacs} file with Gnus stuff.
+(@file{~/.gnus.el} by default) files.  These are normal Emacs Lisp files
+and can be used to avoid cluttering your @file{.emacs} and
+@file{site-init} files with Gnus stuff.
 @node Auto Save
 @section Auto Save
 @cindex dribble file
 performance, but if the server does not support the aforementioned
 @code{LIST ACTIVE group} command, this isn't very nice to the server.
 In any case, if you use @code{some} or @code{nil}, you should definitely
 kill all groups that you aren't interested in to speed things up.
+Note that this variable also affects active file retrieval from
+secondary select methods.
 @node Startup Variables
 @section Startup Variables
 in a while from the group buffer instead (@pxref{Group Maintenance}).
 @item gnus-inhibit-startup-message
 @vindex gnus-inhibit-startup-message
 If non-@code{nil}, the startup message won't be displayed.  That way,
-your boss might not notice that you are reading news instead of doing
+your boss might not notice as easily that you are reading news instead
-your job as easily.
+of doing your job.  Note that this variable is used before
+@file{.gnus.el} is loaded, so it should be set in @code{.emacs} instead.
 @item gnus-no-groups-message
 @vindex gnus-no-groups-message
 Message displayed by Gnus when no groups are available.
+@item gnus-play-startup-jingle
+@vindex gnus-play-startup-jingle
+If non-@code{nil}, play the Gnus jingle at startup.
+@item gnus-startup-jingle
+@vindex gnus-startup-jingle
+Jingle to be played if the above variable is non-@code{nil}.  The
+default is @samp{Tuxedomoon.Jingle4.au}.
 @end table
 @node The Group Buffer
 @chapter The Group Buffer
 @menu
 * Group Buffer Format::    Information listed and how you can change it.
 * Group Maneuvering::      Commands for moving in the group buffer.
 * Selecting a Group::      Actually reading news.
+* Group Data::             Changing the info for a group.
 * Subscription Commands::  Unsubscribing, killing, subscribing.
 * Group Levels::           Levels? What are those, then?
 * Group Score::            A mechanism for finding out what groups you like.
 * Marking Groups::         You can mark groups for later processing.
 * Foreign Groups::         Creating and editing groups.
 @end menu
 @node Group Buffer Format
 @section Group Buffer Format
-@cindex group buffer format
 @menu
 * Group Line Specification::       Deciding how the group buffer is to look.
 * Group Modeline Specification::   The group buffer modeline.
 * Group Highlighting::             Having nice colors in the group buffer.
 @end menu
 @node Group Line Specification
 @subsection Group Line Specification
+@cindex group buffer format
 The default format of the group buffer is nice and dull, but you can
 make it as exciting and ugly as you feel like.
 Here's a couple of example group lines:
 @code{gnus-group-line-format} variable.  This variable works along the
 lines of a @code{format} specification, which is pretty much the same as
 a @code{printf} specifications, for those of you who use (feh!) C.
 @xref{Formatting Variables}.
-The default value that produced those lines above is
+@samp{%M%S%5y: %(%g%)\n} is the value that produced those lines above.
-@samp{%M%S%5y: %(%g%)\n}.
 There should always be a colon on the line; the cursor always moves to
 the colon after performing an operation.  Nothing else is required---not
 even the group name.  All displayed text is just window dressing, and is
 never examined by Gnus.  Gnus stores all real information it needs using
 Here's a list of all available format characters:
 @table @samp
 @item M
-Only marked articles.
+An asterisk if the group only has marked articles.
 @item S
 Whether the group is subscribed.
 @item L
 @item R
 Number of read articles.
 @item t
-Total number of articles.
+Estimated total number of articles.  (This is really @var{max-number}
+minus @var{min-number} plus 1.)
 @item y
 Number of unread, unticked, non-dormant articles.
 @item i
 @item c
 @vindex gnus-group-uncollapsed-levels
 Short (collapsed) group name.  The @code{gnus-group-uncollapsed-levels}
 variable says how many levels to leave at the end of the group name.
-The default is @code{1}.
+The default is 1---this will mean that group names like
+@samp{gnu.emacs.gnus} will be shortened to @samp{g.emacs.gnus}.
+@item m
+@vindex gnus-new-mail-mark
+@cindex %
+@samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
+the group lately.
+@item d
+A string that says when you last read the group (@pxref{Group
+Timestamp}).
 @item u
 User defined specifier.  The next character in the format string should
 be a letter.  @sc{gnus} will call the function
 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
-following @samp{%u}.  The function will be passed the current headers as
+following @samp{%u}.  The function will be passed a single dummy
-argument.  The function should return a string, which will be inserted
+paratere as argument.  The function should return a string, which will
-into the buffer just like information from any other specifier.
+be inserted into the buffer just like information from any other
+specifier.
 @end table
 @cindex *
 All the ``number-of'' specs will be filled with an asterisk (@samp{*})
 if no info is available---for instance, if it is a non-activated foreign
-group, or a bogus (or semi-bogus) native group.
+group, or a bogus native group.
 @node Group Modeline Specification
 @subsection Group Modeline Specification
+@cindex group modeline
 @vindex gnus-group-mode-line-format
 The mode line can be changed by setting
-(@code{gnus-group-mode-line-format}).  It doesn't understand that many
+@code{gnus-group-mode-line-format} (@pxref{Formatting Variables}).  It
-format specifiers:
+doesn't understand that many format specifiers:
 @table @samp
 @item S
 The native news server.
 @item M
 @end table
 @node Group Highlighting
 @subsection Group Highlighting
+@cindex highlighting
+@cindex group highlighting
 @vindex gnus-group-highlight
 Highlighting in the group buffer is controlled by the
 @code{gnus-group-highlight} variable.  This is an alist with elements
 that look like @var{(form . face)}.  If @var{form} evaluates to
 Here's an example value for this variable that might look nice if the
 background is dark:
 @lisp
 (setq gnus-group-highlight
 `(((> unread 200) .
 ,(custom-face-lookup "Red" nil nil t nil nil))
 ((and (< level 3) (zerop unread)) .
 ,(custom-face-lookup "SeaGreen" nil nil t nil nil))
 ((< level 3) .
 ,(custom-face-lookup "SpringGreen" nil nil t nil nil))
 ((zerop unread) .
 ,(custom-face-lookup "SteelBlue" nil nil t nil nil))
 (t .
-,(custom-face-lookup "SkyBlue" nil nil t nil nil))
+,(custom-face-lookup "SkyBlue" nil nil t nil nil))))
-))
 @end lisp
 Variables that are dynamically bound when the forms are evaluated
 include:
 The level of the group.
 @item score
 The score of the group.
 @item ticked
 The number of ticked articles in the group.
+@item total
+The total number of articles in the group.  Or rather, MAX-NUMBER minus
+MIN-NUMBER.
 @item topic
 When using the topic minor mode, this variable is bound to the current
 topic being inserted.
 @end table
 @findex gnus-group-next-unread-group
 Go to the next group that has unread articles
 (@code{gnus-group-next-unread-group}).
 @item p
 @itemx DEL
 @kindex DEL (Group)
 @kindex p (Group)
 @findex gnus-group-prev-unread-group
-Go to the previous group group that has unread articles
+Go to the previous group that has unread articles
 (@code{gnus-group-prev-unread-group}).
 @item N
 @kindex N (Group)
 @findex gnus-group-next-group
 Go to the previous group (@code{gnus-group-prev-group}).
 @item M-p
 @kindex M-p (Group)
 @findex gnus-group-next-unread-group-same-level
-Go to the next unread group on the same level (or lower)
+Go to the next unread group on the same (or lower) level
 (@code{gnus-group-next-unread-group-same-level}).
 @item M-n
 @kindex M-n (Group)
 @findex gnus-group-prev-unread-group-same-level
-Go to the previous unread group on the same level (or lower)
+Go to the previous unread group on the same (or lower) level
 (@code{gnus-group-prev-unread-group-same-level}).
 @end table
 Three commands for jumping to groups:
 @findex gnus-group-read-group
 Select the current group, switch to the summary buffer and display the
 first unread article (@code{gnus-group-read-group}).  If there are no
 unread articles in the group, or if you give a non-numerical prefix to
 this command, Gnus will offer to fetch all the old articles in this
-group from the server.  If you give a numerical prefix @var{N}, Gnus
+group from the server.  If you give a numerical prefix @var{N}, @var{N}
-will fetch @var{N} number of articles.  If @var{N} is positive, fetch
+determines the number of articles Gnus will fetch.  If @var{N} is
-the @var{N} newest articles, if @var{N} is negative, fetch the
+positive, Gnus fetches the @var{N} newest articles, if @var{N} is
-@var{abs(N)} oldest articles.
+negative, Gnus fetches the @var{abs(N)} oldest articles.
 @item RET
 @kindex RET (Group)
 @findex gnus-group-select-group
 Select the current group and switch to the summary buffer
 @item M-RET
 @kindex M-RET (Group)
 @findex gnus-group-quick-select-group
 This does the same as the command above, but tries to do it with the
-minimum amount off fuzz (@code{gnus-group-quick-select-group}).  No
+minimum amount of fuzz (@code{gnus-group-quick-select-group}).  No
 scoring/killing will be performed, there will be no highlights and no
 expunging.  This might be useful if you're in a real hurry and have to
-enter some humongous group.
+enter some humongous group.  If you give a 0 prefix to this command
+(i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer.
+This might be useful if you want to toggle threading before entering the
+group.
 @item M-SPACE
-@kindex M-RET (Group)
+@kindex M-SPACE (Group)
 @findex gnus-group-visible-select-group
-This is yet one more command that does the same as the one above, but
+This is yet one more command that does the same as the @kbd{RET}
-this one does it without expunging and hiding dormants
+command, but this one does it without expunging and hiding dormants
 (@code{gnus-group-visible-select-group}).
-@item c
+@item M-C-RET
-@kindex c (Group)
+@kindex M-C-RET (Group)
-@findex gnus-group-catchup-current
+@findex gnus-group-select-group-ephemerally
-@vindex gnus-group-catchup-group-hook
+Finally, this command selects the current group ephemerally without
-Mark all unticked articles in this group as read
+doing any processing of its contents
-(@code{gnus-group-catchup-current}).
+(@code{gnus-group-select-group-ephemerally}).  Even threading has been
-@code{gnus-group-catchup-group-hook} is when catching up a group from
+turned off.  Everything you do in the group after selecting it in this
-the group buffer.
+manner will have no permanent effects.
-@item C
-@kindex C (Group)
-@findex gnus-group-catchup-current-all
-Mark all articles in this group, even the ticked ones, as read
-(@code{gnus-group-catchup-current-all}).
 @end table
 @vindex gnus-large-newsgroup
 The @code{gnus-large-newsgroup} variable says what Gnus should consider
 to be a big group.  This is 200 by default.  If the group has more
-unread articles than this, Gnus will query the user before entering the
+(unread and/or ticked) articles than this, Gnus will query the user
-group.  The user can then specify how many articles should be fetched
+before entering the group.  The user can then specify how many articles
-from the server.  If the user specifies a negative number (@code{-n}),
+should be fetched from the server.  If the user specifies a negative
-the @code{n} oldest articles will be fetched.  If it is positive, the
+number (@code{-n}), the @code{n} oldest articles will be fetched.  If it
-@code{n} articles that have arrived most recently will be fetched.
+is positive, the @code{n} articles that have arrived most recently will
+be fetched.
 @vindex gnus-select-group-hook
 @vindex gnus-auto-select-first
 @code{gnus-auto-select-first} control whether any articles are selected
-automatically when entering a group.
+automatically when entering a group with the @kbd{SPACE} command.
 @table @code
 @item nil
 Don't select any articles when entering the group.  Just display the
 selected.
 @node Subscription Commands
 @section Subscription Commands
-@cindex subscribing
+@cindex subscription
 @table @kbd
 @item S t
 @itemx u
 @item S C-k
 @kindex S C-k (Group)
 @findex gnus-group-kill-level
 Kill all groups on a certain level (@code{gnus-group-kill-level}).
 These groups can't be yanked back after killing, so this command should
-be used with some caution.  The only thing where this command comes in
+be used with some caution.  The only time where this command comes in
 really handy is when you have a @file{.newsrc} with lots of unsubscribed
-groups that you want to get rid off.  @kbd{S C-k} on level @code{7} will
+groups that you want to get rid off.  @kbd{S C-k} on level 7 will
 kill off all unsubscribed groups that do not have message numbers in the
 @file{.newsrc} file.
 @end table
 Also @pxref{Group Levels}.
+@node Group Data
+@section Group Data
+@table @kbd
+@item c
+@kindex c (Group)
+@findex gnus-group-catchup-current
+@vindex gnus-group-catchup-group-hook
+Mark all unticked articles in this group as read
+(@code{gnus-group-catchup-current}).
+@code{gnus-group-catchup-group-hook} is called when catching up a group from
+the group buffer.
+@item C
+@kindex C (Group)
+@findex gnus-group-catchup-current-all
+Mark all articles in this group, even the ticked ones, as read
+(@code{gnus-group-catchup-current-all}).
+@item M-c
+@kindex M-c (Group)
+@findex gnus-group-clear-data
+Clear the data from the current group---nix out marks and the list of
+read articles (@code{gnus-group-clear-data}).
+@item M-x gnus-group-clear-data-on-native-groups
+@kindex M-x gnus-group-clear-data-on-native-groups
+@findex gnus-group-clear-data-on-native-groups
+If you have switched from one @sc{nntp} server to another, all your marks
+and read ranges have become worthless.  You can use this command to
+clear out all data that you have on your native groups.  Use with
+caution.
+@end table
 @node Group Levels
 @section Group Levels
 @cindex group level
+@cindex level
 All groups have a level of @dfn{subscribedness}.  For instance, if a
 group is on level 2, it is more subscribed than a group on level 5.  You
 can ask Gnus to just list groups on a given level or lower
 (@pxref{Listing Groups}), or to just check for new articles in groups on
 articles you have read, etc, stored.  This distinction between dead and
 living groups isn't done because it is nice or clever, it is done purely
 for reasons of efficiency.
 It is recommended that you keep all your mail groups (if any) on quite
-low levels (eg. 1 or 2).
+low levels (e.g. 1 or 2).
 If you want to play with the level variables, you should show some care.
 Set them once, and don't touch them ever again.  Better yet, don't touch
 them at all unless you know exactly what you're doing.
 @vindex gnus-activate-level
 Gnus will normally just activate groups that are on level
 @code{gnus-activate-level} or less.  If you don't want to activate
 unsubscribed groups, for instance, you might set this variable to
-@code{5}.
+5.  The default is 6.
 @node Group Score
 @section Group Score
 @cindex group score
 group.  You can then sort the group buffer based on this score.
 Alternatively, you can sort on score and then level.  (Taken together,
 the level and the score is called the @dfn{rank} of the group.  A group
 that is on level 4 and has a score of 1 has a higher rank than a group
 on level 5 that has a score of 300.  (The level is the most significant
-part and the score is the least significant part.)
+part and the score is the least significant part.))
 @findex gnus-summary-bubble-group
 If you want groups you read often to get higher scores than groups you
 read seldom you can add the @code{gnus-summary-bubble-group} function to
 the @code{gnus-summary-exit-hook} hook.  This will result (after
 the command to be executed.
 @node Foreign Groups
 @section Foreign Groups
+@cindex foreign groups
-Here are some group mode commands for making and editing general foreign
+Below are some group mode commands for making and editing general foreign
 groups, as well as commands to ease the creation of a few
-special-purpose groups:
+special-purpose groups.  All these commands insert the newly created
+groups under point---@code{gnus-subscribe-newsgroup-method} is not
+consulted.
 @table @kbd
 @item G m
 @kindex G m (Group)
 @findex gnus-group-make-group
+@cindex making groups
 Make a new group (@code{gnus-group-make-group}).  Gnus will prompt you
 for a name, a method and possibly an @dfn{address}.  For an easier way
 to subscribe to @sc{nntp} groups, @pxref{Browse Foreign Server}.
 @item G r
 @kindex G r (Group)
 @findex gnus-group-rename-group
+@cindex renaming groups
 Rename the current group to something else
 (@code{gnus-group-rename-group}).  This is legal only on some
 groups---mail groups mostly.  This command might very well be quite slow
 on some backends.
+@item G c
+@kindex G c (Group)
+@cindex customizing
+@findex gnus-group-customize
+Customize the group parameters (@code{gnus-group-customize}).
 @item G e
 @kindex G e (Group)
 @findex gnus-group-edit-group-method
+@cindex renaming groups
 Enter a buffer where you can edit the select method of the current
 group (@code{gnus-group-edit-group-method}).
 @item G p
 @kindex G p (Group)
 (@code{gnus-group-edit-group}).
 @item G d
 @kindex G d (Group)
 @findex gnus-group-make-directory-group
-Make a directory group.  You will be prompted for a directory name
+@cindex nndir
-(@code{gnus-group-make-directory-group}).
+Make a directory group (@pxref{Directory Groups}).  You will be prompted
+for a directory name (@code{gnus-group-make-directory-group}).
 @item G h
 @kindex G h (Group)
+@cindex help group
 @findex gnus-group-make-help-group
 Make the Gnus help group (@code{gnus-group-make-help-group}).
 @item G a
 @kindex G a (Group)
+@cindex (ding) archive
+@cindex archive group
 @findex gnus-group-make-archive-group
 @vindex gnus-group-archive-directory
 @vindex gnus-group-recent-archive-directory
 Make a Gnus archive group (@code{gnus-group-make-archive-group}).  By
 default a group pointing to the most recent articles will be created
 group will be created from @code{gnus-group-archive-directory}.
 @item G k
 @kindex G k (Group)
 @findex gnus-group-make-kiboze-group
+@cindex nnkiboze
 Make a kiboze group.  You will be prompted for a name, for a regexp to
 match groups to be ``included'' in the kiboze group, and a series of
 strings to match on headers (@code{gnus-group-make-kiboze-group}).
-@xref{Kibozed Groups}
+@xref{Kibozed Groups}.
 @item G D
 @kindex G D (Group)
 @findex gnus-group-enter-directory
+@cindex nneething
 Read an arbitrary directory as if with were a newsgroup with the
 @code{nneething} backend (@code{gnus-group-enter-directory}).
+@xref{Anything Groups}.
 @item G f
 @kindex G f (Group)
 @findex gnus-group-make-doc-group
 @cindex ClariNet Briefs
+@cindex nndoc
 Make a group based on some file or other
 (@code{gnus-group-make-doc-group}).  If you give a prefix to this
 command, you will be prompted for a file name and a file type.
 Currently supported types are @code{babyl}, @code{mbox}, @code{digest},
 @code{mmdf}, @code{news}, @code{rnews}, @code{clari-briefs}, and
 @code{forward}.  If you run this command without a prefix, Gnus will
-guess at the file type.
+guess at the file type.  @xref{Document Groups}.
+@item G w
+@kindex G w (Group)
+@findex gnus-group-make-web-group
+@cindex DejaNews
+@cindex Alta Vista
+@cindex InReference
+@cindex nnweb
+Make an ephemeral group based on a web search
+(@code{gnus-group-make-web-group}).  If you give a prefix to this
+command, make a solid group instead.  You will be prompted for the
+search engine type and the search string.  Legal search engine types
+include @code{dejanews}, @code{altavista} and @code{reference}.
+@xref{Web Searches}.
 @item G DEL
 @kindex G DEL (Group)
 @findex gnus-group-delete-group
 This function will delete the current group
 @item G V
 @kindex G V (Group)
 @findex gnus-group-make-empty-virtual
 Make a new, fresh, empty @code{nnvirtual} group
-(@code{gnus-group-make-empty-virtual}).
+(@code{gnus-group-make-empty-virtual}).  @xref{Virtual Groups}.
 @item G v
 @kindex G v (Group)
 @findex gnus-group-add-to-virtual
 Add the current group to an @code{nnvirtual} group
 @xref{Select Methods} for more information on the various select
 methods.
 @vindex gnus-activate-foreign-newsgroups
-If the @code{gnus-activate-foreign-newsgroups} is a positive number,
+If @code{gnus-activate-foreign-newsgroups} is a positive number,
 Gnus will check all foreign groups with this level or lower at startup.
 This might take quite a while, especially if you subscribe to lots of
 groups from different @sc{nntp} servers.
 @node Group Parameters
 @section Group Parameters
 @cindex group parameters
-Gnus stores all information on a group in a list that is usually known
-as the @dfn{group info}.  This list has from three to six elements.
-Here's an example info.
-@lisp
-("nnml:mail.ding" 3 ((1 . 232) 244 (256 . 270)) ((tick 246 249))
-(nnml "private") ((to-address . "ding@@ifi.uio.no")))
-@end lisp
-The first element is the @dfn{group name}, as Gnus knows the group,
-anyway.  The second element is the @dfn{subscription level}, which
-normally is a small integer.  The third element is a list of ranges of
-read articles.  The fourth element is a list of lists of article marks
-of various kinds.  The fifth element is the select method (or virtual
-server, if you like).  The sixth element is a list of @dfn{group
-parameters}, which is what this section is about.
-Any of the last three elements may be missing if they are not required.
-In fact, the vast majority of groups will normally only have the first
-three elements, which saves quite a lot of cons cells.
 The group parameters store information local to a particular group:
 @table @code
 @item to-address
 @code{Reply-To} headers that point back to the listserv itself.  This is
 broken behavior.  So there!
 @item to-group
 @cindex to-group
-If the group parameter list contains an element like @code{(to-group
+Elements like @code{(to-group . "some.group.name")} means that all
-. "some.group.name")}, all posts will be sent to that group.
+posts in that group will be sent to @code{some.group.name}.
+@item newsgroup
+@cindex newsgroup
+If this symbol is present in the group parameter list, Gnus will treat
+all responses as if they were responses to news articles.  This can be
+useful if you have a mail group that's really a mirror of a news group.
+@item gcc-self
+@cindex gcc-self
+If this symbol is present in the group parameter list and set to
+@code{t}, new composed messages will be @code{Gcc}'d to the current
+group. If it is present and set to @code{none}, no @code{Gcc:} header
+will be generated, if it is present and a string, this string will be
+inserted literally as a @code{gcc} header (this symbol takes precedence over
+any default @code{Gcc} rules as described later).
 @item auto-expire
 @cindex auto-expire
-If this symbol is present in the group parameter list, all articles that
+If the group parameter has an element that looks like @code{(auto-expire
-are read will be marked as expirable.  For an alternative approach,
+. t)}, , all articles that are read will be marked as expirable.  For an
-@pxref{Expiring Mail}.
+alternative approach, @pxref{Expiring Mail}.
 @item total-expire
 @cindex total-expire
-If this symbol is present, all read articles will be put through the
+If the group parameter has an element that looks like
+@code{(total-expire . t)}, all read articles will be put through the
 expiry process, even if they are not marked as expirable.  Use with
 caution.
 @item expiry-wait
 @cindex expiry-wait
 @vindex nnmail-expiry-wait-function
 If the group parameter has an element that looks like @code{(expiry-wait
 @code{nnmail-expiry-wait-function} when expiring expirable messages.
 The value can either be a number of days (not necessarily an integer) or
 the symbols @code{never} or @code{immediate}.
 @item score-file
+@cindex score file group parameter
 Elements that look like @code{(score-file . "file")} will make
-@samp{file} into the current score file for the group in question.  This
+@file{file} into the current score file for the group in question.  This
 means that all score commands you issue will end up in that file.
+@item adapt-file
+@cindex adapt file group parameter
+Elements that look like @code{(adapt-file . "file")} will make
+@file{file} into the current adaptive file for the group in question.
+All adaptive score entries will be put into this file.
 @item admin-address
 When unsubscribing to a mailing list you should never send the
 unsubscription notice to the mailing list itself.  Instead, you'd send
 messages to the administrative address.  This parameter allows you to
 put the admin address somewhere convenient.
+@item display
+Elements that look like @code{(display . MODE)} says which articles to
+display on entering the group.  Legal values are:
+@table @code
+@item all
+Display all articles, both read and unread.
+@item default
+Display the default visible articles, which normally includes unread and
+ticked articles.
+@end table
 @item comment
-This parameter allows you to enter a arbitrary comment on the group.
+Elements that look like @code{(comment . "This is a comment")}
+are arbitrary comments on the group.  They are currently ignored by
+Gnus, but provide a place for you to store information on particular
+groups.
 @item @var{(variable form)}
 You can use the group parameters to set variables local to the group you
-are entering.  Say you want to turn threading off in
+are entering.  If you want to turn threading off in @samp{news.answers},
-@samp{news.answers}.  You'd then put @code{(gnus-show-threads nil)} in
+you could put @code{(gnus-show-threads nil)} in the group parameters of
-the group parameters of that group.  @code{gnus-show-threads} will be
+that group.  @code{gnus-show-threads} will be made into a local variable
-made into a local variable in the summary buffer you enter, and the form
+in the summary buffer you enter, and the form @code{nil} will be
-@code{nil} will be @code{eval}ed there.
+@code{eval}ed there.
 This can also be used as a group-specific hook function, if you'd like.
-If you want to hear a beep when you enter the group
+If you want to hear a beep when you enter a group, you could put
-@samp{alt.binaries.pictures.furniture}, you could put something like
+something like @code{(dummy-variable (ding))} in the parameters of that
-@code{(dummy-variable (ding))} in the parameters of that group.
+group.  @code{dummy-variable} will be set to the result of the
-@code{dummy-variable} will be set to the result of the @code{(ding)}
+@code{(ding)} form, but who cares?
-form, but who cares?
+@end table
-@end table
+Use the @kbd{G p} command to edit group parameters of a group.
-If you want to change the group info you can use the @kbd{G E} command
-to enter a buffer where you can edit it.
+Also @pxref{Topic Parameters}.
-You usually don't want to edit the entire group info, so you'd be better
-off using the @kbd{G p} command to just edit the group parameters.
 @node Listing Groups
 @section Listing Groups
 @cindex group listing
 @kindex l (Group)
 @findex gnus-group-list-groups
 List all groups that have unread articles
 (@code{gnus-group-list-groups}).  If the numeric prefix is used, this
 command will list only groups of level ARG and lower.  By default, it
-only lists groups of level five or lower (i.e., just subscribed groups).
+only lists groups of level five (i. e.,
+@code{gnus-group-default-list-level}) or lower (i.e., just subscribed
+groups).
 @item L
 @itemx A u
 @kindex A u (Group)
 @kindex L (Group)
 @kindex A A (Group)
 @findex gnus-group-list-active
 List absolutely all groups that are in the active file(s) of the
 server(s) you are connected to (@code{gnus-group-list-active}).  This
 might very well take quite a while.  It might actually be a better idea
-to do a @kbd{A m} to list all matching, and just give @samp{.} as the
+to do a @kbd{A M} to list all matching, and just give @samp{.} as the
-thing to match on.
+thing to match on.  Also note that this command may list group that
+don't exist (yet)---these will be listed as if they are killed groups.
+Take the output with some grains of salt.
 @item A a
 @kindex A a (Group)
 @findex gnus-group-apropos
 List all groups that have names that match a regexp
 @item gnus-group-sort-by-alphabet
 @findex gnus-group-sort-by-alphabet
 Sort the group names alphabetically.  This is the default.
+@item gnus-group-sort-by-real-name
+@findex gnus-group-sort-by-real-name
+Sort the group alphabetically on the real (unprefixed) group names.
 @item gnus-group-sort-by-level
 @findex gnus-group-sort-by-level
 Sort by group level.
 @item gnus-group-sort-by-score
 @findex gnus-group-sort-by-unread
 Sort by number of unread articles.
 @item gnus-group-sort-by-method
 @findex gnus-group-sort-by-method
-Sort by alphabetically on the select method.
+Sort alphabetically on the select method.
 @end table
 @code{gnus-group-sort-function} can also be a list of sorting
 (@code{gnus-group-sort-groups-by-score}).
 @item G S r
 @kindex G S r (Group)
 @findex gnus-group-sort-groups-by-rank
-Sort the group buffer by group level
+Sort the group buffer by group rank
 (@code{gnus-group-sort-groups-by-rank}).
 @item G S m
 @kindex G S m (Group)
 @findex gnus-group-sort-groups-by-method
 (@code{gnus-group-sort-groups-by-method}).
 @end table
 When given a prefix, all these commands will sort in reverse order.
+You can also sort a subset of the groups:
+@table @kbd
+@item G P a
+@kindex G P a (Group)
+@findex gnus-group-sort-selected-groups-by-alphabet
+Sort the process/prefixed groups in the group buffer alphabetically by
+group name (@code{gnus-group-sort-selected-groups-by-alphabet}).
+@item G P u
+@kindex G P u (Group)
+@findex gnus-group-sort-selected-groups-by-unread
+Sort the process/prefixed groups in the group buffer by the number of
+unread articles (@code{gnus-group-sort-selected-groups-by-unread}).
+@item G P l
+@kindex G P l (Group)
+@findex gnus-group-sort-selected-groups-by-level
+Sort the process/prefixed groups in the group buffer by group level
+(@code{gnus-group-sort-selected-groups-by-level}).
+@item G P v
+@kindex G P v (Group)
+@findex gnus-group-sort-selected-groups-by-score
+Sort the process/prefixed groups in the group buffer by group score
+(@code{gnus-group-sort-selected-groups-by-score}).
+@item G P r
+@kindex G P r (Group)
+@findex gnus-group-sort-selected-groups-by-rank
+Sort the process/prefixed groups in the group buffer by group rank
+(@code{gnus-group-sort-selected-groups-by-rank}).
+@item G P m
+@kindex G P m (Group)
+@findex gnus-group-sort-selected-groups-by-method
+Sort the process/prefixed groups in the group buffer alphabetically by
+backend name (@code{gnus-group-sort-selected-groups-by-method}).
+@end table
 @node Group Maintenance
 @section Group Maintenance
 @cindex bogus groups
 (@code{gnus-group-browse-foreign-server}).
 @end table
 @findex gnus-browse-mode
 A new buffer with a list of available groups will appear.  This buffer
-will be use the @code{gnus-browse-mode}.  This buffer looks a bit
+will be use the @code{gnus-browse-mode}.  This buffer looks a bit (well,
-(well, a lot) like a normal group buffer, but with one major difference
+a lot) like a normal group buffer.
-- you can't enter any of the groups.  If you want to read any of the
-news available on that server, you have to subscribe to the groups you
-think may be interesting, and then you have to exit this buffer.  The
-new groups will be added to the group buffer, and then you can read them
-as you would any other group.
-Future versions of Gnus may possibly permit reading groups straight from
-the browse buffer.
 Here's a list of keystrokes available in the browse mode:
 @table @kbd
 @item n
 Quit Gnus (@code{gnus-group-exit}).
 @item Q
 @kindex Q (Group)
 @findex gnus-group-quit
-Quit Gnus without saving any startup files (@code{gnus-group-quit}).
+Quit Gnus without saving the @file{.newsrc} files (@code{gnus-group-quit}).
+The dribble file will be saved, though (@pxref{Auto Save}).
 @end table
 @vindex gnus-exit-gnus-hook
 @vindex gnus-suspend-gnus-hook
 @code{gnus-suspend-gnus-hook} is called when you suspend Gnus and
 trying to customize meta-variables.
 Note:
 @quotation
-Miss Lisa Cannifax, while sitting in English class, feels her feet go
+Miss Lisa Cannifax, while sitting in English class, felt her feet go
 numbly heavy and herself fall into a hazy trance as the boy sitting
 behind her drew repeated lines with his pencil across the back of her
 plastic chair.
 @end quotation
 here, your sex groups over there, and the rest (what, two groups or so?)
 you put in some misc section that you never bother with anyway.  You can
 even group the Emacs sex groups as a sub-topic to either the Emacs
 groups or the sex groups---or both!  Go wild!
+Here's an example:
+@example
+Gnus
+Emacs -- I wuw it!
+3: comp.emacs
+2: alt.religion.emacs
+Naughty Emacs
+452: alt.sex.emacs
+0: comp.talk.emacs.recovery
+Misc
+8: comp.binaries.fractals
+13: comp.sources.unix
+@end example
 @findex gnus-topic-mode
 @kindex t (Group)
 To get this @emph{fab} functionality you simply turn on (ooh!) the
 @code{gnus-topic} minor mode---type @kbd{t} in the group buffer.  (This
 is a toggling command.)
 @end lisp
 @menu
 * Topic Variables::    How to customize the topics the Lisp Way.
 * Topic Commands::     Interactive E-Z commands.
+* Topic Sorting::      Sorting each topic individually.
 * Topic Topology::     A map of the world.
+* Topic Parameters::   Parameters that apply to all groups in a topic.
 @end menu
 @node Topic Variables
 @subsection Topic Variables
 Now, if you select a topic, if will fold/unfold that topic, which is
 really neat, I think.
 @vindex gnus-topic-line-format
 The topic lines themselves are created according to the
-@code{gnus-topic-line-format} variable.  @xref{Formatting Variables}.
+@code{gnus-topic-line-format} variable (@pxref{Formatting Variables}).
-Elements allowed are:
+Legal elements are:
 @table @samp
 @item i
 Indentation.
 @item n
 @end table
 @vindex gnus-topic-indent-level
 Each sub-topic (and the groups in the sub-topics) will be indented with
 @code{gnus-topic-indent-level} times the topic level number of spaces.
-The default is @code{2}.
+The default is 2.
 @vindex gnus-topic-mode-hook
 @code{gnus-topic-mode-hook} is called in topic minor mode buffers.
+@vindex gnus-topic-display-empty-topics
+The @code{gnus-topic-display-empty-topics} says whether to display even
+topics that have no unread articles in them.  The default is @code{t}.
 @node Topic Commands
 @subsection Topic Commands
 @cindex topic commands
 definitions slightly.
 @table @kbd
 @item T n
-@kindex T n (Group)
+@kindex T n (Topic)
 @findex gnus-topic-create-topic
 Prompt for a new topic name and create it
 (@code{gnus-topic-create-topic}).
 @item T m
-@kindex T m (Group)
+@kindex T m (Topic)
 @findex gnus-topic-move-group
 Move the current group to some other topic
-(@code{gnus-topic-move-group}).  This command understands the
+(@code{gnus-topic-move-group}).  This command uses the process/prefix
-process/prefix convention (@pxref{Process/Prefix}).
+convention (@pxref{Process/Prefix}).
 @item T c
-@kindex T c (Group)
+@kindex T c (Topic)
 @findex gnus-topic-copy-group
 Copy the current group to some other topic
-(@code{gnus-topic-copy-group}).  This command understands the
+(@code{gnus-topic-copy-group}).  This command uses the process/prefix
-process/prefix convention (@pxref{Process/Prefix}).
+convention (@pxref{Process/Prefix}).
 @item T D
-@kindex T D (Group)
+@kindex T D (Topic)
 @findex gnus-topic-remove-group
 Remove a group from the current topic (@code{gnus-topic-remove-group}).
-This command understands the process/prefix convention
+This command uses the process/prefix convention
 (@pxref{Process/Prefix}).
 @item T M
-@kindex T M (Group)
+@kindex T M (Topic)
 @findex gnus-topic-move-matching
 Move all groups that match some regular expression to a topic
 (@code{gnus-topic-move-matching}).
 @item T C
-@kindex T C (Group)
+@kindex T C (Topic)
 @findex gnus-topic-copy-matching
 Copy all groups that match some regular expression to a topic
 (@code{gnus-topic-copy-matching}).
 @item T #
-@kindex T # (Group)
+@kindex T # (Topic)
 @findex gnus-topic-mark-topic
 Mark all groups in the current topic with the process mark
 (@code{gnus-topic-mark-topic}).
 @item T M-#
-@kindex T M-# (Group)
+@kindex T M-# (Topic)
 @findex gnus-topic-unmark-topic
 Remove the process mark from all groups in the current topic
 (@code{gnus-topic-unmark-topic}).
 @item RET
-@kindex RET (Group)
+@kindex RET (Topic)
 @findex gnus-topic-select-group
 @itemx SPACE
 Either select a group or fold a topic (@code{gnus-topic-select-group}).
 When you perform this command on a group, you'll enter the group, as
 usual.  When done on a topic line, the topic will be folded (if it was
 visible) or unfolded (if it was folded already).  So it's basically a
 toggling command on topics.  In addition, if you give a numerical
 prefix, group on that level (and lower) will be displayed.
 @item T TAB
-@kindex T TAB (Group)
+@kindex T TAB (Topic)
 @findex gnus-topic-indent
 ``Indent'' the current topic so that it becomes a sub-topic of the
 previous topic (@code{gnus-topic-indent}).  If given a prefix,
 ``un-indent'' the topic instead.
 @item C-k
-@kindex C-k (Group)
+@kindex C-k (Topic)
 @findex gnus-topic-kill-group
-Kill a group or topic (@code{gnus-topic-kill-group}).
+Kill a group or topic (@code{gnus-topic-kill-group}).  All groups in the
+topic will be removed along with the topic.
 @item C-y
-@kindex C-y (Group)
+@kindex C-y (Topic)
 @findex gnus-topic-yank-group
-Yank the previously killed group or topic (@code{gnus-topic-yank-group}).
+Yank the previously killed group or topic
-Note that all topics will be yanked before all groups.
+(@code{gnus-topic-yank-group}).  Note that all topics will be yanked
+before all groups.
 @item T r
-@kindex T r (Group)
+@kindex T r (Topic)
 @findex gnus-topic-rename
 Rename a topic (@code{gnus-topic-rename}).
 @item T DEL
-@kindex T DEL (Group)
+@kindex T DEL (Topic)
 @findex gnus-topic-delete
 Delete an empty topic (@code{gnus-topic-delete}).
 @item A T
-@kindex A T (Group)
+@kindex A T (Topic)
 @findex gnus-topic-list-active
 List all groups that Gnus knows about in a topics-ified way
 (@code{gnus-topic-list-active}).
-@end table
+@item G p
+@kindex G p (Topic)
+@findex gnus-topic-edit-parameters
+@cindex group parameters
+@cindex topic parameters
+@cindex parameters
+Edit the topic parameters (@code{gnus-topic-edit-parameters}).
+@xref{Topic Parameters}.
+@end table
+@node Topic Sorting
+@subsection Topic Sorting
+@cindex topic sorting
+You can sort the groups in each topic individually with the following
+commands:
+@table @kbd
+@item T S a
+@kindex T S a (Topic)
+@findex gnus-topic-sort-groups-by-alphabet
+Sort the current topic alphabetically by group name
+(@code{gnus-topic-sort-groups-by-alphabet}).
+@item T S u
+@kindex T S u (Topic)
+@findex gnus-topic-sort-groups-by-unread
+Sort the current topic by the number of unread articles
+(@code{gnus-topic-sort-groups-by-unread}).
+@item T S l
+@kindex T S l (Topic)
+@findex gnus-topic-sort-groups-by-level
+Sort the current topic by group level
+(@code{gnus-topic-sort-groups-by-level}).
+@item T S v
+@kindex T S v (Topic)
+@findex gnus-topic-sort-groups-by-score
+Sort the current topic by group score
+(@code{gnus-topic-sort-groups-by-score}).
+@item T S r
+@kindex T S r (Topic)
+@findex gnus-topic-sort-groups-by-rank
+Sort the current topic by group rank
+(@code{gnus-topic-sort-groups-by-rank}).
+@item T S m
+@kindex T S m (Topic)
+@findex gnus-topic-sort-groups-by-method
+Sort the current topic alphabetically by backend name
+(@code{gnus-topic-sort-groups-by-method}).
+@end table
+@xref{Sorting Groups} for more information about group sorting.
 @node Topic Topology
 @subsection Topic Topology
 @cindex topic topology
 So, let's have a look at an example group buffer:
 @example
 Gnus
 Emacs -- I wuw it!
 3: comp.emacs
 2: alt.religion.emacs
 Naughty Emacs
 452: alt.sex.emacs
 0: comp.talk.emacs.recovery
 Misc
 8: comp.binaries.fractals
 13: comp.sources.unix
 @end example
-So, here we have one top-level topic, two topics under that, and one
+So, here we have one top-level topic (@samp{Gnus}), two topics under
-sub-topic under one of the sub-topics.  (There is always just one (1)
+that, and one sub-topic under one of the sub-topics.  (There is always
-top-level topic).  This topology can be expressed as follows:
+just one (1) top-level topic).  This topology can be expressed as
+follows:
 @lisp
 (("Gnus" visible)
 (("Emacs -- I wuw it!" visible)
 (("Naughty Emacs" visible)))
 This topology shows what topics are sub-topics of what topics (right),
 and which topics are visible.  Two settings are currently
 allowed---@code{visible} and @code{invisible}.
+@node Topic Parameters
+@subsection Topic Parameters
+@cindex topic parameters
+All groups in a topic will inherit group parameters from the parent (and
+ancestor) topic parameters.  All legal group parameters are legal topic
+parameters (@pxref{Group Parameters}).
+Group parameters (of course) override topic parameters, and topic
+parameters in sub-topics override topic parameters in super-topics.  You
+know.  Normal inheritance rules.  (@dfn{Rules} is here a noun, not a
+verb, although you may feel free to disagree with me here.)
+@example
+Gnus
+Emacs
+3: comp.emacs
+2: alt.religion.emacs
+452: alt.sex.emacs
+Relief
+452: alt.sex.emacs
+0: comp.talk.emacs.recovery
+Misc
+8: comp.binaries.fractals
+13: comp.sources.unix
+452: alt.sex.emacs
+@end example
+The @samp{Emacs} topic has the topic parameter @code{(score-file
+. "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
+@code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
+topic parameter @code{(score-file . "emacs.SCORE")}.  In addition,
+@samp{alt.religion.emacs} has the group parameter @code{(score-file
+. "religion.SCORE")}.
+Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
+will get the @file{relief.SCORE} home score file.  If you enter the same
+group in the @samp{Emacs} topic, you'll get the @file{emacs.SCORE} home
+score file.  If you enter the group @samp{alt.religion.emacs}, you'll
+get the @file{religion.SCORE} home score file.
+This seems rather simple and self-evident, doesn't it?  Well, yes.  But
+there are some problems, especially with the @code{total-expiry}
+parameter.  Say you have a mail group in two topics; one with
+@code{total-expiry} and one without.  What happens when you do @kbd{M-x
+gnus-expire-all-expirable-groups}?  Gnus has no way of telling which one
+of these topics you mean to expire articles from, so anything may
+happen.  In fact, I hereby declare that it is @dfn{undefined} what
+happens.  You just have to be careful if you do stuff like that.
 @node Misc Group Stuff
 @section Misc Group Stuff
 @menu
 * Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
 * Group Information::     Information and help on groups and Gnus.
+* Group Timestamp::       Making Gnus keep track of when you last read a group.
 * File Commands::         Reading and writing the Gnus files.
 @end menu
 @table @kbd
 @item ^
 @kindex ^ (Group)
 @findex gnus-group-enter-server-mode
-Enter the server buffer (@code{gnus-group-enter-server-mode}). @xref{The
+Enter the server buffer (@code{gnus-group-enter-server-mode}).
-Server Buffer}.
+@xref{The Server Buffer}.
 @item a
 @kindex a (Group)
 @findex gnus-group-post-news
 Post an article to a group (@code{gnus-group-post-news}).  The current
 @item M-g
 @kindex M-g (Group)
 @findex gnus-group-get-new-news-this-group
 @vindex gnus-goto-next-group-when-activating
 Check whether new articles have arrived in the current group
-(@code{gnus-group-get-new-news-this-group}).  The
+(@code{gnus-group-get-new-news-this-group}).
-@code{gnus-goto-next-group-when-activating} variable controls whether
+@code{gnus-goto-next-group-when-activating} says whether this command is
-this command is to move point to the next group or not.  It is @code{t}
+to move point to the next group or not.  It is @code{t} by default.
-by default.
 @findex gnus-activate-all-groups
 @cindex activating groups
 @item C-c M-g
 @kindex C-c M-g (Group)
 @item R
 @kindex R (Group)
 @cindex restarting
 @findex gnus-group-restart
-Restart Gnus (@code{gnus-group-restart}).
+Restart Gnus (@code{gnus-group-restart}).  This saves the @file{.newsrc}
+file(s), closes the connection to all servers, clears up all run-time
+Gnus variables, and then starts Gnus all over again.
 @end table
 @vindex gnus-get-new-news-hook
 @code{gnus-get-new-news-hook} is run just before checking for new news.
 @cindex group information
 @cindex information on groups
 @table @kbd
-@item M-f
-@kindex M-f (Group)
+@item H f
+@kindex H f (Group)
 @findex gnus-group-fetch-faq
+@vindex gnus-group-faq-directory
 @cindex FAQ
 @cindex ange-ftp
 Try to fetch the FAQ for the current group
 (@code{gnus-group-fetch-faq}).  Gnus will try to get the FAQ from
 @code{gnus-group-faq-directory}, which is usually a directory on a
-remote machine.  @code{ange-ftp} will be used for fetching the file.
+remote machine.  This variable can also be a list of directories.  In
+that case, giving a prefix to this command will allow you to choose
-@item D
+between the various sites.  @code{ange-ftp} (or @code{efs}) will be used
-@kindex D (Group)
+for fetching the file.
+If fetching from the first site is unsuccessful, Gnus will attempt to go
+through @code{gnus-group-faq-directory} and try to open them one by one.
+@item H d
+@itemx C-c C-d
+@kindex H d (Group)
+@kindex C-c C-d (Group)
 @cindex describing groups
 @cindex group description
 @findex gnus-group-describe-group
 Describe the current group (@code{gnus-group-describe-group}).  If given
 a prefix, force Gnus to re-read the description from the server.
 @findex gnus-info-find-node
 Go to the Gnus info node (@code{gnus-info-find-node}).
 @end table
+@node Group Timestamp
+@subsection Group Timestamp
+@cindex timestamps
+@cindex group timestamps
+It can be convenient to let Gnus keep track of when you last read a
+group.  To set the ball rolling, you should add
+@code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
+@lisp
+(add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
+@end lisp
+After doing this, each time you enter a group, it'll be recorded.
+This information can be displayed in various ways---the easiest is to
+use the @samp{%d} spec in the group line format:
+@lisp
+(setq gnus-group-line-format
+"%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
+@end lisp
+This will result in lines looking like:
+@example
+*        0: mail.ding                                19961002T012943
+0: custom                                   19961002T012713
+@end example
+As you can see, the date is displayed in compact ISO 8601 format.  This
+may be a bit too much, so to just display the date, you could say
+something like:
+@lisp
+(setq gnus-group-line-format
+"%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
+@end lisp
 @node File Commands
 @subsection File Commands
 @cindex file commands
 @table @kbd
 @item r
 @kindex r (Group)
 @findex gnus-group-read-init-file
 @vindex gnus-init-file
 @cindex reading init file
-Read the init file (@code{gnus-init-file}, which defaults to
+Re-read the init file (@code{gnus-init-file}, which defaults to
 @file{~/.gnus}) (@code{gnus-group-read-init-file}).
 @item s
 @kindex s (Group)
 @findex gnus-group-save-newsrc
 @chapter The Summary Buffer
 @cindex summary buffer
 A line for each article is displayed in the summary buffer.  You can
 move around, read articles, post articles and reply to articles.
+The most common way to a summary buffer is to select a group from the
+group buffer (@pxref{Selecting a Group}).
+You can have as many summary buffers open as you wish.
 @menu
 * Summary Buffer Format::       Deciding how the summary buffer is to look.
 * Summary Maneuvering::         Moving around the summary buffer.
 * Choosing Articles::           Reading articles.
 * Persistent Articles::         Making articles expiry-resistant.
 * Article Backlog::             Having already read articles hang around.
 * Saving Articles::             Ways of customizing article saving.
 * Decoding Articles::           Gnus can treat series of (uu)encoded articles.
 * Article Treatment::           The article buffer can be mangled at will.
+* Article Commands::            Doing various things with the article buffer.
 * Summary Sorting::             Sorting the summary buffer in various ways.
 * Finding the Parent::          No child support? Get the parent.
 * Alternative Approaches::      Reading using non-default summaries.
 * Tree Display::                A more visual display of threads.
 * Mail Group Commands::         Some commands can only be used in mail groups.
 * Various Summary Stuff::       What didn't fit anywhere else.
 * Exiting the Summary Buffer::  Returning to the Group buffer.
+* Crosspost Handling::          How crossposted articles are dealt with.
+* Duplicate Suppression::       An alternative when crosspost handling fails.
 @end menu
 @node Summary Buffer Format
 @section Summary Buffer Format
 @subsection Summary Buffer Lines
 @vindex gnus-summary-line-format
 You can change the format of the lines in the summary buffer by changing
 the @code{gnus-summary-line-format} variable.  It works along the same
-lines a a normal @code{format} string, with some extensions.
+lines a a normal @code{format} string, with some extensions
+(@pxref{Formatting Variables}).
 The default string is @samp{%U%R%z%I%(%[%4L: %-20,20n%]%) %s\n}.
 The following format specification characters are understood:
 @item N
 Article number.
 @item S
 Subject string.
 @item s
-Subject if the article is the root, @code{gnus-summary-same-subject}
+Subject if the article is the root or the previous article had a
-otherwise.
+different subject, @code{gnus-summary-same-subject} otherwise.
+(@code{gnus-summary-same-subject} defaults to @samp{}.)
 @item F
-Full @code{From} line.
+Full @code{From} header.
 @item n
 The name (from the @code{From} header).
 @item a
 The name (from the @code{From} header).  This differs from the @code{n}
-spec in that it uses @code{gnus-extract-address-components}, which is
+spec in that it uses the function designated by the
-slower, but may be more thorough.
+@code{gnus-extract-address-components} variable, which is slower, but
+may be more thorough.
 @item A
 The address (from the @code{From} header).  This works the same way as
 the @code{a} spec.
 @item L
 Number of lines in the article.
 @item I
 Indentation based on thread level (@pxref{Customizing Threading}).
 @item T
 Nothing if the article is a root and lots of spaces if it isn't (it
 pushes everything after it off the screen).
-@item \[
+@item [
-Opening bracket, which is normally @samp{\[}, but can also be @samp{<}
+Opening bracket, which is normally @samp{[}, but can also be @samp{<}
-for adopted articles.
+for adopted articles (@pxref{Customizing Threading}).
-@item \]
+@item ]
-Closing bracket, which is normally @samp{\]}, but can also be @samp{>}
+Closing bracket, which is normally @samp{]}, but can also be @samp{>}
 for adopted articles.
 @item >
 One space for each thread level.
 @item <
 Twenty minus thread level spaces.
 Total thread score.
 @item x
 @code{Xref}.
 @item D
 @code{Date}.
+@item d
+The @code{Date} in @code{DD-MMM} format.
+@item o
+The @code{Date} in @code{YYYYMMDDTHHMMSS} format.
 @item M
 @code{Message-ID}.
 @item r
 @code{References}.
 @item t
 Number of articles in the current sub-thread.  Using this spec will slow
 down summary buffer generation somewhat.
 @item e
-A single character will be displayed if the article has any children.
+An @samp{=} (@code{gnus-not-empty-thread-mark}) will be displayed if the
+article has any children.
+@item P
+The line number.
 @item u
 User defined specifier.  The next character in the format string should
 be a letter.  @sc{gnus} will call the function
 @code{gnus-user-format-function-}@samp{X}, where @samp{X} is the letter
 following @samp{%u}.  The function will be passed the current header as
 @node Summary Buffer Mode Line
 @subsection Summary Buffer Mode Line
 @vindex gnus-summary-mode-line-format
 You can also change the format of the summary mode bar.  Set
-@code{gnus-summary-mode-line-format} to whatever you like.  Here are the
+@code{gnus-summary-mode-line-format} to whatever you like.  The default
-elements you can play with:
+is @samp{Gnus: %%b [%A] %Z}.
+Here are the elements you can play with:
 @table @samp
 @item G
 Group name.
 @item p
 Number of unread articles in this group.
 @item e
 Number of unselected articles in this group.
 @item Z
 A string with the number of unread and unselected articles represented
-either as @samp{<%U(+%u) more>} if there are both unread and unselected
+either as @samp{<%U(+%e) more>} if there are both unread and unselected
 articles, and just as @samp{<%U more>} if there are just unread articles
 and no unselected ones.
 @item g
 Shortish group name.  For instance, @samp{rec.arts.anime} will be
 shortened to @samp{r.a.anime}.
 @item S
 Subject of the current article.
 @item u
-Used-defined spec.
+User-defined spec.
 @item s
 Name of the current score file.
 @item d
 Number of dormant articles.
 @item t
 highlight the current article in the summary buffer.
 @item gnus-summary-highlight
 @vindex gnus-summary-highlight
 Summary lines are highlighted according to this variable, which is a
-list where the elements are on the format @code{(FORM . FACE)}.  If you
+list where the elements are on the format @var{(FORM . FACE)}.  If you
 would, for instance, like ticked articles to be italic and high-scored
 articles to be bold, you could set this variable to something like
 @lisp
 (((eq mark gnus-ticked-mark) . italic)
 ((> score default) . bold))
 @item G j
 @itemx j
 @kindex j (Summary)
 @kindex G j (Summary)
 @findex gnus-summary-goto-article
-Ask for an article number and then go that article
+Ask for an article number and then go to that article
 (@code{gnus-summary-goto-article}).
 @item G g
 @kindex G g (Summary)
 @findex gnus-summary-goto-subject
 Ask for an article number and then go the summary line of that article
-(@code{gnus-summary-goto-subject}).
+without displaying the article (@code{gnus-summary-goto-subject}).
 @end table
 If Gnus asks you to press a key to confirm going to the next group, you
 can use the @kbd{C-n} and @kbd{C-p} keys to move around the group
 buffer, searching for the next group to read without actually returning
 @table @code
 @vindex gnus-auto-select-next
 @item gnus-auto-select-next
-If you are at the end of the group and issue one of the movement
+If you issue one of the movement commands (like @kbd{n}) and there are
-commands, Gnus will offer to go to the next group.  If this variable is
+no more unread articles after the current one, Gnus will offer to go to
-@code{t} and the next group is empty, Gnus will exit summary mode and
+the next group.  If this variable is @code{t} and the next group is
-return to the group buffer.  If this variable is neither @code{t} nor
+empty, Gnus will exit summary mode and return to the group buffer.  If
-@code{nil}, Gnus will select the next group, no matter whether it has
+this variable is neither @code{t} nor @code{nil}, Gnus will select the
-any unread articles or not.  As a special case, if this variable is
+next group, no matter whether it has any unread articles or not.  As a
-@code{quietly}, Gnus will select the next group without asking for
+special case, if this variable is @code{quietly}, Gnus will select the
-confirmation.  If this variable is @code{almost-quietly}, the same will
+next group without asking for confirmation.  If this variable is
-happen only if you are located on the last article in the group.
+@code{almost-quietly}, the same will happen only if you are located on
-Finally, if this variable is @code{slightly-quietly}, the @kbd{Z n}
+the last article in the group.  Finally, if this variable is
-command will go to the next group without confirmation.  Also
+@code{slightly-quietly}, the @kbd{Z n} command will go to the next group
-@pxref{Group Levels}.
+without confirmation.  Also @pxref{Group Levels}.
 @item gnus-auto-select-same
 @vindex gnus-auto-select-same
 If non-@code{nil}, all the movement commands will try to go to the next
 article with the same subject as the current.  (@dfn{Same} here might
 @node Choosing Articles
 @section Choosing Articles
 @cindex selecting articles
+@menu
+* Choosing Commands::        Commands for choosing articles.
+* Choosing Variables::       Variables that influence these commands.
+@end menu
+@node Choosing Commands
+@subsection Choosing Commands
 None of the following movement commands understand the numeric prefix,
 and they all select and display an article.
 @table @kbd
 @item SPACE
 Pop an article off the summary history and go to this article
 (@code{gnus-summary-pop-article}).  This command differs from the
 command above in that you can pop as many previous articles off the
 history as you like.
 @end table
+@node Choosing Variables
+@subsection Choosing Variables
 Some variables that are relevant for moving and selecting articles:
 @table @code
 @item gnus-auto-extend-newsgroup
 @kindex A > (Summary)
 @findex gnus-summary-end-of-article
 Scroll to the end of the article (@code{gnus-summary-end-of-article}).
 @item A s
+@itemx s
 @kindex A s (Summary)
+@kindex s (Summary)
 @findex gnus-summary-isearch-article
 Perform an isearch in the article buffer
 (@code{gnus-summary-isearch-article}).
 @end table
 @findex gnus-summary-reply-with-original
 Mail a reply to the author of the current article and include the
 original message (@code{gnus-summary-reply-with-original}).  This
 command uses the process/prefix convention.
+@item S w
+@kindex S w (Summary)
+@findex gnus-summary-wide-reply
+Mail a wide reply to the author of the current article
+(@code{gnus-summary-wide-reply}).
+@item S W
+@kindex S W (Summary)
+@findex gnus-summary-wide-reply-with-original
+Mail a wide reply to the current article and include the original
+message (@code{gnus-summary-reply-with-original}).  This command uses
+the process/prefix convention.
 @item S o m
 @kindex S o m (Summary)
 @findex gnus-summary-mail-forward
 Forward the current article to some other person
-(@code{gnus-summary-mail-forward}).
+(@code{gnus-summary-mail-forward}).  If given a prefix, include the full
+headers of the forwarded article.
-@item S o p
-@kindex S o p (Summary)
-@findex gnus-summary-post-forward
-Forward the current article to a newsgroup
-(@code{gnus-summary-post-forward}).
 @item S m
 @itemx m
 @kindex m (Summary)
 @kindex S m (Summary)
 This command is mainly used if you have several accounts and want to
 ship a mail to a different account of yours.  (If you're both
 @code{root} and @code{postmaster} and get a mail for @code{postmaster}
 to the @code{root} account, you may want to resend it to
-@code{postmaster}.  Ordnung muss sein!
+@code{postmaster}.  Ordnung mu� sein!
+This command understands the process/prefix convention
+(@pxref{Process/Prefix}).
 @item S O m
 @kindex S O m (Summary)
 @findex gnus-uu-digest-mail-forward
 Digest the current series and forward the result using mail
 (@code{gnus-uu-digest-mail-forward}).  This command uses the
 process/prefix convention (@pxref{Process/Prefix}).
-@item S O p
+@item S M-c
-@kindex S O p (Summary)
+@kindex S M-c (Summary)
-@findex gnus-uu-digest-post-forward
+@findex gnus-summary-mail-crosspost-complaint
-Digest the current series and forward the result to a newsgroup
+@cindex crossposting
-(@code{gnus-uu-digest-mail-forward}).
+@cindex excessive crossposting
+Send a complaint about excessive crossposting to the author of the
+current article (@code{gnus-summary-mail-crosspost-complaint}).
+@findex gnus-crosspost-complaint
+This command is provided as a way to fight back agains the current
+crossposting pandemic that's sweeping Usenet.  It will compose a reply
+using the @code{gnus-crosspost-complaint} variable as a preamble.  This
+command understands the process/prefix convention
+(@pxref{Process/Prefix}) and will prompt you before sending each mail.
 @end table
 @node Summary Post Commands
 @subsection Summary Post Commands
 @cindex post
 @cindex composing news
-Commands for posting an article:
+Commands for posting a news article:
 @table @kbd
 @item S p
 @itemx a
 @kindex a (Summary)
 @findex gnus-summary-followup-with-original
 Post a followup to the current article and include the original message
 (@code{gnus-summary-followup-with-original}).   This command uses the
 process/prefix convention.
+@item S n
+@kindex S n (Summary)
+@findex gnus-summary-followup-to-mail
+Post a followup to the current article via news, even if you got the
+message through mail (@code{gnus-summary-followup-to-mail}).
+@item S n
+@kindex S n (Summary)
+@findex gnus-summary-followup-to-mail
+Post a followup to the current article via news, even if you got the
+message through mail and include the original message
+(@code{gnus-summary-followup-to-mail-with-original}).  This command uses
+the process/prefix convention.
+@item S o p
+@kindex S o p (Summary)
+@findex gnus-summary-post-forward
+Forward the current article to a newsgroup
+(@code{gnus-summary-post-forward}).  If given a prefix, include the full
+headers of the forwarded article.
+@item S O p
+@kindex S O p (Summary)
+@findex gnus-uu-digest-post-forward
+Digest the current series and forward the result to a newsgroup
+(@code{gnus-uu-digest-mail-forward}).
 @item S u
 @kindex S u (Summary)
 @findex gnus-uu-post-news
 Uuencode a file, split it into parts, and post it as a series
 (@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
 have posted almost the same article twice.
 If you have just posted the article, and change your mind right away,
 there is a trick you can use to cancel/supersede the article without
 waiting for the article to appear on your site first.  You simply return
-to the post buffer (which is called @code{*post-buf*}).  There you will
+to the post buffer (which is called @code{*sent ...*}).  There you will
 find the article you just posted, with all the headers intact.  Change
 the @code{Message-ID} header to a @code{Cancel} or @code{Supersedes}
-header by substituting one of those words for @code{Message-ID}.  Then
+header by substituting one of those words for the word
-just press @kbd{C-c C-c} to send the article as you would do normally.
+@code{Message-ID}.  Then just press @kbd{C-c C-c} to send the article as
-The previous article will be canceled/superseded.
+you would do normally.  The previous article will be
+canceled/superseded.
 Just remember, kids: There is no 'c' in 'supersede'.
 @node Marking Articles
 @node Unread Articles
 @subsection Unread Articles
-The following marks mark articles as unread, in one form or other.
+The following marks mark articles as (kinda) unread, in one form or
+other.
-@vindex gnus-dormant-mark
-@vindex gnus-ticked-mark
 @table @samp
 @item !
+@vindex gnus-ticked-mark
+Marked as ticked (@code{gnus-ticked-mark}).
 @dfn{Ticked articles} are articles that will remain visible always.  If
 you see an article that you find interesting, or you want to put off
 reading it, or replying to it, until sometime later, you'd typically
 tick it.  However, articles can be expired, so if you want to keep an
-article forever, you'll have to save it.  Ticked articles have a
+article forever, you'll have to make it persistent (@pxref{Persistent
-@samp{!} (@code{gnus-ticked-mark}) in the first column.
+Articles}).
 @item ?
 @vindex gnus-dormant-mark
-A @dfn{dormant} article is marked with a @samp{?}
+Marked as dormant (@code{gnus-dormant-mark}).
-(@code{gnus-dormant-mark}), and will only appear in the summary buffer
-if there are followups to it.
+@dfn{Dormant articles} will only appear in the summary buffer if there
+are followups to it.
 @item SPACE
 @vindex gnus-unread-mark
-An @dfn{unread} article is marked with a @samp{SPACE}
+Markes as unread (@code{gnus-unread-mark}).
-(@code{gnus-unread-mark}).  These are articles that haven't been read at
-all yet.
+@dfn{Unread articles} are articles that haven't been read at all yet.
 @end table
 @node Read Articles
 @subsection Read Articles
 @table @samp
 @item r
 @vindex gnus-del-mark
-Articles that are marked as read.  They have a @samp{r}
+These are articles that the user has marked as read with the @kbd{d}
-(@code{gnus-del-mark}) in the first column.  These are articles that the
+command manually, more or less (@code{gnus-del-mark}).
-user has marked as read more or less manually.
 @item R
 @vindex gnus-read-mark
-Articles that are actually read are marked with @samp{R}
+Articles that have actually been read (@code{gnus-read-mark}).
-(@code{gnus-read-mark}).
 @item O
 @vindex gnus-ancient-mark
-Articles that were marked as read in previous sessions are now
+Articles that were marked as read in previous sessions and are now
-@dfn{old} and marked with @samp{O} (@code{gnus-ancient-mark}).
+@dfn{old} (@code{gnus-ancient-mark}).
 @item K
 @vindex gnus-killed-mark
 Marked as killed (@code{gnus-killed-mark}).
 @vindex gnus-canceled-mark
 Canceled article (@code{gnus-canceled-mark})
 @item F
 @vindex gnus-souped-mark
-@sc{SOUP}ed article (@code{gnus-souped-mark}).
+@sc{SOUP}ed article (@code{gnus-souped-mark}).  @xref{SOUP}.
 @item Q
 @vindex gnus-sparse-mark
-Sparsely reffed article (@code{gnus-sparse-mark}).
+Sparsely reffed article (@code{gnus-sparse-mark}).  @xref{Customizing
+Threading}.
+@item M
+@vindex gnus-duplicate-mark
+Article marked as read by duplicate suppression
+(@code{gnus-duplicated-mark}).  @xref{Duplicate Suppression}.
 @end table
 All these marks just mean that the article is marked as read, really.
-They are interpreted differently by the adaptive scoring scheme,
+They are interpreted differently when doing adaptive scoring, though.
-however.
 One more special mark, though:
 @table @samp
 @item E
 @vindex gnus-expirable-mark
-You can also mark articles as @dfn{expirable} (or have them marked as
+Marked as expirable (@code{gnus-expirable-mark}).
-such automatically).  That doesn't make much sense in normal groups,
-because a user does not control the expiring of news articles, but in
+Marking articles as @dfn{expirable} (or have them marked as such
-mail groups, for instance, articles that are marked as @dfn{expirable}
+automatically) doesn't make much sense in normal groups---a user doesn't
-can be deleted by Gnus at any time.  Expirable articles are marked with
+control the expiring of news articles, but in mail groups, for instance,
-@samp{E} (@code{gnus-expirable-mark}).
+articles that are marked as @dfn{expirable} can be deleted by Gnus at
+any time.
 @end table
 @node Other Marks
 @subsection Other Marks
 @item
 You can set a bookmark in the current article.  Say you are reading a
 long thesis on cats' urinary tracts, and have to go home for dinner
 before you've finished reading the thesis.  You can then set a bookmark
 in the article, and Gnus will jump to this bookmark the next time it
-encounters the article.
+encounters the article.  @xref{Setting Marks}
 @item
 @vindex gnus-replied-mark
 All articles that you have replied to or made a followup to (i.e., have
 answered) will be marked with an @samp{A} in the second column
 @kindex M d (Summary)
 @kindex d (Summary)
 @findex gnus-summary-mark-as-read-forward
 Mark the current article as read
 (@code{gnus-summary-mark-as-read-forward}).
+@item D
+@kindex D (Summary)
+@findex gnus-summary-mark-as-read-backward
+Mark the current article as read and move point to the previous line
+(@code{gnus-summary-mark-as-read-backward}).
 @item M k
 @itemx k
 @kindex k (Summary)
 @kindex M k (Summary)
 (@code{gnus-summary-kill-same-subject}).
 @item M C
 @kindex M C (Summary)
 @findex gnus-summary-catchup
-Mark all unread articles in the group as read
+Mark all unread articles as read (@code{gnus-summary-catchup}).
-(@code{gnus-summary-catchup}).
 @item M C-c
 @kindex M C-c (Summary)
 @findex gnus-summary-catchup-all
 Mark all articles in the group as read---even the ticked and dormant
 @kindex M P U (Summary)
 @findex gnus-summary-unmark-all-processable
 Remove the process mark from all articles
 (@code{gnus-summary-unmark-all-processable}).
+@item M P i
+@kindex M P i (Summary)
+@findex gnus-uu-invert-processable
+Invert the list of process marked articles
+(@code{gnus-uu-invert-processable}).
 @item M P R
 @kindex M P R (Summary)
 @findex gnus-uu-mark-by-regexp
 Mark articles by a regular expression (@code{gnus-uu-mark-by-regexp}).
 @item M P b
 @kindex M P b (Summary)
 @findex gnus-uu-mark-buffer
 Mark all articles in the buffer in the order they appear
 (@code{gnus-uu-mark-buffer}).
+@item M P k
+@kindex M P k (Summary)
+@findex gnus-summary-kill-process-mark
+Push the current process mark set onto the stack and unmark all articles
+(@code{gnus-summary-kill-process-mark}).
+@item M P y
+@kindex M P y (Summary)
+@findex gnus-summary-yank-process-mark
+Pop the previous process mark set from the stack and restore it
+(@code{gnus-summary-yank-process-mark}).
+@item M P w
+@kindex M P w (Summary)
+@findex gnus-summary-save-process-mark
+Push the current process mark set onto the stack
+(@code{gnus-summary-save-process-mark}).
 @end table
 @node Limiting
 @section Limiting
 @item / m
 @kindex / m (Summary)
 @findex gnus-summary-limit-to-marks
 Ask for a mark and then limit to all articles that have not been marked
 with that mark (@code{gnus-summary-limit-to-marks}).
+@item / t
+@kindex / t (Summary)
+@findex gnus-summary-limit-to-age
+Ask for a number and then limit the summary buffer to articles that are
+older than (or equal to) that number of days
+(@code{gnus-summary-limit-to-marks}).  If given a prefix, limit to
+articles that are younger than that number of days.
 @item / n
 @kindex / n (Summary)
 @findex gnus-summary-limit-to-articles
 Limit the summary buffer to the current article
 @c Written by Michael Ernst <mernst@cs.rice.edu>
 @lisp
 (setq gnus-simplify-ignored-prefixes
 (concat
 "\\`\\[?\\("
+(mapconcat
+'identity
+'("looking"
+"wanted" "followup" "summary\\( of\\)?"
+"help" "query" "problem" "question"
+"answer" "reference" "announce"
+"How can I" "How to" "Comparison of"
+;; ...
+)
+"\\|")
+"\\)\\s *\\("
 (mapconcat 'identity
-'("looking"
+'("for" "for reference" "with" "about")
-"wanted" "followup" "summary\\( of\\)?"
-"help" "query" "problem" "question"
-"answer" "reference" "announce"
-"How can I" "How to" "Comparison of"
-;; ...
-)
 "\\|")
-"\\)\\s *\\("
+"\\)?\\]?:?[ \t]*"))
-(mapconcat 'identity
-'("for" "for reference" "with" "about")
-"\\|")
-"\\)?\\]?:?[ \t]*"))
 @end lisp
 All words that match this regexp will be removed before comparing two
 subjects.
 @item gnus-thread-hide-subtree
 @vindex gnus-thread-hide-subtree
 If non-@code{nil}, all threads will be hidden when the summary buffer is
 generated.
+@item gnus-thread-expunge-below
+@vindex gnus-thread-expunge-below
+All threads that have a total score (as defined by
+@code{gnus-thread-score-function}) less than this number will be
+expunged.  This variable is @code{nil} by default, which means that no
+threads are expunged.
 @item gnus-thread-hide-killed
 @vindex gnus-thread-hide-killed
 if you kill a thread and this variable is non-@code{nil}, the subtree
 will be hidden.
 in a new thread.
 @item gnus-thread-indent-level
 @vindex gnus-thread-indent-level
 This is a number that says how much each sub-thread should be indented.
-The default is @code{4}.
+The default is 4.
+@item gnus-parse-headers-hook
+@vindex gnus-parse-headers-hook
+Hook run before parsing any headers.  The default value is
+@code{(gnus-decode-rfc1522)}, which means that QPized headers will be
+slightly decoded in a hackish way.  This is likely to change in the
+future when Gnus becomes @sc{MIME}ified.
 @end table
 @node Thread Commands
 @subsection Thread Commands
 @item T k
 @itemx M-C-k
 @kindex T k (Summary)
 @kindex M-C-k (Summary)
 @findex gnus-summary-kill-thread
-Mark all articles in the current sub-thread as read
+Mark all articles in the current (sub-)thread as read
 (@code{gnus-summary-kill-thread}).  If the prefix argument is positive,
 remove all marks instead.  If the prefix argument is negative, tick
 articles instead.
 @item T l
 @itemx M-C-l
 @kindex T l (Summary)
 @kindex M-C-l (Summary)
 @findex gnus-summary-lower-thread
-Lower the score of the current thread
+Lower the score of the current (sub-)thread
 (@code{gnus-summary-lower-thread}).
 @item T i
 @kindex T i (Summary)
 @findex gnus-summary-raise-thread
-Increase the score of the current thread
+Increase the score of the current (sub-)thread
 (@code{gnus-summary-raise-thread}).
 @item T #
 @kindex T # (Summary)
 @findex gnus-uu-mark-thread
-Set the process mark on the current thread
+Set the process mark on the current (sub-)thread
 (@code{gnus-uu-mark-thread}).
 @item T M-#
 @kindex T M-# (Summary)
 @findex gnus-uu-unmark-thread
-Remove the process mark from the current thread
+Remove the process mark from the current (sub-)thread
 (@code{gnus-uu-unmark-thread}).
 @item T T
 @kindex T T (Summary)
 @findex gnus-summary-toggle-threads
 Toggle threading (@code{gnus-summary-toggle-threads}).
 @item T s
 @kindex T s (Summary)
 @findex gnus-summary-show-thread
-Expose the thread hidden under the current article, if any
+Expose the (sub-)thread hidden under the current article, if any
 (@code{gnus-summary-show-thread}).
 @item T h
 @kindex T h (Summary)
 @findex gnus-summary-hide-thread
-Hide the current (sub)thread (@code{gnus-summary-hide-thread}).
+Hide the current (sub-)thread (@code{gnus-summary-hide-thread}).
 @item T S
 @kindex T S (Summary)
 @findex gnus-summary-show-all-threads
 Expose all hidden threads (@code{gnus-summary-show-all-threads}).
 @node Asynchronous Fetching
 @section Asynchronous Article Fetching
 @cindex asynchronous article fetching
+@cindex article pre-fetch
+@cindex pre-fetch
 If you read your news from an @sc{nntp} server that's far away, the
 network latencies may make reading articles a chore.  You have to wait
 for a while after pressing @kbd{n} to go to the next article before the
 article appears.  Why can't Gnus just go ahead and fetch the article
-while you are reading the previous one? Why not, indeed.
+while you are reading the previous one?  Why not, indeed.
 First, some caveats.  There are some pitfalls to using asynchronous
 article fetching, especially the way Gnus does it.
 Let's say you are reading article 1, which is short, and article 2 is
 @vindex gnus-asynchronous
 Here's how:  Set @code{gnus-asynchronous} to @code{t}.  The rest should
 happen automatically.
-@vindex nntp-async-number
+@vindex gnus-use-article-prefetch
 You can control how many articles that are to be pre-fetched by setting
-@code{nntp-async-number}.  This is five by default, which means that when
+@code{gnus-use-article-prefetch}.  This is 30 by default, which means
-you read an article in the group, @code{nntp} will pre-fetch the next
+that when you read an article in the group, the backend will pre-fetch
-five articles.  If this variable is @code{t}, @code{nntp} will pre-fetch
+the next 30 articles.  If this variable is @code{t}, the backend will
-all the articles that it can without bound.  If it is @code{nil}, no
+pre-fetch all the articles that it can without bound.  If it is
-pre-fetching will be made.
+@code{nil}, no pre-fetching will be made.
-@vindex gnus-asynchronous-article-function
+@vindex gnus-async-prefetch-article-p
-You may wish to create some sort of scheme for choosing which articles
+@findex gnus-async-read-p
-that @code{nntp} should consider as candidates for pre-fetching.  For
+There are probably some articles that you don't want to pre-fetch---read
-instance, you may wish to pre-fetch all articles with high scores, and
+articles, for instance.  Which articles to pre-fetch is controlled by
-not pre-fetch low-scored articles.  You can do that by setting the
+the @code{gnus-async-prefetch-article-p} variable.  This function should
-@code{gnus-asynchronous-article-function}, which will be called with an
+return non-@code{nil} when the article in question is to be
-alist where the keys are the article numbers.  Your function should
+pre-fetched.  The default is @code{gnus-async-read-p}, which returns
-return an alist where the articles you are not interested in have been
+@code{nil} on read articles.  The function is called with an article
-removed.  You could also do sorting on article score and the like.
+data structure as the only parameter.
+If, for instance, you wish to pre-fetch only unread articles that are
+shorter than 100 lines, you could say something like:
+@lisp
+(defun my-async-short-unread-p (data)
+"Return non-nil for short, unread articles."
+(and (gnus-data-unread-p data)
+(< (mail-header-lines (gnus-data-header data))
+100)))
+(setq gnus-async-prefetch-article-p 'my-async-short-unread-p)
+@end lisp
+These functions will be called many, many times, so they should
+preferrably be short and sweet to avoid slowing down Gnus too much.
+It's also probably a good idea to byte-compile things like this.
+@vindex gnus-prefetched-article-deletion-strategy
+Articles have to be removed from the asynch buffer sooner or later.  The
+@code{gnus-prefetched-article-deletion-strategy} says when to remove
+articles.  This is a list that may contain the following elements:
+@table @code
+@item read
+Remove articles when they are read.
+@item exit
+Remove articles when exiting the group.
+@end table
+The default value is @code{(read exit)}.
+@vindex gnus-use-header-prefetch
+If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
+from the next group.
 @node Article Caching
 @section Article Caching
 @cindex article caching
 @item O f
 @kindex O f (Summary)
 @findex gnus-summary-save-article-file
 Save the current article in plain file format
 (@code{gnus-summary-save-article-file}).
+@item O F
+@kindex O F (Summary)
+@findex gnus-summary-write-article-file
+Write the current article in plain file format, overwriting any previous
+file contents (@code{gnus-summary-write-article-file}).
 @item O b
 @kindex O b (Summary)
 @findex gnus-summary-save-article-body-file
 Save the current article body in plain file format
 @table @code
 @item gnus-Numeric-save-name
 @findex gnus-Numeric-save-name
-Generates file names that look like @file{~/News/Alt.andrea-dworkin/45}.
+File names like @file{~/News/Alt.andrea-dworkin/45}.
 @item gnus-numeric-save-name
 @findex gnus-numeric-save-name
-Generates file names that look like @file{~/News/alt.andrea-dworkin/45}.
+File names like @file{~/News/alt.andrea-dworkin/45}.
 @item gnus-Plain-save-name
 @findex gnus-Plain-save-name
-Generates file names that look like @file{~/News/Alt.andrea-dworkin}.
+File names like @file{~/News/Alt.andrea-dworkin}.
 @item gnus-plain-save-name
 @findex gnus-plain-save-name
-Generates file names that look like @file{~/News/alt.andrea-dworkin}.
+File names like @file{~/News/alt.andrea-dworkin}.
 @end table
 @vindex gnus-split-methods
 You can have Gnus suggest where to save articles by plonking a regexp into
 the @code{gnus-split-methods} alist.  For instance, if you would like to
 @cindex sox
 This variable is consulted first when viewing files.  If you wish to use,
 for instance, @code{sox} to convert an @samp{.au} sound file, you could
 say something like:
 @lisp
 (setq gnus-uu-user-view-rules
 (list '(\"\\\\.au$\" \"sox %s -t .aiff > /dev/audio\")))
 @end lisp
 @item gnus-uu-user-view-rules-end
 @vindex gnus-uu-user-view-rules-end
 This variable is consulted if Gnus couldn't make any matches from the
 @item gnus-uu-grab-move
 @findex gnus-uu-grab-move
 Move the file (if you're using a saving function.)
 @end table
+@item gnus-uu-be-dangerous
+@vindex gnus-uu-be-dangerous
+Specifies what to do if unusual situations arise during decoding.  If
+@code{nil}, be as conservative as possible.  If @code{t}, ignore things
+that didn't work, and overwrite existing files.  Otherwise, ask each
+time.
 @item gnus-uu-ignore-files-by-name
 @vindex gnus-uu-ignore-files-by-name
 Files with name matching this regular expression won't be viewed.
 writing, so there are tons of functions and variables to make reading
 these articles easier.
 @menu
 * Article Highlighting::    You want to make the article look like fruit salad.
+* Article Fontisizing::     Making emphasized text look niced.
 * Article Hiding::          You also want to make certain info go away.
 * Article Washing::         Lots of way-neat functions to make life better.
 * Article Buttons::         Click on URLs, Message-IDs, addresses and the like.
 * Article Date::            Grumble, UT!
+* Article Signature::       What is a signature?
 @end menu
 @node Article Highlighting
 @subsection Article Highlighting
 @kindex W H s (Summary)
 @vindex gnus-signature-separator
 @vindex gnus-signature-face
 @findex gnus-article-highlight-signature
 Highlight the signature (@code{gnus-article-highlight-signature}).
-Everything after @code{gnus-signature-separator} in an article will be
+Everything after @code{gnus-signature-separator} (@pxref{Article
-considered a signature and will be highlighted with
+Signature}) in an article will be considered a signature and will be
-@code{gnus-signature-face}, which is @code{italic} by default.
+highlighted with @code{gnus-signature-face}, which is @code{italic} by
+default.
-@end table
+@end table
+@node Article Fontisizing
+@subsection Article Fontisizing
+@cindex emphasis
+@cindex article emphasis
+@findex gnus-article-emphasize
+@kindex W e (Summary)
+People commonly add emphasis to words in news articles by writing things
+like @samp{_this_} or @samp{*this*}.  Gnus can make this look nicer by
+running the article through the @kbd{W e}
+(@code{gnus-article-emphasize}) command.
+@vindex gnus-article-emphasis
+How the emphasis is computed is controlled by the
+@code{gnus-article-emphasis} variable.  This is an alist where the first
+element is a regular expression to be matched.  The second is a number
+that says what regular expression grouping used to find the entire
+emphasized word.  The third is a number that says what regexp grouping
+should be displayed and highlighted.  (The text between these two
+groupings will be hidden.)  The fourth is the face used for
+highlighting.
+@lisp
+(setq gnus-article-emphasis
+'(("_\\(\\w+\\)_" 0 1 gnus-emphasis-underline)
+("\\*\\(\\w+\\)\\*" 0 1 gnus-emphasis-bold)))
+@end lisp
+@vindex gnus-emphasis-underline
+@vindex gnus-emphasis-bold
+@vindex gnus-emphasis-italic
+@vindex gnus-emphasis-underline-bold
+@vindex gnus-emphasis-underline-italic
+@vindex gnus-emphasis-bold-italic
+@vindex gnus-emphasis-underline-bold-italic
+By default, there are seven rules, and they use the following faces:
+@code{gnus-emphasis-bold}, @code{gnus-emphasis-italic},
+@code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
+@code{gnus-emphasis-underline-italic},
+@code{gnus-emphasis-undeline-bold}, and
+@code{gnus-emphasis-underline-bold-italic}.
+If you want to change these faces, you can either use @kbd{M-x
+customize}, or you can use @code{copy-face}.  For instance, if you want
+to make @code{gnus-emphasis-italic} use a red face instead, you could
+say something like:
+@lisp
+(copy-face 'red 'gnus-emphasis-italic)
+@end lisp
 @node Article Hiding
 @subsection Article Hiding
 @cindex article hiding
 (@code{gnus-article-hide-boring-headers}).  @xref{Hiding Headers}.
 @item W W s
 @kindex W W s (Summary)
 @findex gnus-article-hide-signature
-Hide signature (@code{gnus-article-hide-signature}).
+Hide signature (@code{gnus-article-hide-signature}).  @xref{Article
+Signature}.
 @item W W p
 @kindex W W p (Summary)
 @findex gnus-article-hide-pgp
 Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}).
 @item W W P
 @kindex W W P (Summary)
 @findex gnus-article-hide-pem
-Hide @sc{pem} (privacy enhavnced hessages) gruft
+Hide @sc{pem} (privacy enhanced messages) gruft
 (@code{gnus-article-hide-pem}).
 @item W W c
 @kindex W W c (Summary)
 @findex gnus-article-hide-citation
 @item gnus-cited-text-button-line-format
 @vindex gnus-cited-text-button-line-format
 Gnus adds buttons show where the cited text has been hidden, and to
 allow toggle hiding the text.  The format of the variable is specified
-by this format-like variable.  These specs are legal:
+by this format-like variable (@pxref{Formatting Variables}).  These
+specs are legal:
 @table @samp
 @item b
 Start point of the hidden text.
 @item e
 hidden.  If you give a positive prefix, they will always hide.
 Also @pxref{Article Highlighting} for further variables for
 citation customization.
-@vindex gnus-signature-limit
-@code{gnus-signature-limit} provides a limit to what is considered a
-signature.  If it is a number, no signature may not be longer (in
-characters) than that number.  If it is a function, the function will be
-called without any parameters, and if it returns @code{nil}, there is no
-signature in the buffer.  If it is a string, it will be used as a
-regexp.  If it matches, the text in question is not a signature.
 @node Article Washing
 @subsection Article Washing
 @cindex washing
 @cindex article washing
 @findex gnus-article-fill-cited-article
 Do word wrap (@code{gnus-article-fill-cited-article}).  If you use this
 function in @code{gnus-article-display-hook}, it should be run fairly
 late and certainly after any highlighting.
+You can give the command a numerical prefix to specify the width to use
+when filling.
 @item W c
 @kindex W c (Summary)
 @findex gnus-article-remove-cr
 Remove CR (@code{gnus-article-remove-cr}).
-@item W L
-@kindex W L (Summary)
-@findex gnus-article-remove-trailing-blank-lines
-Remove all blank lines at the end of the article
-(@code{gnus-article-remove-trailing-blank-lines}).
 @item W q
 @kindex W q (Summary)
 @findex gnus-article-de-quoted-unreadable
 Treat quoted-printable (@code{gnus-article-de-quoted-unreadable}).
 @kindex W B (Summary)
 @findex gnus-article-add-buttons-to-head
 Add clickable buttons to the article headers
 (@code{gnus-article-add-buttons-to-head}).
+@item W E l
+@kindex W E l (Summary)
+@findex gnus-article-strip-leading-blank-lines
+Remove all blank lines from the beginning of the article
+(@code{gnus-article-strip-leading-blank-lines}).
+@item W E m
+@kindex W E m (Summary)
+@findex gnus-article-strip-multiple-blank-lines
+Replace all blank lines with empty lines and then all multiple empty
+lines with a single empty line.
+(@code{gnus-article-strip-multiple-blank-lines}).
+@item W E t
+@kindex W E t (Summary)
+@findex gnus-article-remove-trailing-blank-lines
+Remove all blank lines at the end of the article
+(@code{gnus-article-remove-trailing-blank-lines}).
+@item W E a
+@kindex W E a (Summary)
+@findex gnus-article-strip-blank-lines
+Do all the three commands above
+(@code{gnus-article-strip-blank-lines}).
 @end table
 @node Article Buttons
 @subsection Article Buttons
 @samp{<URL:\\([^\n\r>]*\\)>}.
 @item button-par
 Gnus has to know which parts of the match is to be highlighted.  This is
 a number that says what sub-expression of the regexp that is to be
-highlighted.  If you want it all highlighted, you use @code{0} here.
+highlighted.  If you want it all highlighted, you use 0 here.
 @item use-p
 This form will be @code{eval}ed, and if the result is non-@code{nil},
 this is considered a match.  This is useful if you want extra sifting to
 avoid false matches.
 A regular expression that matches embedded URLs.  It is used in the
 default values of the variables above.
 @item gnus-article-button-face
 @vindex gnus-article-button-face
-Face used on bottons.
+Face used on buttons.
 @item gnus-article-mouse-face
 @vindex gnus-article-mouse-face
 Face is used when the mouse cursor is over a button.
 @item W T l
 @kindex W T l (Summary)
 @findex gnus-article-date-local
 Display the date in the local timezone (@code{gnus-article-date-local}).
+@item W T s
+@kindex W T s (Summary)
+@vindex gnus-article-time-format
+@findex gnus-article-date-user
+@findex format-time-string
+Display the date using a user-defined format
+(@code{gnus-article-date-user}).  The format is specified by the
+@code{gnus-article-time-format} variable, and is a string that's passed
+to @code{format-time-string}.  See the documentation of that variable
+for a list possible format specs.
 @item W T e
 @kindex W T e (Summary)
 @findex gnus-article-date-lapsed
 Say how much time has (e)lapsed between the article was posted and now
 @emph{totally} impossible.  Don't you trust me? *titter*
 @end table
+@node Article Signature
+@subsection Article Signature
+@cindex signatures
+@cindex article signature
+@vindex gnus-signature-separator
+Each article is divided into two parts---the head and the body.  The
+body can be divided into a signature part and a text part.  The variable
+that says what is to be considered a signature is
+@code{gnus-signature-separator}.  This is normally the standard
+@samp{^-- $} as mandated by son-of-RFC 1036.  However, many people use
+non-standard signature separators, so this variable can also be a list
+of regular expressions to be tested, one by one.  (Searches are done
+from the end of the body towards the beginning.)  One likely value is:
+@lisp
+(setq gnus-signature-separator
+'("^-- $"         ; The standard
+"^-- *$"        ; A common mangling
+"^-------*$"    ; Many people just use a looong
+; line of dashes.  Shame!
+"^ *--------*$" ; Double-shame!
+"^________*$"   ; Underscores are also popular
+"^========*$")) ; Pervert!
+@end lisp
+The more permissive you are, the more likely it is that you'll get false
+positives.
+@vindex gnus-signature-limit
+@code{gnus-signature-limit} provides a limit to what is considered a
+signature.
+@enumerate
+@item
+If it is an integer, no signature may be longer (in characters) than
+that integer.
+@item
+If it is a floating point number, no signature may be longer (in lines)
+than that number.
+@item
+If it is a function, the function will be called without any parameters,
+and if it returns @code{nil}, there is no signature in the buffer.
+@item
+If it is a string, it will be used as a regexp.  If it matches, the text
+in question is not a signature.
+@end enumerate
+This variable can also be a list where the elements may be of the types
+listed above.
+@node Article Commands
+@section Article Commands
+@table @kbd
+@item A P
+@cindex PostScript
+@cindex printing
+@kindex A P (Summary)
+@vindex gnus-ps-print-hook
+@findex gnus-summary-print-article
+Generate and print a PostScript image of the article buffer
+(@code{gnus-summary-print-article}).  @code{gnus-ps-print-hook} will be
+run just before printing the buffer.
+@end table
 @node Summary Sorting
 @section Summary Sorting
 @cindex summary sorting
 You can have the summary buffer sorted in various ways, even though I
 @item C-c C-s C-d
 @kindex C-c C-s C-d (Summary)
 @findex gnus-summary-sort-by-date
 Sort by date (@code{gnus-summary-sort-by-date}).
+@item C-c C-s C-l
+@kindex C-c C-s C-l (Summary)
+@findex gnus-summary-sort-by-lines
+Sort by lines (@code{gnus-summary-sort-by-lines}).
 @item C-c C-s C-i
 @kindex C-c C-s C-i (Summary)
 @findex gnus-summary-sort-by-score
 Sort by score (@code{gnus-summary-sort-by-score}).
 can just press @kbd{^} or @kbd{A r}
 (@code{gnus-summary-refer-parent-article}).  If everything goes well,
 you'll get the parent.  If the parent is already displayed in the
 summary buffer, point will just move to this article.
+If given a positive numerical prefix, fetch that many articles back into
+the ancestry.  If given a negative numerical prefix, fetch just that
+ancestor.  So if you say @kbd{3 ^}, Gnus will fetch the parent, the
+grandparent and the grandgrandparent of the current article.  If you say
+@kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
+article.
 @findex gnus-summary-refer-references
 @kindex A R (Summary)
 You can have Gnus fetch all articles mentioned in the @code{References}
 header of the article by pushing @kbd{A R}
 (@code{gnus-summary-refer-references}).
 @findex gnus-summary-refer-article
 @kindex M-^ (Summary)
+@cindex Message-ID
+@cindex fetching by Message-ID
 You can also ask the @sc{nntp} server for an arbitrary article, no
 matter what group it belongs to.  @kbd{M-^}
 (@code{gnus-summary-refer-article}) will ask you for a
-@code{Message-ID}, which is one of those long thingies that look
+@code{Message-ID}, which is one of those long, hard-to-read thingies
-something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}.  You have to get
+that look something like @samp{<38o6up$6f2@@hymir.ifi.uio.no>}.  You
-it all exactly right.  No fuzzy searches, I'm afraid.
+have to get it all exactly right.  No fuzzy searches, I'm afraid.
 @vindex gnus-refer-article-method
 If the group you are reading is located on a backend that does not
 support fetching by @code{Message-ID} very well (like @code{nnspool}),
 you can set @code{gnus-refer-article-method} to an @sc{nntp} method.  It
 available.
 Here are the available keystrokes when using pick mode:
 @table @kbd
+@item .
+@kindex . (Pick)
+@findex gnus-summary-mark-as-processable
+Pick the article on the current line
+(@code{gnus-summary-mark-as-processable}).  If given a numerical prefix,
+go to the article on that line and pick that article.  (The line number
+is normally displayed on the beginning of the summary pick lines.)
 @item SPACE
 @kindex SPACE (Pick)
-@findex gnus-summary-mark-as-processable
+@findex gnus-pick-next-page
-Pick the article (@code{gnus-summary-mark-as-processable}).
+Scroll the summary buffer up one page (@code{gnus-pick-next-page}).  If
+at the end of the buffer, start reading the picked articles.
 @item u
 @kindex u (Pick)
 @findex gnus-summary-unmark-as-processable
 Unpick the article (@code{gnus-summary-unmark-as-processable}).
 (add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
 @end lisp
 @vindex gnus-pick-mode-hook
 @code{gnus-pick-mode-hook} is run in pick minor mode buffers.
+@vindex gnus-mark-unpicked-articles-as-read
+If @code{gnus-mark-unpicked-articles-as-read} is non-@code{nil}, mark
+all unpicked articles as read.  The default is @code{nil}.
+@vindex gnus-summary-pick-line-format
+The summary line format in pick mode is slightly different than the
+standard format.  At the beginning of each line the line number is
+displayed.  The pick mode line format is controlled by the
+@code{gnus-summary-pick-line-format} variable (@pxref{Formatting
+Variables}).  It accepts the same format specs that
+@code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
 @node Binary Groups
 @subsection Binary Groups
 @cindex binary groups
 Here's and example from a horizontal tree buffer:
 @example
 @{***@}-(***)-[odd]-[Gun]
-|     \[Jan]
+|      \[Jan]
-|     \[odd]-[Eri]
+|      \[odd]-[Eri]
-|     \(***)-[Eri]
+|      \(***)-[Eri]
-|           \[odd]-[Paa]
+|            \[odd]-[Paa]
 \[Bjo]
 \[Gun]
 \[Gun]-[Jor]
 @end example
 (@code{gnus-summary-expire-articles}).
 @item B M-C-e
 @kindex B M-C-e (Summary)
 @findex gnus-summary-expire-articles-now
-Expunge all the expirable articles in the group
+Delete all the expirable articles in the group
 (@code{gnus-summary-expire-articles-now}).  This means that @strong{all}
 articles that are eligible for expiry in the current group will
 disappear forever into that big @file{/dev/null} in the sky.
 @item B DEL
 @item B r
 @kindex B r (Summary)
 @findex gnus-summary-respool-article
 Respool the mail article (@code{gnus-summary-move-article}).
+@code{gnus-summary-respool-default-method} will be used as the default
+select method when respooling.  This variable is @code{nil} by default,
+which means that the current group select method will be used instead.
 @item B w
 @itemx e
 @kindex B w (Summary)
 @kindex e (Summary)
 @kindex B q (Summary)
 @findex gnus-summary-respool-query
 If you want to re-spool an article, you might be curious as to what group
 the article will end up in before you do the re-spooling.  This command
 will tell you (@code{gnus-summary-respool-query}).
+@item B p
+@kindex B p (Summary)
+@findex gnus-summary-article-posted-p
+Some people have a tendency to send you "courtesy" copies when they
+follow up to articles you have posted.  These usually have a
+@code{Newsgroups} header in them, but not always.  This command
+(@code{gnus-summary-article-posted-p}) will try to fetch the current
+article from your news server (or rather, from
+@code{gnus-refer-article-method} or @code{gnus-select-method}) and will
+report back whether it found the article or not.  Even if it says that
+it didn't find the article, it may have been posted anyway---mail
+propagation is much faster than news propagation, and the news copy may
+just not have arrived yet.
 @end table
 @vindex gnus-move-split-methods
 @cindex moving articles
 If you move (or copy) articles regularly, you might wish to have Gnus
 suggest where to put the articles.  @code{gnus-move-split-methods} is a
 variable that uses the same syntax as @code{gnus-split-methods}
 (@pxref{Saving Articles}).  You may customize that variable to create
 suggestions you find reasonable.
+@lisp
+(setq gnus-move-split-methods
+'(("^From:.*Lars Magne" "nnml:junk")
+("^Subject:.*gnus" "nnfolder:important")
+(".*" "nnml:misc")))
+@end lisp
 @node Various Summary Stuff
 @section Various Summary Stuff
 @menu
 * Summary Group Information::         Information oriented commands.
 * Searching for Articles::            Multiple article commands.
+* Summary Generation Commands::       (Re)generating the summary buffer.
 * Really Various Summary Commands::   Those pesky non-conformant commands.
 @end menu
 @table @code
 @vindex gnus-summary-mode-hook
 rereading the description from the server.
 @item H h
 @kindex H h (Summary)
 @findex gnus-summary-describe-briefly
-Give a very brief description of the most important summary keystrokes
+Give an extremely brief description of the most important summary
-(@code{gnus-summary-describe-briefly}).
+keystrokes (@code{gnus-summary-describe-briefly}).
 @item H i
 @kindex H i (Summary)
 @findex gnus-info-find-node
 Go to the Gnus info node (@code{gnus-info-find-node}).
 @findex gnus-summary-universal-argument
 Perform any operation on all articles that have been marked with
 the process mark (@code{gnus-summary-universal-argument}).
 @end table
+@node Summary Generation Commands
+@subsection Summary Generation Commands
+@table @kbd
+@item Y g
+@kindex Y g (Summary)
+@findex gnus-summary-prepare
+Regenerate the current summary buffer (@code{gnus-summary-prepare}).
+@item Y c
+@kindex Y c (Summary)
+@findex gnus-summary-insert-cached-articles
+Pull all cached articles (for the current group) into the summary buffer
+(@code{gnus-summary-insert-cached-articles}).
+@end table
 @node Really Various Summary Commands
 @subsection Really Various Summary Commands
 @table @kbd
-@item A D
+@item C-d
-@kindex A D (Summary)
+@kindex C-d (Summary)
 @findex gnus-summary-enter-digest-group
 If the current article is a collection of other articles (for instance,
 a digest), you might use this command to enter a group based on the that
 article (@code{gnus-summary-enter-digest-group}).  Gnus will try to
 guess what article type is currently displayed unless you give a prefix
 to this command, which forces a ``digest'' interpretation.  Basically,
 whenever you see a message that is a collection of other messages on
-some format, you @kbd{A D} and read these messages in a more convenient
+some format, you @kbd{C-d} and read these messages in a more convenient
 fashion.
+@item M-C-d
+@kindex M-C-d (Summary)
+@findex gnus-summary-read-document
+This command is very similar to the one above, but lets you gather
+several documents into one biiig group
+(@code{gnus-summary-read-document}).  It does this by opening several
+@code{nndoc} groups for each document, and then opening an
+@code{nnvirtual} group on top of these @code{nndoc} groups.  This
+command understands the process/prefix convention
+(@pxref{Process/Prefix}).
 @item C-t
 @kindex C-t (Summary)
 @findex gnus-summary-toggle-truncation
-Toggle truncation of summary lines (@code{gnus-summary-toggle-truncation}).
+Toggle truncation of summary lines
+(@code{gnus-summary-toggle-truncation}).  This will probably confuse the
+line centering function in the summary buffer, so it's not a good idea
+to have truncation switched off while reading articles.
 @item =
 @kindex = (Summary)
 @findex gnus-summary-expand-window
 Expand the summary buffer window (@code{gnus-summary-expand-window}).
 If given a prefix, force an @code{article} window configuration.
 @end table
 @node Exiting the Summary Buffer
 @section Exiting the Summary Buffer
 Exit the current group and update all information on the group
 (@code{gnus-summary-exit}). @code{gnus-summary-prepare-exit-hook} is
 called before doing much of the exiting, and calls
 @code{gnus-summary-expire-articles} by default.
 @code{gnus-summary-exit-hook} is called after finishing the exiting
-process.
+process.  @code{gnus-group-no-more-groups-hook} is run when returning to
+group mode having no more (unread) groups.
 @item Z E
 @itemx Q
 @kindex Z E (Summary)
 @kindex Q (Summary)
 @item Z P
 @kindex Z P (Summary)
 @findex gnus-summary-prev-group
 Exit the group and go to the previous group
 (@code{gnus-summary-prev-group}).
+@item Z s
+@kindex Z s (Summary)
+@findex gnus-summary-save-newsrc
+Save the current number of read/marked articles in the dribble buffer
+and then save the dribble buffer (@code{gnus-summary-save-newsrc}).  If
+given a prefix, also save the @file{.newsrc} file(s).  Using this
+command will make exit without updating (the @kbd{Q} command) worthless.
 @end table
 @vindex gnus-exit-group-hook
 @code{gnus-exit-group-hook} is called when you exit the current
 group.
 summary buffer.  If the @code{gnus-use-cross-reference} variable is
 @code{t} (which is the default), articles that are cross-referenced to
 this group and are marked as read, will also be marked as read in the
 other subscribed groups they were cross-posted to.  If this variable is
 neither @code{nil} nor @code{t}, the article will be marked as read in
-both subscribed and unsubscribed groups.
+both subscribed and unsubscribed groups (@pxref{Crosspost Handling}).
+@node Crosspost Handling
+@section Crosspost Handling
 @cindex velveeta
 @cindex spamming
 Marking cross-posted articles as read ensures that you'll never have to
 read the same article more than once.  Unless, of course, somebody has
 posted it to several groups separately.  Posting the same article to
 several groups (not cross-posting) is called @dfn{spamming}, and you are
 by law required to send nasty-grams to anyone who perpetrates such a
-heinous crime.
+heinous crime.  You may want to try NoCeM handling to filter out spam
+(@pxref{NoCeM}).
 Remember: Cross-posting is kinda ok, but posting the same article
 separately to several groups is not.  Massive cross-posting (aka.
-@dfn{velveeta}) is to be avoided.
+@dfn{velveeta}) is to be avoided at all costs, and you can even use the
+@code{gnus-summary-mail-crosspost-complaint} command to complain about
+excessive crossposting (@pxref{Summary Mail Commands}).
 @cindex cross-posting
 @cindex Xref
 @cindex @sc{nov}
 One thing that may cause Gnus to not do the cross-posting thing
 set @code{gnus-nov-is-evil} to @code{t}, which slows things down
 considerably.
 C'est la vie.
+For an alternative approach, @pxref{Duplicate Suppression}.
+@node Duplicate Suppression
+@section Duplicate Suppression
+By default, Gnus tries to make sure that you don't have to read the same
+article more than once by utilizing the crossposting mechanism
+(@pxref{Crosspost Handling}).  However, that simple and efficient
+approach may not work satisfactorily for some users for various
+reasons.
+@enumerate
+@item
+The @sc{nntp} server may fail to generate the @code{Xref} header.  This
+is evil and not very common.
+@item
+The @sc{nntp} server may fail to include the @code{Xref} header in the
+@file{.overview} data bases.  This is evil and all too common, alas.
+@item
+You may be reading the same group (or several related groups) from
+different @sc{nntp} servers.
+@item
+You may be getting mail that duplicates articles posted to groups.
+@end enumerate
+I'm sure there are other situations that @code{Xref} handling fails as
+well, but these four are the most common situations.
+If, and only if, @code{Xref} handling fails for you, then you may
+consider switching on @dfn{duplicate suppression}.  If you do so, Gnus
+will remember the @code{Message-ID}s of all articles you have read or
+otherwise marked as read, and then, as if by magic, mark them as read
+all subsequent times you see them---in @emph{all} groups.  Using this
+mechanism is quite likely to be somewhat inefficient, but not overly
+so.  It's certainly preferable to reading the same articles more than
+once.
+Duplicate suppression is not a very subtle instrument.  It's more like a
+sledge hammer than anything else.  It works in a very simple
+fashion---if you have marked an article as read, it adds this Message-ID
+to a cache.  The next time it sees this Message-ID, it will mark the
+article as read the the @samp{M} mark.  It doesn't care what group it
+saw the article in.
+@table @code
+@item gnus-suppress-duplicates
+@vindex gnus-suppress-duplicates
+If non-@code{nil}, suppress duplicates.
+@item gnus-save-duplicate-list
+@vindex gnus-save-duplicate-list
+If non-@code{nil}, save the list of duplicates to a file.  This will
+make startup and shutdown take longer, so the default is @code{nil}.
+However, this means that only duplicate articles that is read in a
+single Gnus session are suppressed.
+@item gnus-duplicate-list-length
+@vindex gnus-duplicate-list-length
+This variables says how many @code{Message-ID}s to keep in the duplicate
+suppression list.  The default is 10000.
+@item gnus-duplicate-file
+@vindex gnus-duplicate-file
+The name of the file to store the duplicate suppression list.  The
+default is @file{~/News/suppression}.
+@end table
+If you have a tendency to stop and start Gnus often, setting
+@code{gnus-save-duplicate-list} to @code{t} is probably a good idea.  If
+you leave Gnus running for weeks on end, you may have it @code{nil}.  On
+the other hand, saving the list makes startup and shutdown much slower,
+so that means that if you stop and start Gnus often, you should set
+@code{gnus-save-duplicate-list} to @code{nil}.  Uhm.  I'll leave this up
+to you to figure out, I think.
 @node The Article Buffer
 @chapter The Article Buffer
 @cindex article buffer
 @menu
 * Hiding Headers::        Deciding what headers should be displayed.
 * Using MIME::            Pushing articles through @sc{mime} before reading them.
 * Customizing Articles::  Tailoring the look of the articles.
-* Article Keymap::        Keystrokes available in the article buffer
+* Article Keymap::        Keystrokes available in the article buffer.
 * Misc Article::          Other stuff.
 @end menu
 @node Hiding Headers
 @vindex gnus-show-mime
 @vindex gnus-show-mime-method
 @vindex gnus-strict-mime
 @findex metamail-buffer
-Gnus handles @sc{mime} by shoving the articles through
+Gnus handles @sc{mime} by pushing the articles through
 @code{gnus-show-mime-method}, which is @code{metamail-buffer} by
 default.  Set @code{gnus-show-mime} to @code{t} if you want to use
 @sc{mime} all the time.  However, if @code{gnus-strict-mime} is
 non-@code{nil}, the @sc{mime} method will only be used if there are
-@sc{mime} headers in the article.
+@sc{mime} headers in the article.  If you have @code{gnus-show-mime}
+set, then you'll see some unfortunate display glitches in the article
+buffer.  These can't be avoided.
 It might be best to just use the toggling functions from the summary
 buffer to avoid getting nasty surprises. (For instance, you enter the
 group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
 decoded the sound file in the article and some horrible sing-a-long song
 The @code{gnus-article-display-hook} is called after the article has
 been inserted into the article buffer.  It is meant to handle all
 treatment of the article before it is displayed.
 @findex gnus-article-maybe-highlight
-By default it contains @code{gnus-article-hide-headers},
+By default this hook just contains @code{gnus-article-hide-headers},
 @code{gnus-article-treat-overstrike}, and
 @code{gnus-article-maybe-highlight}, but there are thousands, nay
 millions, of functions you can put in this hook.  For an overview of
 functions @pxref{Article Highlighting}, @pxref{Article Hiding},
 @pxref{Article Washing}, @pxref{Article Buttons} and @pxref{Article
-Date}.
+Date}.  Note that the order of functions in this hook might affect
+things, so you may have to fiddle a bit to get the desired results.
 You can, of course, write your own functions.  The functions are called
 from the article buffer, and you can do anything you like, pretty much.
 There is no information that you have to keep in the buffer---you can
 change everything.  However, you shouldn't delete any headers.  Instead
 @item gnus-article-mode-hook
 @vindex gnus-article-mode-hook
 Hook called in article mode buffers.
+@item gnus-article-mode-syntax-table
+@vindex gnus-article-mode-syntax-table
+Syntax table used in article buffers.  It is initialized from
+@code{text-mode-syntax-table}.
 @vindex gnus-article-mode-line-format
 @item gnus-article-mode-line-format
 This variable is a format string along the same lines as
-@code{gnus-summary-mode-line-format}.  It accepts exactly the same
+@code{gnus-summary-mode-line-format}.  It accepts the same
-format specifications as that variable.
+format specifications as that variable, with one extension:
+@table @samp
+@item w
+The @dfn{wash status} of the article.  This is a short string with one
+character for each possible article wash operation that may have been
+performed.
+@end table
 @vindex gnus-break-pages
 @item gnus-break-pages
 Controls whether @dfn{page breaking} is to take place.  If this variable
 is non-@code{nil}, the articles will be divided into pages whenever a
 Now, if you've done this, and then this server rejects your article, or
 this server is down, what do you do then?  To override this variable you
 can use a non-zero prefix to the @kbd{C-c C-c} command to force using
 the ``current'' server for posting.
-If you give a zero prefix (i. e., @kbd{C-u 0 C-c C-c}) to that command,
+If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
 Gnus will prompt you for what method to use for posting.
 You can also set @code{gnus-post-method} to a list of select methods.
 If that's the case, Gnus will always prompt you for what method to use
 for posting.
 @cindex archived messages
 @cindex sent messages
 Gnus provides a few different methods for storing the mail you send.
 The default method is to use the @dfn{archive virtual server} to store
-the mail.  If you want to disable this completely, you should set
+the mail.  If you want to disable this completely, the
-@code{gnus-message-archive-group} to @code{nil}.
+@code{gnus-message-archive-group} variable should be @code{nil}, which
+is the default.
 @vindex gnus-message-archive-method
 @code{gnus-message-archive-method} says what virtual server Gnus is to
-use to store sent messages.  It is @code{(nnfolder "archive"
+use to store sent messages.  The default is:
-(nnfolder-directory "~/Mail/archive/"))} by default, but you can use any
-mail select method (@code{nnml}, @code{nnmbox}, etc.).  However,
+@lisp
-@code{nnfolder} is a quite likeable select method for doing this sort of
+(nnfolder "archive"
-thing.  If you don't like the default directory chosen, you could say
+(nnfolder-directory "~/Mail/archive/"))
-something like:
+@end lisp
+You can, however, use any mail select method (@code{nnml},
+@code{nnmbox}, etc.).  @code{nnfolder} is a quite likeable select method
+for doing this sort of thing, though.  If you don't like the default
+directory chosen, you could say something like:
 @lisp
 (setq gnus-message-archive-method
 '(nnfolder "archive"
 (nnfolder-inhibit-expiry t)
 group.  If the group gets really big and annoying, you can simply rename
 if (using @kbd{G r} in the group buffer) to something
 nice---@samp{misc-mail-september-1995}, or whatever.  New messages will
 continue to be stored in the old (now empty) group.
-That's the default method of archiving sent mail.  Gnus also offers two
+That's the default method of archiving sent mail.  Gnus also a different
-other variables for the people who don't like the default method.  In
+way for the people who don't like the default method.  In that case you
-that case you should set @code{gnus-message-archive-group} to
+should set @code{gnus-message-archive-group} to @code{nil}; this will
-@code{nil}; this will disable archiving.
+disable archiving.
 XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
 use a different value for @code{gnus-message-archive-group} there.
 @table @code
 @item gnus-outgoing-message-group
 @vindex gnus-outgoing-message-group
 All outgoing messages will be put in this group.  If you want to store
 @sc{nntp} server, it could be a virtual group, or it could be your own
 personal mail group.
 A foreign group (or any group, really) is specified by a @dfn{name} and
 a @dfn{select method}.  To take the latter first, a select method is a
-list where the first element says what backend to use (eg. @code{nntp},
+list where the first element says what backend to use (e.g. @code{nntp},
 @code{nnspool}, @code{nnml}) and the second element is the @dfn{server
 name}.  There may be additional elements in the select method, where the
 value may have special meaning for the backend in question.
 One could say that a select method defines a @dfn{virtual server}---so
 The @dfn{name} of the group is the name the backend will recognize the
 group as.
 For instance, the group @samp{soc.motss} on the @sc{nntp} server
 @samp{some.where.edu} will have the name @samp{soc.motss} and select
-method @code{(nntp "some.where.edu")}.  Gnus will call this group, in
+method @code{(nntp "some.where.edu")}.  Gnus will call this group
-all circumstances, @samp{nntp+some.where.edu:soc.motss}, even though the
+@samp{nntp+some.where.edu:soc.motss}, even though the @code{nntp}
-@code{nntp} backend just knows this group as @samp{soc.motss}.
+backend just knows this group as @samp{soc.motss}.
 The different methods all have their peculiarities, of course.
 @menu
 * The Server Buffer::     Making and editing virtual servers.
 on the same actual @sc{nntp} server.  You tell Gnus which backend to
 use, and what parameters to set by specifying a @dfn{select method}.
 These select methods specifications can sometimes become quite
 complicated---say, for instance, that you want to read from the
-@sc{nntp} server @samp{news.funet.fi} on port number @code{13}, which
+@sc{nntp} server @samp{news.funet.fi} on port number 13, which
 hangs if queried for @sc{nov} headers and has a buggy select.  Ahem.
 Anyways, if you had to specify that for each group that used this
 server, that would be too much work, so Gnus offers a way of naming
 select methods, which is what you do in the server buffer.
 @item l
 @kindex l (Server)
 @findex gnus-server-list-servers
 List all servers (@code{gnus-server-list-servers}).
+@item s
+@kindex s (Server)
+@findex gnus-server-scan-server
+Request that the server scan its sources for new articles
+(@code{gnus-server-scan-server}).  This is mainly sensible with mail
+servers.
+@item g
+@kindex g (Server)
+@findex gnus-server-regenerate-server
+Request that the server regenerate all its data structures
+(@code{gnus-server-regenerate-server}).  This can be useful if you have
+a mail backend that has gotten out of synch.
 @end table
 @node Example Methods
 @subsection Example Methods
 After these two elements, there may be a arbitrary number of
 @var{(variable form)} pairs.
 To go back to the first example---imagine that you want to read from
-port @code{15} from that machine.  This is what the select method should
+port 15 from that machine.  This is what the select method should
 look like then:
 @lisp
 (nntp "news.funet.fi" (nntp-port-number 15))
 @end lisp
 (nnmh "public"
 (nnmh-directory "/usr/information/spool/")
 (nnmh-get-new-mail nil))
 @end lisp
+If you are behind a firewall and only have access to the @sc{nntp}
+server from the firewall machine, you can instruct Gnus to @code{rlogin}
+on the firewall machine and telnet from there to the @sc{nntp} server.
+Doing this can be rather fiddly, but your virtual server definition
+should probably look something like this:
+@lisp
+(nntp "firewall"
+(nntp-address "the.firewall.machine")
+(nntp-open-connection-function nntp-open-rlogin)
+(nntp-end-of-line "\n")
+(nntp-rlogin-parameters
+("telnet" "the.real.nntp.host" "nntp")))
+@end lisp
 @node Creating a Virtual Server
 @subsection Creating a Virtual Server
 If you're saving lots of articles in the cache by using persistent
 Change that to:
 @lisp
 (nnspool "cache"
-	 (nnspool-spool-directory "~/News/cache/")
+(nnspool-spool-directory "~/News/cache/")
-	 (nnspool-nov-directory "~/News/cache/")
+(nnspool-nov-directory "~/News/cache/")
-	 (nnspool-active-file "~/News/cache/active"))
+(nnspool-active-file "~/News/cache/active"))
 @end lisp
 Type @kbd{C-c C-c} to return to the server buffer.  If you now press
 @kbd{RET} over this virtual server, you should be entered into a browse
 buffer, and you should be able to enter any of the groups displayed.
 @node Servers and Methods
 @subsection Servers and Methods
 Wherever you would normally use a select method
-(eg. @code{gnus-secondary-select-method}, in the group select method,
+(e.g. @code{gnus-secondary-select-method}, in the group select method,
 when browsing a foreign server) you can use a virtual server name
 instead.  This could potentially save lots of typing.  And it's nice all
 over.
 @item D
 @kindex D (Server)
 @findex gnus-server-deny-server
 Mark the current server as unreachable
 (@code{gnus-server-deny-server}).
+@item M-o
+@kindex M-o (Server)
+@findex gnus-server-open-all-servers
+Open the connections to all servers in the buffer
+(@code{gnus-server-open-all-servers}).
+@item M-c
+@kindex M-c (Server)
+@findex gnus-server-close-all-servers
+Close the connections to all servers in the buffer
+(@code{gnus-server-close-all-servers}).
 @item R
 @kindex R (Server)
 @findex gnus-server-remove-denials
 Remove all marks to whether Gnus was denied connection from all servers
 @findex nntp-send-authinfo
 @findex nntp-send-mode-reader
 @code{nntp-server-opened-hook} is run after a connection has been made.
 It can be used to send commands to the @sc{nntp} server after it has
 been contacted.  By default is sends the command @code{MODE READER} to
-the server with the @code{nntp-send-mode-reader} function.  Another
+the server with the @code{nntp-send-mode-reader} function.
-popular function is @code{nntp-send-authinfo}, which will prompt you for
-an @sc{nntp} password and stuff.
+@item nntp-authinfo-function
+@vindex nntp-authinfo-function
+This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
+server.  Available functions include:
+@table @code
+@item nntp-send-authinfo
+@findex nntp-send-authinfo
+This function will used you current login name as the user name and will
+prompt you for the password.  This is the default.
+@item nntp-send-nosy-authinfo
+@findex nntp-send-nosy-authinfo
+This function will prompt you for both user name and password.
+@item nntp-send-authinfo-from-file
+@findex nntp-send-authinfo-from-file
+This function will use your current login name as the user name and will
+read the @sc{nntp} password from @file{~/.nntp-authinfo}.
+@end table
 @item nntp-server-action-alist
 @vindex nntp-server-action-alist
 This is an list of regexps to match on server types and actions to be
 taken when matches are made.  For instance, if you want Gnus to beep
 This hook is run as the last step when connecting to an @sc{nntp}
 server.
 @findex nntp-open-rlogin
 @findex nntp-open-network-stream
-@item nntp-open-server-function
+@item nntp-open-connection-function
-@vindex nntp-open-server-function
+@vindex nntp-open-connection-function
 This function is used to connect to the remote system.  Two pre-made
 functions are @code{nntp-open-network-stream}, which is the default, and
 simply connects to some port or other on the remote system.  The other
 is @code{nntp-open-rlogin}, which does an rlogin on the remote system,
 and then does a telnet to the @sc{nntp} server available there.
 @item nntp-rlogin-parameters
 @vindex nntp-rlogin-parameters
 If you use @code{nntp-open-rlogin} as the
-@code{nntp-open-server-function}, this list will be used as the
+@code{nntp-open-connection-function}, this list will be used as the
 parameter list given to @code{rsh}.
 @item nntp-end-of-line
 @vindex nntp-end-of-line
 String to use as end-of-line markers when talking to the @sc{nntp}
 @item nntp-prepare-server-hook
 @vindex nntp-prepare-server-hook
 A hook run before attempting to connect to an @sc{nntp} server.
-@item nntp-async-number
-@vindex nntp-async-number
-How many articles should be pre-fetched when in asynchronous mode.  If
-this variable is @code{t}, @code{nntp} will pre-fetch all the articles
-that it can without bound.  If it is @code{nil}, no pre-fetching will be
-made.
 @item nntp-warn-about-losing-connection
 @vindex nntp-warn-about-losing-connection
 If this variable is non-@code{nil}, some noise will be made when a
 server closes connection.
 @subsection News Spool
 @cindex nnspool
 @cindex news spool
 Subscribing to a foreign group from the local spool is extremely easy,
-and might be useful, for instance, to speed up reading groups like
+and might be useful, for instance, to speed up reading groups that
-@samp{alt.binaries.pictures.furniture}.
+contain very big articles---@samp{alt.binaries.pictures.furniture}, for
+instance.
 Anyways, you just specify @code{nnspool} as the method and @samp{} (or
 anything else) as the address.
 If you have access to a local spool, you should probably use that as the
 * Mail Backend Variables::       Variables for customizing mail handling.
 * Fancy Mail Splitting::         Gnus can do hairy splitting of incoming mail.
 * Mail and Procmail::            Reading mail groups that procmail create.
 * Incorporating Old Mail::       What about the old mail you have?
 * Expiring Mail::                Getting rid of unwanted mail.
+* Washing Mail::                 Removing gruft from the mail you get.
 * Duplicates::                   Dealing with duplicated mail.
 * Not Reading Mail::             Using mail backends for reading other files.
 * Choosing a Mail Backend::      Gnus can read a variety of mail formats.
 @end menu
 You will probably want to split the mail into several groups, though:
 @lisp
 (setq nnmail-split-methods
 '(("junk" "^From:.*Lars Ingebrigtsen")
 ("crazy" "^Subject:.*die\\|^Organization:.*flabby")
 ("other" "")))
 @end lisp
-This will result in three new mail groups being created:
+This will result in three new @code{nnml} mail groups being created:
 @samp{nnml:junk}, @samp{nnml:crazy}, and @samp{nnml:other}.  All the
 mail that doesn't fit into the first two groups will be placed in the
 latter group.
 This should be sufficient for reading mail with Gnus.  You might want to
 these lists is the name of the mail group (they do not have to be called
 something beginning with @samp{mail}, by the way), and the second
 element is a regular expression used on the header of each mail to
 determine if it belongs in this mail group.
+If the first element is the special symbol @code{junk}, then messages
+that match the regexp will disappear into the aether.  Use with
+extreme caution.
 The second element can also be a function.  In that case, it will be
 called narrowed to the headers with the first element of the rule as the
 argument.  It should return a non-@code{nil} value if it thinks that the
 mail belongs in that group.
 The last of these groups should always be a general one, and the regular
-expression should @emph{always} be @samp{} so that it matches any
+expression should @emph{always} be @samp{} so that it matches any mails
-mails that haven't been matched by any of the other regexps.
+that haven't been matched by any of the other regexps.  (These rules are
+processed from the beginning of the alist toward the end.  The first
+rule to make a match will "win", unless you have crossposting enabled.
+In that case, all matching rules will "win".)
 If you like to tinker with this yourself, you can set this variable to a
 function of your choice.  This function will be called without any
 arguments in a buffer narrowed to the headers of an incoming mail
 message.  The function should return a list of groups names that it
 @code{nnmh} and @code{nnml} makes crossposts by creating hard links to
 the crossposted articles.  However, not all files systems support hard
 links.  If that's the case for you, set
 @code{nnmail-crosspost-link-function} to @code{copy-file}.  (This
 variable is @code{add-name-to-file} by default.)
+@kindex M-x nnmail-split-history
+@kindex nnmail-split-history
+If you wish to see where the previous mail split put the messages, you
+can use the @kbd{M-x nnmail-split-history} command.
 Gnus gives you all the opportunity you could possibly want for shooting
 yourself in the foot.  Let's say you create a group that will contain
 all the mail you get from your boss.  And then you accidentally
 unsubscribe from the group.  Gnus will still put all the mail from your
 @code{MAILHOST} environment variable.  If the POP server needs a
 password, you can either set @code{nnmail-pop-password-required} to
 @code{t} and be prompted for the password, or set
 @code{nnmail-pop-password} to the password itself.
+@code{nnmail-spool-file} can also be a list of mailboxes.
+Your Emacs has to have been configured with @samp{--with-pop} before
+compilation.  This is the default, but some installations have it
+switched off.
 When you use a mail backend, Gnus will slurp all your mail from your
 inbox and plonk it down in your home directory.  Gnus doesn't move any
 mail if you're not using a mail backend---you have to do a lot of magic
 invocations first.  At the time when you have finished drawing the
 pentagram, lightened the candles, and sacrificed the goat, you really
 @vindex nnmail-prepare-incoming-hook
 @item nnmail-prepare-incoming-hook
 This is run in a buffer that holds all the new incoming mail, and can be
 used for, well, anything, really.
+@vindex nnmail-split-hook
+@item nnmail-split-hook
+@findex article-decode-rfc1522
+@findex RFC1522 decoding
+Hook run in the buffer where the mail headers of each message is kept
+just before the splitting based on these headers is done.  The hook is
+free to modify the buffer contents in any way it sees fit---the buffer
+is discarded after the splitting has been done, and no changes performed
+in the buffer will show up in any files.  @code{gnus-article-decode-rfc1522}
+is one likely function to add to this hook.
 @vindex nnmail-pre-get-new-mail-hook
 @vindex nnmail-post-get-new-mail-hook
 @item nnmail-pre-get-new-mail-hook
 @itemx nnmail-post-get-new-mail-hook
 @item nnmail-movemail-program
 @vindex nnmail-movemail-program
 This program is executed to move mail from the user's inbox to her home
 directory.  The default is @samp{movemail}.
+This can also be a function.  In that case, the function will be called
+with two parameters -- the name of the inbox, and the file to be moved
+to.
 @item nnmail-delete-incoming
 @vindex nnmail-delete-incoming
 @cindex incoming mail files
 @cindex deleting incoming files
 If non-@code{nil}, the mail backends will delete the temporary incoming
 file after splitting mail into the proper groups.  This is @code{nil} by
 default for reasons of security.
+@c Since Red Gnus is an alpha release, it is to be expected to lose mail.
+(No Gnus release since (ding) Gnus 0.10 (or something like that) have
+lost mail, I think, but that's not the point.  (Except certain versions
+of Red Gnus.))  By not deleting the Incoming* files, one can be sure to
+not lose mail -- if Gnus totally whacks out, one can always recover what
+was lost.
+Delete the @file{Incoming*} files at will.
 @item nnmail-use-long-file-names
 @vindex nnmail-use-long-file-names
 If non-@code{nil}, the mail backends will use long file and directory
 names.  Groups like @samp{mail.misc} will end up in directories like
 @file{mail.misc/}.  If it is @code{nil}, the same group will end up in
 @vindex nnmail-split-fancy
 @findex nnmail-split-fancy
 If the rather simple, standard method for specifying how to split mail
 doesn't allow you to do what you want, you can set
 @code{nnmail-split-methods} to @code{nnmail-split-fancy}.  Then you can
 play with the @code{nnmail-split-fancy} variable.
 Let's look at an example value of this variable first:
 @lisp
 ;; Messages from the mailer daemon are not crossposted to any of
 (any "procmail@@informatik\\.rwth-aachen\\.de" "procmail.list")
 (any "SmartList@@informatik\\.rwth-aachen\\.de" "SmartList.list")
 ;; People...
 (any "larsi@@ifi\\.uio\\.no" "people.Lars Magne Ingebrigtsen"))
 ;; Unmatched mail goes to the catch all group.
-"misc.misc"))")
+"misc.misc")
 @end lisp
 This variable has the format of a @dfn{split}.  A split is a (possibly)
 recursive structure where each split may contain other splits.  Here are
-the four possible split syntaxes:
+the five possible split syntaxes:
-@table @dfn
+@enumerate
-@item GROUP
+@item
-If the split is a string, that will be taken as a group name.
+@samp{group}: If the split is a string, that will be taken as a group name.
-@item (FIELD VALUE SPLIT)
+@item
-If the split is a list, and the first element is a string, then that
+@var{(FIELD VALUE SPLIT)}: If the split is a list, and the first
-means that if header FIELD (a regexp) contains VALUE (also a regexp),
+element is a string, then that means that if header FIELD (a regexp)
-then store the message as specified by SPLIT.
+contains VALUE (also a regexp), then store the message as specified by
+SPLIT.
-@item (| SPLIT...)
-If the split is a list, and the first element is @code{|} (vertical
+@item
-bar), then process each SPLIT until one of them matches.  A SPLIT is
+@var{(| SPLIT...)}: If the split is a list, and the first element is
-said to match if it will cause the mail message to be stored in one or
+@code{|} (vertical bar), then process each SPLIT until one of them
-more groups.
+matches.  A SPLIT is said to match if it will cause the mail message to
+be stored in one or more groups.
-@item (& SPLIT...)
-If the split is a list, and the first element is @code{&}, then process
+@item
-all SPLITs in the list.
+@var{(& SPLIT...)}: If the split is a list, and the first element is
-@end table
+@code{&}, then process all SPLITs in the list.
-In these splits, FIELD must match a complete field name.  VALUE must
+@item
-match a complete word according to the fundamental mode syntax table.
+@code{junk}: If the split is the symbol @code{junk}, then don't save
-You can use @code{.*} in the regexps to match partial field names or
+this message anywhere.
-words.
+@item
+@var{(: function arg1 arg2 ...)}:  If the split is a list, and the first
+element is @code{:}, then the second element will be called as a
+function with @var{args} given as arguments.  The function should return
+a SPLIT.
+@end enumerate
+In these splits, @var{FIELD} must match a complete field name.
+@var{VALUE} must match a complete word according to the fundamental mode
+syntax table.  You can use @code{.*} in the regexps to match partial
+field names or words.  In other words, all @var{VALUE}'s are wrapped in
+@samp{\<} and @samp{\>} pairs.
 @vindex nnmail-split-abbrev-alist
-FIELD and VALUE can also be lisp symbols, in that case they are expanded
+@var{FIELD} and @var{VALUE} can also be lisp symbols, in that case they
-as specified by the variable @code{nnmail-split-abbrev-alist}.  This is
+are expanded as specified by the variable
-an alist of cons cells, where the car of the cells contains the key, and
+@code{nnmail-split-abbrev-alist}.  This is an alist of cons cells, where
-the cdr contains a string.
+the car of the cells contains the key, and the cdr contains a string.
 @vindex nnmail-split-fancy-syntax-table
 @code{nnmail-split-fancy-syntax-table} is the syntax table in effect
 when all this splitting is performed.
+If you want to have Gnus create groups dynamically based on some
+information in the headers, you can say things like:
+@example
+(any "debian-\(\\w*\\)@@lists.debian.org" "mail.debian.\\1")
+@end example
+That is, do @code{replace-match}-like substitions in the group names.
 @node Mail and Procmail
 @subsection Mail and Procmail
 @cindex procmail
 directory (which you shouldn't do), you should set
 @code{nnmail-keep-last-article} to non-@code{nil} to prevent Gnus from
 ever expiring the final article in a mail newsgroup.  This is quite,
 quite important.
+Here's an example setup:  The incoming spools are located in
+@file{~/incoming/} and have @samp{""} as suffixes (i. e., the incoming
+spool files have the same names as the equivalent groups).  The
+@code{nnfolder} backend is to be used as the mail interface, and the
+@code{nnfolder} directory is @file{~/fMail/}.
+@lisp
+(setq nnfolder-directory "~/fMail/")
+(setq nnmail-spool-file 'procmail)
+(setq nnmail-procmail-directory "~/incoming/")
+(setq gnus-secondary-select-methods '((nnfolder "")))
+(setq nnmail-procmail-suffix "")
+@end lisp
 @node Incorporating Old Mail
 @subsection Incorporating Old Mail
 Most people have lots of old mail stored in various file formats.  If
 match the regular expression @code{gnus-auto-expirable-newsgroups} will
 have all articles that you read marked as expirable automatically.  All
 articles that are marked as expirable have an @samp{E} in the first
 column in the summary buffer.
+Note that making a group auto-expirable don't mean that all read
+articles are expired---only the articles that are marked as expirable
+will be expired.  Also note the using the @kbd{d} command won't make
+groups expirable---only semi-automatic marking of articles as read will
+mark the articles as expirable in auto-expirable groups.
 Let's say you subscribe to a couple of mailing lists, and you want the
 articles you have read to disappear after a while:
 @lisp
 (setq gnus-auto-expirable-newsgroups
 "mail.nonsense-list\\|mail.nice-list")
 @end lisp
 Another way to have auto-expiry happen is to have the element
 @code{auto-expire} in the group parameters of the group.
+If you use adaptive scoring (@pxref{Adaptive Scoring}) and
+auto-expiring, you'll have problems.  Auto-expiring and adaptive scoring
+doesn't really mix very well.
 @vindex nnmail-expiry-wait
 The @code{nnmail-expiry-wait} variable supplies the default time an
 expirable article has to live.  The default is seven days.
 crying to me when you discover that the regexp you used matched the
 wrong group and all your important mail has disappeared.  Be a
 @emph{man}!  Or a @emph{woman}!  Whatever you feel more comfortable
 with!  So there!
+Most people make most of their mail groups total-expirable, though.
+@node Washing Mail
+@subsection Washing Mail
+@cindex mail washing
+@cindex list server brain damage
+@cindex incoming mail treatment
+Mailers and list servers are notorious for doing all sorts of really,
+really stupid things with mail.  ``Hey, RFC822 doesn't explicitly
+prohibit us from adding the string @code{wE aRe ElItE!!!!!1!!} to the
+end of all lines passing through our server, so let's do that!!!!1!''
+Yes, but RFC822 wasn't designed to be read by morons.  Things that were
+considered to be self-evident were not discussed.  So.  Here we are.
+Case in point:  The German version of Microsoft Exchange adds @samp{AW:
+} to the subjects of replies instead of @samp{Re: }.  I could pretend to
+be shocked and dismayed by this, but I haven't got the energy.  It is to
+laugh.
+Gnus provides a plethora of functions for washing articles while
+displaying them, but it might be nicer to do the filtering before
+storing the mail to disc.  For that purpose, we have three hooks and
+various functions that can be put in these hooks.
+@table @code
+@item nnmail-prepare-incoming-hook
+@vindex nnmail-prepare-incoming-hook
+This hook is called before doing anything with the mail and is meant for
+grand, sweeping gestures.  Functions to be used include:
+@table @code
+@item nnheader-ms-strip-cr
+@findex nnheader-ms-strip-cr
+Remove trailing carriage returns from each line.  This is default on
+Emacs running on MS machines.
+@end table
+@item nnmail-prepare-incoming-header-hook
+@vindex nnmail-prepare-incoming-header-hook
+This hook is called narrowed to each header.  It can be used when
+cleaning up the headers.  Functions that can be used include:
+@table @code
+@item nnmail-remove-leading-whitespace
+@findex nnmail-remove-leading-whitespace
+Clear leading white space that ``helpful'' listservs have added to the
+headers too make them look nice.  Aaah.
+@item nnmail-remove-list-identifiers
+@findex nnmail-remove-list-identifiers
+Some list servers add an identifier---for example, @samp{(idm)}---to the
+beginning of all @code{Subject} headers.  I'm sure that's nice for
+people who use stone age mail readers.  This function will remove
+strings that match the @code{nnmail-list-identifiers} regexp, which can
+also be a list of regexp.
+For instance, if you want to remove the @samp{(idm)} and the
+@samp{nagnagnag} identifiers:
+@lisp
+(setq nnmail-list-identifiers
+'("(idm)" "nagnagnag"))
+@end lisp
+@item nnmail-remove-tabs
+@findex nnmail-remove-tabs
+Translate all @samp{TAB} characters into @samp{SPACE} characters.
+@end table
+@item nnmail-prepare-incoming-message-hook
+@vindex nnmail-prepare-incoming-message-hook
+This hook is called narrowed to each message.  Functions to be used
+include:
+@table @code
+@item article-de-quoted-unreadable
+@findex article-de-quoted-unreadable
+Decode Quoted Readable encoding.
+@end table
+@end table
 @node Duplicates
 @subsection Duplicates
 @vindex nnmail-treat-duplicates
 @vindex nnmail-message-id-cache-file
 @cindex duplicate mails
 If you are a member of a couple of mailing list, you will sometime
 receive two copies of the same mail.  This can be quite annoying, so
 @code{nnmail} checks for and treats any duplicates it might find.  To do
-this, it keeps a cache of old @code{Message-ID}s -
+this, it keeps a cache of old @code{Message-ID}s---
 @code{nnmail-message-id-cache-file}, which is @file{~/.nnmail-cache} by
 default.  The approximate maximum number of @code{Message-ID}s stored
 there is controlled by the @code{nnmail-message-id-cache-length}
 variable, which is 1000 by default. (So 1000 @code{Message-ID}s will be
 stored.) If all this sounds scary to you, you can set
 @findex nnml-generate-nov-databases
 If your @code{nnml} groups and @sc{nov} files get totally out of whack,
 you can do a complete update by typing @kbd{M-x
 nnml-generate-nov-databases}.  This command will trawl through the
 entire @code{nnml} hierarchy, looking at each and every article, so it
-might take a while to complete.
+might take a while to complete.  A better interface to this
+functionality can be found in the server buffer (@pxref{Server
+Commands}).
 @node MH Spool
 @subsubsection MH Spool
 @cindex nnmh
 Gnus can do more than just read news or mail.  The methods described
 below allow Gnus to view directories and files as if they were
 newsgroups.
 @menu
-* Directory Groups::   You can read a directory as if it was a newsgroup.
+* Directory Groups::      You can read a directory as if it was a newsgroup.
-* Anything Groups::    Dired?  Who needs dired?
+* Anything Groups::       Dired?  Who needs dired?
-* Document Groups::    Single files can be the basis of a group.
+* Document Groups::       Single files can be the basis of a group.
-* SOUP::               Reading @sc{SOUP} packets ``offline''.
+* SOUP::                  Reading @sc{SOUP} packets ``offline''.
+* Web Searches::          Creating groups from articles that match a string.
+* Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
 @end menu
 @node Directory Groups
 @subsection Directory Groups
 This might be an opportune moment to mention @code{ange-ftp}, that most
 wonderful of all wonderful Emacs packages.  When I wrote @code{nndir}, I
 didn't think much about it---a backend to read directories.  Big deal.
 @code{ange-ftp} changes that picture dramatically.  For instance, if you
-enter @file{"/ftp.hpc.uh.edu:/pub/emacs/ding-list/"} as the the
+enter the @code{ange-ftp} file name
-directory name, ange-ftp will actually allow you to read this directory
+@file{/ftp.hpc.uh.edu:/pub/emacs/ding-list/} as the the directory name,
-over at @samp{sina} as a newsgroup.  Distributed news ahoy!
+@code{ange-ftp} will actually allow you to read this directory over at
+@samp{sina} as a newsgroup.  Distributed news ahoy!
 @code{nndir} will use @sc{nov} files if they are present.
 @code{nndir} is a ``read-only'' backend---you can't delete or expire
 articles with this method.  You can use @code{nnmh} or @code{nnml} for
 a group, @code{nneething} must create ``headers'' that Gnus can use.
 After all, Gnus is a newsreader, in case you're
 forgetting. @code{nneething} does this in a two-step process.  First, it
 snoops each file in question.  If the file looks like an article (i.e.,
 the first few lines look like headers), it will use this as the head.
-If this is just some arbitrary file without a head (eg. a C source
+If this is just some arbitrary file without a head (e.g. a C source
 file), @code{nneething} will cobble up a header out of thin air.  It
 will use file ownership, name and date and do whatever it can with these
 elements.
 All this should happen automatically for you, and you will be presented
 If you have some old archived articles that you want to insert into your
 new & spiffy Gnus mail backend, @code{nndoc} can probably help you with
 that.  Say you have an old @file{RMAIL} file with mail that you now want
 to split into your new @code{nnml} groups.  You look at that file using
-@code{nndoc}, set the process mark on all the articles in the buffer
+@code{nndoc} (using the @kbd{G f} command in the group buffer
-(@kbd{M P b}, for instance), and then re-spool (@kbd{B r}) using
+(@pxref{Foreign Groups})), set the process mark on all the articles in
-@code{nnml}.  If all goes well, all the mail in the @file{RMAIL} file is
+the buffer (@kbd{M P b}, for instance), and then re-spool (@kbd{B r})
-now also stored in lots of @code{nnml} directories, and you can delete
+using @code{nnml}.  If all goes well, all the mail in the @file{RMAIL}
-that pesky @file{RMAIL} file.  If you have the guts!
+file is now also stored in lots of @code{nnml} directories, and you can
+delete that pesky @file{RMAIL} file.  If you have the guts!
 Virtual server variables:
 @table @code
 @item nndoc-article-type
 This variable says whether Gnus is to consider the group a news group or
 a mail group.  There are two legal values:  @code{mail} (the default)
 and @code{news}.
 @end table
+@menu
+* Document Server Internals::   How to add your own document types.
+@end menu
+@node Document Server Internals
+@subsubsection Document Server Internals
+Adding new document types to be recognized by @code{nndoc} isn't
+difficult.  You just have to whip up a definition of what the document
+looks like, write a predicate function to recognize that document type,
+and then hook into @code{nndoc}.
+First, here's an example document type definition:
+@example
+(mmdf
+(article-begin .  "^\^A\^A\^A\^A\n")
+(body-end .  "^\^A\^A\^A\^A\n"))
+@end example
+The definition is simply a unique @dfn{name} followed by a series of
+regexp pseudo-variable settings.  Below are the possible
+variables---don't be daunted by the number of variables; most document
+types can be defined with very few settings:
+@table @code
+@item first-article
+If present, @code{nndoc} will skip past all text until it finds
+something that match this regexp.  All text before this will be
+totally ignored.
+@item article-begin
+This setting has to be present in all document type definitions.  It
+says what the beginning of each article looks like.
+@item head-begin-function
+If present, this should be a function that moves point to the head of
+the article.
+@item nndoc-head-begin
+If present, this should be a regexp that matches the head of the
+article.
+@item nndoc-head-end
+This should match the end of the head of the article.  It defaults to
+@samp{^$}---the empty line.
+@item body-begin-function
+If present, this function should move point to the beginning of the body
+of the article.
+@item body-begin
+This should match the beginning of the body of the article.  It defaults
+to @samp{^\n}.
+@item body-end-function
+If present, this function should move point to the end of the body of
+the article.
+@item body-end
+If present, this should match the end of the body of the article.
+@item nndoc-file-end
+If present, this should match the end of the file.  All text after this
+regexp will be totally ignored.
+@end table
+So, using these variables @code{nndoc} is able to dissect a document
+file into a series of articles, each with a head and a body.  However, a
+few more variables are needed since not all document types are all that
+news-like---variables needed to transform the head or the body into
+something that's palatable for Gnus:
+@table @code
+@item prepare-body-function
+If present, this function will be called when requesting an article.  It
+will be called with point at the start of the body, and is useful if the
+document has encoded some parts of its contents.
+@item article-transform-function
+If present, this function is called when requesting an article.  It's
+meant to be used how more wide-ranging transformation of both head and
+body of the article.
+@item generate-head-function
+If present, this function is called to generate a head that Gnus can
+understand.  It is called with the article number as a parameter, and is
+expected to generate a nice head for the article in question.  It is
+called when requesting the headers of all articles.
+@end table
+Let's look at the most complicated example I can come up with---standard
+digests:
+@example
+(standard-digest
+(first-article . ,(concat "^" (make-string 70 ?-) "\n\n+"))
+(article-begin . ,(concat "\n\n" (make-string 30 ?-) "\n\n+"))
+(prepare-body-function . nndoc-unquote-dashes)
+(body-end-function . nndoc-digest-body-end)
+(head-end . "^ ?$")
+(body-begin . "^ ?\n")
+(file-end . "^End of .*digest.*[0-9].*\n\\*\\*\\|^End of.*Digest *$")
+(subtype digest guess))
+@end example
+We see that all text before a 70-width line of dashes is ignored; all
+text after a line that starts with that @samp{^End of} is also ignored;
+each article begins with a 30-width line of dashes; the line separating
+the head from the body may contain a single space; and that the body is
+run through @code{nndoc-unquote-dashes} before being delivered.
+To hook your own document definition into @code{nndoc}, use the
+@code{nndoc-add-type} function.  It takes two parameters---the first is
+the definition itself and the second (optional) parameter says where in
+the document type definition alist to put this definition.  The alist is
+traversed sequentially, and @code{nndoc-TYPE-type-p} is called for each
+type.  So @code{nndoc-mmdf-type-p} is called to see whether a document
+is of @code{mmdf} type, and so on.  These type predicates should return
+@code{nil} if the document is not of the correct type; @code{t} if it is
+of the correct type; and a number if the document might be of the
+correct type.  A high number means high probability; a low number means
+low probability with @samp{0} being the lowest legal number.
 @node SOUP
 @subsection SOUP
 @cindex SOUP
 @cindex offline
 A file format called @sc{soup} has been developed for transporting news
 and mail from servers to home machines and back again.  It can be a bit
 fiddly.
+First some terminology:
+@table @dfn
+@item server
+This is the machine that is connected to the outside world and where you
+get news and/or mail from.
+@item home machine
+This is the machine that you want to do the actual reading and responding
+on.  It is typically not connected to the rest of the world in any way.
+@item packet
+Something that contains messages and/or commands.  There are two kinds
+of packets:
+@table @dfn
+@item message packets
+These are packets made at the server, and typically contains lots of
+messages for you to read.  These are called @file{SoupoutX.tgz} by
+default, where @var{X} is a number.
+@item response packets
+These are packets made at the home machine, and typically contains
+replies that you've written.  These are called @file{SoupinX.tgz} by
+default, where @var{X} is a number.
+@end table
+@end table
 @enumerate
 @item
 You log in on the server and create a @sc{soup} packet.  You can either
-use a dedicated @sc{soup} thingie, or you can use Gnus to create the
+use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
-packet with the @kbd{O s} command.
+can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
+s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
 @item
 You transfer the packet home.  Rail, boat, car or modem will do fine.
 @item
 You put the packet in your home directory.
 @item
-You fire up Gnus using the @code{nnsoup} backend as the native server.
+You fire up Gnus on your home machine using the @code{nnsoup} backend as
+the native or secondary server.
 @item
 You read articles and mail and answer and followup to the things you
-want.
+want (@pxref{SOUP Replies}).
 @item
 You do the @kbd{G s r} command to pack these replies into a @sc{soup}
 packet.
 @end menu
 @node SOUP Commands
 @subsubsection SOUP Commands
+These are commands for creating and manipulating @sc{soup} packets.
 @table @kbd
 @item G s b
 @kindex G s b (Group)
 @findex gnus-group-brew-soup
 process/prefix convention.
 @item G s w
 @kindex G s w (Group)
 @findex gnus-soup-save-areas
-Save all data files (@code{gnus-soup-save-areas}).
+Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
 @item G s s
 @kindex G s s (Group)
 @findex gnus-soup-send-replies
 Send all replies from the replies packet
 @item O s
 @kindex O s (Summary)
 @findex gnus-soup-add-article
 This summary-mode command adds the current article to a @sc{soup} packet
 (@code{gnus-soup-add-article}).  It understands the process/prefix
-convention.
+convention (@pxref{Process/Prefix}).
 @end table
 There are a few variables to customize where Gnus will put all these
 @sc{soup} packets.  The default is @file{~/SoupBrew/}.
 @item gnus-soup-replies-directory
 @vindex gnus-soup-replies-directory
 This is what Gnus will use as a temporary directory while sending our
-reply packets.  The default is @file{~/SoupBrew/SoupReplies/}.
+reply packets.  @file{~/SoupBrew/SoupReplies/} is the default.
 @item gnus-soup-prefix-file
 @vindex gnus-soup-prefix-file
 Name of the file where Gnus stores the last used prefix.  The default is
 @samp{gnus-prefix}.
 @sc{soup} system.
 In specific, this is what it does:
 @lisp
-(setq gnus-inews-article-function 'nnsoup-request-post)
+(setq message-send-news-function 'nnsoup-request-post)
-(setq send-mail-function 'nnsoup-request-mail)
+(setq message-send-mail-function 'nnsoup-request-mail)
 @end lisp
 And that's it, really.  If you only want news to go into the @sc{soup}
 system you just use the first line.  If you only want mail to be
 @sc{soup}ed you use the second.
+@node Web Searches
+@subsection Web Searches
+@cindex nnweb
+@cindex DejaNews
+@cindex Alta Vista
+@cindex InReference
+@cindex Usenet searches
+@cindex searching the Usenet
+It's, like, too neat to search the Usenet for articles that match a
+string, but it, like, totally @emph{sucks}, like, totally, to use one of
+those, like, Web browsers, and you, like, have to, rilly, like, look at
+the commercials, so, like, with Gnus you can do @emph{rad}, rilly,
+searches without having to use a browser.
+The @code{nnweb} backend allows an easy interface to the mighty search
+engine.  You create an @code{nnweb} group, enter a search pattern, and
+then enter the group and read the articles like you would any normal
+group.  The @kbd{G w} command in the group buffer (@pxref{Foreign
+Groups}) will do this in an easy-to-use fashion.
+@code{nnweb} groups don't really lend themselves to being solid
+groups---they have a very fleeting idea of article numbers.  In fact,
+each time you enter an @code{nnweb} group (not even changing the search
+pattern), you are likely to get the articles ordered in a different
+manner.  Not even using duplicate suppression (@code{Duplicate
+Suppression}) will help, since @code{nnweb} doesn't even know the
+@code{Message-ID} of the articles before reading them using some search
+engines (DejaNews, for instance).  The only possible way to keep track
+of which articles you've read is by scoring on the @code{Date}
+header---mark all articles that were posted before the last date you
+read the group as read.
+If the search engine changes its output substantially, @code{nnweb}
+won't be able to parse it and will fail.  One could hardly fault the Web
+providers if they were to do this---their @emph{raison d'�tre} is to
+make money off of advertisements, not to provide services to the
+community.  Since @code{nnweb} washes the ads off all the articles, one
+might think that the providers might be somewhat miffed.  We'll see.
+You must have the @code{url} and @code{w3} package installed to be able
+to use @code{nnweb}.
+Virtual server variables:
+@table @code
+@item nnweb-type
+@vindex nnweb-type
+What search engine type is being used.  The currently supported types
+are @code{dejanews}, @code{altavista} and @code{reference}.
+@item nnweb-search
+@vindex nnweb-search
+The search string to feed to the search engine.
+@item nnweb-max-hits
+@vindex nnweb-max-hits
+Advisory maximum number of hits per search to display.  The default is
+100.
+@item nnweb-type-definition
+@vindex nnweb-type-definition
+Type-to-definition alist.  This alist says what @code{nnweb} should do
+with the various search engine types.  The following elements must be
+present:
+@table @code
+@item article
+Function to decode the article and provide something that Gnus
+understands.
+@item map
+Function to create an article number to message header and URL alist.
+@item search
+Function to send the search string to the search engine.
+@item address
+The address the aforementioned function should send the search string
+to.
+@item id
+Format string URL to fetch an article by @code{Message-ID}.
+@end table
+@end table
+@node Mail-To-News Gateways
+@subsection Mail-To-News Gateways
+@cindex mail-to-news gateways
+@cindex gateways
+If your local @code{nntp} server doesn't allow posting, for some reason
+or other, you can post using one of the numerous mail-to-news gateways.
+The @code{nngateway} backend provides the interface.
+Note that you can't read anything from this backend---it can only be
+used to post with.
+Server variables:
+@table @code
+@item nngateway-address
+@vindex nngateway-address
+This is the address of the mail-to-news gateway.
+@item nngateway-header-transformation
+@vindex nngateway-header-transformation
+News headers have often have to be transformed in some odd way or other
+for the mail-to-news gateway to accept it.  This variable says what
+transformation should be called, and defaults to
+@code{nngateway-simple-header-transformation}.  The function is called
+narrowed to the headers to be transformed and with one parameter---the
+gateway address.
+This default function just inserts a new @code{To} header based on the
+@code{Newsgroups} header and the gateway address---an article with this
+@code{Newsgroups} header:
+@example
+Newsgroups: alt.religion.emacs
+@end example
+will get this @code{From} header inserted:
+@example
+To: alt-religion-emacs@@GATEWAY
+@end example
+@end table
+So, to use this, simply say something like:
+@lisp
+(setq gnus-post-method '(nngateway "GATEWAY.ADDRESS"))
+@end lisp
 @node Combined Groups
 @section Combined Groups
 * Summary Score Commands::   Adding score entries for the current group.
 * Group Score Commands::     General score commands.
 * Score Variables::          Customize your scoring.  (My, what terminology).
 * Score File Format::        What a score file may contain.
 * Score File Editing::       You can edit score files by hand as well.
-* Adaptive Scoring::         Big Sister Gnus @emph{knows} what you read.
+* Adaptive Scoring::         Big Sister Gnus knows what you read.
+* Home Score File::          How to say where new score entries are to go.
 * Followups To Yourself::    Having Gnus notice when people answer you.
 * Scoring Tips::             How to score effectively.
 * Reverse Scoring::          That problem child of old is not problem.
 * Global Score Files::       Earth-spanning, ear-splitting score files.
 * Kill Files::               They are still here, but they can be ignored.
+* Converting Kill Files::    Translating kill files to score files.
 * GroupLens::                Getting predictions on what you like to read.
+* Advanced Scoring::         Using logical expressions to build score rules.
+* Score Decays::             It can be useful to let scores wither away.
 @end menu
 @node Summary Score Commands
 @section Summary Score Commands
 @dfn{current score file alist}.  The score commands simply insert
 entries into this list, and upon group exit, this list is saved.
 The current score file is by default the group's local score file, even
 if no such score file actually exists.  To insert score commands into
-some other score file (eg. @file{all.SCORE}), you must first make this
+some other score file (e.g. @file{all.SCORE}), you must first make this
 score file the current one.
 General score commands that don't actually change the score file:
 @table @kbd
 @findex gnus-score-find-trace
 Display all score rules that have been used on the current article
 (@code{gnus-score-find-trace}).
 @item V R
-@cindex V R (Summary)
+@kindex V R (Summary)
 @findex gnus-summary-rescore
 Run the current summary through the scoring process
 (@code{gnus-summary-rescore}).  This might be useful if you're playing
 around with your score files behind Gnus' back and want to see the
 effect you're having.
 (@code{gnus-score-edit-file}).
 @item V F
 @kindex V F (Summary)
 @findex gnus-score-flush-cache
-Flush the score cahe (@code{gnus-score-flush-cache}).  This is useful
+Flush the score cache (@code{gnus-score-flush-cache}).  This is useful
 after editing score files.
 @item V C
 @kindex V C (Summary)
 @findex gnus-score-customize
 @item gnus-summary-default-score
 @vindex gnus-summary-default-score
 Default score of an article, which is 0 by default.
+@item gnus-summary-expunge-below
+@vindex gnus-summary-expunge-below
+Don't display the summary lines of articles that have scores lower than
+this variable.  This is @code{nil} by default, which means that no
+articles will be hidden.
 @item gnus-score-over-mark
 @vindex gnus-score-over-mark
 Mark (in the third column) used for articles with a score over the
 default.  Default is @samp{+}.
 Only apply the group's own score file.
 @item gnus-score-find-bnews
 @findex gnus-score-find-bnews
 Apply all score files that match, using bnews syntax.  This is the
-default.  For instance, if the current group is @samp{gnu.emacs.gnus},
+default.  If the current group is @samp{gnu.emacs.gnus}, for instance,
 @file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
 @file{gnu.all.SCORE} would all apply.  In short, the instances of
 @samp{all} in the score file names are translated into @samp{.*}, and
 then a regexp match is done.
 This means that if you have some score entries that you want to apply to
 all groups, then you put those entries in the @file{all.SCORE} file.
+The score files are applied in a semi-random order, although Gnus will
+try to apply the more general score files before the more specific score
+files.  It does this by looking at the number of elements in the score
+file names---discarding the @samp{all} elements.
 @item gnus-score-find-hierarchical
 @findex gnus-score-find-hierarchical
 Apply all score files from all the parent groups.  This means that you
-can't have score files like @file{all.SCORE} or @file{all.emacs.SCORE},
+can't have score files like @file{all.SCORE}, but you can have
-but you can have @file{SCORE},  @file{comp.SCORE} and
+@file{SCORE}, @file{comp.SCORE} and @file{comp.emacs.SCORE}.
-@file{comp.emacs.SCORE}.
 @end table
 This variable can also be a list of functions.  In that case, all these
 functions will be called, and all the returned lists of score files will
 be applied.  These functions can also return lists of score alists
 whether this score entry matches the article.  What match types that can
 be used depends on what header you wish to perform the match on.
 @table @dfn
 @item From, Subject, References, Xref, Message-ID
-For most header types, there are the @code{r} and @code{R} (regexp) as
+For most header types, there are the @code{r} and @code{R} (regexp), as
-well as @code{s} and @code{S} (substring) types and @code{e} and
+well as @code{s} and @code{S} (substring) types, and @code{e} and
-@code{E} (exact match) types.  If this element is not present, Gnus will
+@code{E} (exact match), and @code{w} (word match) types.  If this
-assume that substring matching should be used.  @code{R} and @code{S}
+element is not present, Gnus will assume that substring matching should
-differ from the other two in that the matches will be done in a
+be used.  @code{R}, @code{S}, and @code{E} differ from the others in
-case-sensitive manner.  All these one-letter types are really just
+that the matches will be done in a case-sensitive manner.  All these
-abbreviations for the @code{regexp}, @code{string} and @code{exact}
+one-letter types are really just abbreviations for the @code{regexp},
-types, which you can use instead, if you feel like.
+@code{string}, @code{exact}, and @code{word} types, which you can use
+instead, if you feel like.
 @item Lines, Chars
 These two headers use different match types: @code{<}, @code{>},
-@code{=}, @code{>=} and @code{<=}.
+@code{=}, @code{>=} and @code{<=}.  When matching on @code{Lines}, be
+careful because some backends (like @code{nndir}) do not generate
+@code{Lines} header, so every article ends up being marked as having 0
+lines.  This can lead to strange results if you happen to lower score of
+the articles with few lines.
 @item Date
-For the Date header we have three match types: @code{before}, @code{at}
+For the Date header we have three kinda silly match types:
-and @code{after}.  I can't really imagine this ever being useful, but,
+@code{before}, @code{at} and @code{after}.  I can't really imagine this
-like, it would feel kinda silly not to provide this function.  Just in
+ever being useful, but, like, it would feel kinda silly not to provide
-case.  You never know.  Better safe than sorry.  Once burnt, twice shy.
+this function.  Just in case.  You never know.  Better safe than sorry.
-Don't judge a book by its cover.  Never not have sex on a first date.
+Once burnt, twice shy.  Don't judge a book by its cover.  Never not have
-(I have been told that at least one person, and I quote, ``found this
+sex on a first date.  (I have been told that at least one person, and I
-function indispensable'', however.)
+quote, ``found this function indispensable'', however.)
+@cindex ISO8601
+@cindex date
+A more useful match type is @code{regexp}.  With it, you can match the
+date string using a regular expression.  The date is normalized to
+ISO8601 compact format first---@samp{YYYYMMDDTHHMMSS}.  If you want to
+match all articles that have been posted on April 1st in every year, you
+could use @samp{....0401.........} as a match string, for instance.
+(Note that the date is kept in its original time zone, so this will
+match articles that were posted when it was April 1st where the article
+was posted from.  Time zones are such wholesome fun for the whole
+family, eh?)
 @item Head, Body, All
 These three match keys use the same match types as the @code{From} (etc)
 header uses.
 @item Followup
-This match key will add a score entry on all articles that followup to
+This match key is somewhat special, in that it will match the
-some author.  Uses the same match types as the @code{From} header uses.
+@code{From} header, and affect the score of not only the matching
+articles, but also all followups to the matching articles.  This allows
+you e.g. increase the score of followups to your own articles, or
+decrease the score of followups to the articles of some known
+trouble-maker.  Uses the same match types as the @code{From} header
+uses.
 @item Thread
-This match key will add a score entry on all articles that are part of
+This match key works along the same lines as the @code{Followup} match
-a thread.  Uses the same match types as the @code{References} header
+key.  If you say that you want to score on a (sub-)thread that is
-uses.
+started by an article with a @code{Message-ID} @var{X}, then you add a
+@samp{thread} match.  This will add a new @samp{thread} match for each
+article that has @var{X} in its @code{References} header.  (These new
+@samp{thread} matches will use the @code{Message-ID}s of these matching
+articles.)  This will ensure that you can raise/lower the score of an
+entire thread, even though some articles in the thread may not have
+complete @code{References} headers.  Note that using this may lead to
+undeterministic scores of the articles in the thread.
 @end table
 @end enumerate
 @item mark
 The value of this entry should be a number.  Any articles with a score
 The value of this entry should be any number of file names.  These files
 are assumed to be score files as well, and will be loaded the same way
 this one was.
 @item exclude-files
-The clue of this entry should be any number of files.  This files will
+The clue of this entry should be any number of files.  These files will
 not be loaded, even though they would normally be so, for some reason or
 other.
 @item eval
 The value of this entry will be @code{eval}el.  This element will be
 will only follow a few of the threads, also want to see any new threads.
 You can do this with the following two score file entries:
 @example
-	(orphan -500)
+(orphan -500)
-	(mark-and-expunge -100)
+(mark-and-expunge -100)
 @end example
 When you enter the group the first time, you will only see the new
 threads.  You then raise the score of the threads that you find
 interesting (with @kbd{I T} or @kbd{I S}), and ignore (@kbd{C y}) the
 @vindex gnus-use-adaptive-scoring
 When you read an article, or mark an article as read, or kill an
 article, you leave marks behind.  On exit from the group, Gnus can sniff
 these marks and add score elements depending on what marks it finds.
 You turn on this ability by setting @code{gnus-use-adaptive-scoring} to
-@code{t}.
+@code{t} or @code{(line)}.  If you want score adaptively on separate
+words appearing in the subjects, you should set this variable to
+@code{(word)}.  If you want to use both adaptive methods, set this
+variable to @code{(word line)}.
 @vindex gnus-default-adaptive-score-alist
 To give you complete control over the scoring process, you can customize
 the @code{gnus-default-adaptive-score-alist} variable.  For instance, it
 might look something like this:
 If you have marked 10 articles with the same subject with
 @code{gnus-del-mark}, the rule for that mark will be applied ten times.
 That means that that subject will get a score of ten times -1, which
 should be, unless I'm much mistaken, -10.
+If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
+the read articles will be marked with the @samp{E} mark.  This'll
+probably make adaptive scoring slightly impossible, so auto-expiring and
+adaptive scoring doesn't really mix very well.
 The headers you can score on are @code{from}, @code{subject},
 @code{message-id}, @code{references}, @code{xref}, @code{lines},
 @code{chars} and @code{date}.  In addition, you can score on
 @code{followup}, which will create an adaptive score entry that matches
 on the @code{References} header using the @code{Message-ID} of the
 the length of the match is less than
 @code{gnus-score-exact-adapt-limit}, exact matching will be used.  If
 this variable is @code{nil}, exact matching will always be used to avoid
 this problem.
+@vindex gnus-default-adaptive-word-score-alist
+As mentioned above, you can adapt either on individual words or entire
+headers.  If you adapt on words, the
+@code{gnus-default-adaptive-word-score-alist} variable says what score
+each instance of a word should add given a mark.
+@lisp
+(setq gnus-default-adaptive-word-score-alist
+`((,gnus-read-mark . 30)
+(,gnus-catchup-mark . -10)
+(,gnus-killed-mark . -20)
+(,gnus-del-mark . -15)))
+@end lisp
+This is the default value.  If you have adaption on words enabled, every
+word that appears in subjects of articles that are marked with
+@code{gnus-read-mark} will result in a score rule that increase the
+score with 30 points.
+@vindex gnus-default-ignored-adaptive-words
+@vindex gnus-ignored-adaptive-words
+Words that appear in the @code{gnus-default-ignored-adaptive-words} list
+will be ignored.  If you wish to add more words to be ignored, use the
+@code{gnus-ignored-adaptive-words} list instead.
+@vindex gnus-adaptive-word-syntax-table
+When the scoring is done, @code{gnus-adaptive-word-syntax-table} is the
+syntax table in effect.  It is similar to the standard syntax table, but
+it considers numbers to be non-word-constituent characters.
+After using this scheme for a while, it might be nice to write a
+@code{gnus-psychoanalyze-user} command to go through the rules and see
+what words you like and what words you don't like.  Or perhaps not.
+Note that the adaptive word scoring thing is highly experimental and is
+likely to change in the future.  Initial impressions seem to indicate
+that it's totally useless as it stands.  Some more work (involving more
+rigorous statistical methods) will have to be done to make this useful.
+@node Home Score File
+@section Home Score File
+The score file where new score file entries will go is called the
+@dfn{home score file}.  This is normally (and by default) the score file
+for the group itself.  For instance, the home score file for
+@samp{gnu.emacs.gnus} is @file{gnu.emacs.gnus.SCORE}.
+However, this may not be what you want.  It is often convenient to share
+a common home score file among many groups---all @samp{emacs} groups
+could perhaps use the same home score file.
+@vindex gnus-home-score-file
+The variable that controls this is @code{gnus-home-score-file}.  It can
+be:
+@enumerate
+@item
+A string.  Then this file will be used as the home score file for all
+groups.
+@item
+A function. The result of this function will be used as the home score
+file.  The function will be called with the name of the group as the
+parameter.
+@item
+A list.  The elements in this list can be:
+@enumerate
+@item
+@var{(regexp file-name)}.  If the @var{regexp} matches the group name,
+the @var{file-name} will will be used as the home score file.
+@item
+A function. If the function returns non-nil, the result will be used as
+the home score file.
+@item
+A string.  Use the string as the home score file.
+@end enumerate
+The list will be traversed from the beginning towards the end looking
+for matches.
+@end enumerate
+So, if you want to use just a single score file, you could say:
+@lisp
+(setq gnus-home-score-file
+"my-total-score-file.SCORE")
+@end lisp
+If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
+@file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
+@lisp
+(setq gnus-home-score-file
+'gnus-hierarchial-home-score-file)
+@end lisp
+This is a ready-made function provided for your convenience.
+If you want to have one score file for the @samp{emacs} groups and
+another for the @samp{comp} groups, while letting all other groups use
+their own home score files:
+@lisp
+(setq gnus-home-score-file
+;; All groups that match the regexp "\\.emacs"
+'("\\.emacs" "emacs.SCORE")
+;; All the comp groups in one score file
+("^comp" "comp.SCORE"))
+@end lisp
+@vindex gnus-home-adapt-file
+@code{gnus-home-adapt-file} works exactly the same way as
+@code{gnus-home-score-file}, but says what the home adaptive score file
+is instead.  All new adaptive file entries will go into the file
+specified by this variable, and the same syntax is allowed.
+In addition to using @code{gnus-home-score-file} and
+@code{gnus-home-adapt-file}, you can also use group parameters
+(@pxref{Group Parameters}) and topic parameters (@pxref{Topic
+Parameters}) to achieve much the same.  Group and topic parameters take
+precedence over this variable.
 @node Followups To Yourself
 @section Followups To Yourself
 Gnus offers two commands for picking out the @code{Message-ID} header in
 @findex gnus-score-followup-thread
 This will add a score to all articles that appear in a thread ``below''
 your own article.
 @end table
-@vindex gnus-inews-article-hook
+@vindex message-sent-hook
 These two functions are both primarily meant to be used in hooks like
-@code{message-send-hook}.
+@code{message-sent-hook}.
+If you look closely at your own @code{Message-ID}, you'll notice that
+the first two or three characters are always the same.  Here's two of
+mine:
+@example
+<x6u3u47icf.fsf@@eyesore.no>
+<x6sp9o7ibw.fsf@@eyesore.no>
+@end example
+So ``my'' ident on this machine is @samp{x6}.  This can be
+exploited---the following rule will raise the score on all followups to
+myself:
+@lisp
+("references"
+("<x6[0-9a-z]+\\.fsf@.*eyesore.no>" 1000 nil r))
+@end lisp
+Whether it's the first two or first three characters that are ``yours''
+is system-dependent.
 @node Scoring Tips
 @section Scoring Tips
 @cindex scoring tips
 All you have to do to use other people's score files is to set the
 @code{gnus-global-score-files} variable.  One entry for each score file,
 or each score file directory.  Gnus will decide by itself what score
 files are applicable to which group.
-Say you want to use all score files in the
+Say you want to use the score file
-@file{/ftp@@ftp.some-where:/pub/score} directory and the single score
+@file{/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE} and
-file @file{/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE}:
+all score files in the @file{/ftp@@ftp.some-where:/pub/score} directory:
 @lisp
 (setq gnus-global-score-files
 '("/ftp@@ftp.ifi.uio.no:/pub/larsi/ding/score/soc.motss.SCORE"
 "/ftp@@ftp.some-where:/pub/score/"))
 Anyway, a kill file is a normal @code{emacs-lisp} file.  You can put any
 forms into this file, which means that you can use kill files as some
 sort of primitive hook function to be run on group entry, even though
 that isn't a very good idea.
-XCNormal kill files look like this:
+Normal kill files look like this:
 @lisp
 (gnus-kill "From" "Lars Ingebrigtsen")
 (gnus-kill "Subject" "ding")
 (gnus-expunge "X")
 A hook called in kill-file mode buffers.
 @end table
+@node Converting Kill Files
+@section Converting Kill Files
+@cindex kill files
+@cindex converting kill files
+If you have loads of old kill files, you may want to convert them into
+score files.  If they are ``regular'', you can use
+the @file{gnus-kill-to-score.el} package; if not, you'll have to do it
+by hand.
+The kill to score conversion package isn't included in Gnus by default.
+You can fetch it from
+@file{http://www.ifi.uio.no/~larsi/ding-other/gnus-kill-to-score}.
+If your old kill files are very complex---if they contain more
+non-@code{gnus-kill} forms than not, you'll have to convert them by
+hand.  Or just let them be as they are.  Gnus will still use them as
+before.
 @node GroupLens
 @section GroupLens
 @cindex GroupLens
 GroupLens is a collaborative filtering system that helps you work
 @node Using GroupLens
 @subsection Using GroupLens
 To use GroupLens you must register a pseudonym with your local Better
-Bit Bureau (BBB).  At the moment the only better bit in town is at
+Bit Bureau (BBB).
-@samp{http://www.cs.umn.edu/Research/GroupLens/bbb.html}.
+@samp{http://www.cs.umn.edu/Research/GroupLens/bbb.html} is the only
+better bit in town is at the moment.
 Once you have registered you'll need to set a couple of variables.
 @table @code
 Setting this variable to a non-@code{nil} value will make Gnus hook into
 all the relevant GroupLens functions.
 @item grouplens-pseudonym
 @vindex grouplens-pseudonym
-This variable should be set to the pseudonum you got when registering
+This variable should be set to the pseudonym you got when registering
 with the Better Bit Bureau.
 @item grouplens-newsgroups
 @vindex grouplens-newsgroups
 A list of groups that you want to get GroupLens predictions for.
 enhanced.  It accepts the same specs as the normal summary line format
 (@pxref{Summary Buffer Lines}).  The default is
 @samp{%U%R%z%l%I%(%[%4L: %-20,20n%]%) %s\n}.
 @item grouplens-bbb-host
-Host running the bbbd server.  The default is
+Host running the bbbd server.  @samp{grouplens.cs.umn.edu} is the
-@samp{grouplens.cs.umn.edu}.
+default.
 @item grouplens-bbb-port
 Port of the host running the bbbd server.  The default is 9000.
 @item grouplens-score-offset
 This variable allows the user to magnify the effect of GroupLens scores.
 The scale factor is applied after the offset.  The default is 1.
 @end table
+@node Advanced Scoring
+@section Advanced Scoring
+Scoring on Subjects and From headers is nice enough, but what if you're
+really interested in what a person has to say only when she's talking
+about a particular subject?  Or what about if you really don't want to
+read what person A has to say when she's following up to person B, but
+want to read what she says when she's following up to person C?
+By using advanced scoring rules you may create arbitrarily complex
+scoring patterns.
+@menu
+* Advanced Scoring Syntax::     A definition.
+* Advanced Scoring Examples::   What they look like.
+* Advanced Scoring Tips::       Getting the most out of it.
+@end menu
+@node Advanced Scoring Syntax
+@subsection Advanced Scoring Syntax
+Ordinary scoring rules have a string as the first element in the rule.
+Advanced scoring rules have a list as the first element.  The second
+element is the score to be applied if the first element evaluated to a
+non-@code{nil} value.
+These lists may consist of three logical operators, one redirection
+operator, and various match operators.
+Logical operators:
+@table @code
+@item &
+@itemx and
+This logical operator will evaluate each of its arguments until it finds
+one that evaluates to @code{false}, and then it'll stop.  If all arguments
+evaluate to @code{true} values, then this operator will return
+@code{true}.
+@item |
+@itemx or
+This logical operator will evaluate each of its arguments until it finds
+one that evaluates to @code{true}.  If no arguments are @code{true},
+then this operator will return @code{false}.
+@item !
+@itemx not
+@itemx �
+This logical operator only takes a single argument.  It returns the
+inverse of the value of its argument.
+@end table
+There is an @dfn{indirection operator} that will make its arguments
+apply to the ancestors of the current article being scored.  For
+instance, @code{1-} will make score rules apply to the parent of the
+current article.  @code{2-} will make score fules apply to the
+grandparent of the current article.  Alternatively, you can write
+@code{^^}, where the number of @code{^}s (carets) say how far back into
+the ancestry you want to go.
+Finally, we have the match operators.  These are the ones that do the
+real work.  Match operators are header name strings followed by a match
+and a match type.  A typical match operator looks like @samp{("from"
+"Lars Ingebrigtsen" s)}.  The header names are the same as when using
+simple scoring, and the match types are also the same.
+@node Advanced Scoring Examples
+@subsection Advanced Scoring Examples
+Let's say you want to increase the score of articles written by Lars
+when he's talking about Gnus:
+@example
+((&
+("from" "Lars Ingebrigtsen")
+("subject" "Gnus"))
+1000)
+@end example
+Quite simple, huh?
+When he writes long articles, he sometimes has something nice to say:
+@example
+((&
+("from" "Lars Ingebrigtsen")
+(|
+("subject" "Gnus")
+("lines" 100 >)))
+1000)
+@end example
+However, when he responds to things written by Reig Eigil Logge, you
+really don't want to read what he's written:
+@example
+((&
+("from" "Lars Ingebrigtsen")
+(1- ("from" "Reig Eigir Logge")))
+-100000)
+@end example
+Everybody that follows up Redmondo when he writes about disappearing
+socks should have their scores raised, but only when they talk about
+white socks.  However, when Lars talks about socks, it's usually not
+very interesting:
+@example
+((&
+(1-
+(&
+("from" "redmondo@@.*no" r)
+("body" "disappearing.*socks" t)))
+(! ("from" "Lars Ingebrigtsen"))
+("body" "white.*socks"))
+1000)
+@end example
+The possibilities are endless.
+@node Advanced Scoring Tips
+@subsection Advanced Scoring Tips
+The @code{&} and @code{|} logical operators do short-circuit logic.
+That is, they stop processing their arguments when it's clear what the
+result of the operation will be.  For instance, if one of the arguments
+of an @code{&} evaluates to @code{false}, there's no point in evaluating
+the rest of the arguments.  This means that you should put slow matches
+(@samp{body}, @code{header}) last and quick matches (@samp{from},
+@samp{subject}) first.
+The indirection arguments (@code{1-} and so on) will make their
+arguments work on previous generations of the thread.  If you say
+something like:
+@example
+...
+(1-
+(1-
+("from" "lars")))
+...
+@end example
+Then that means "score on the from header of the grandparent of the
+current article".  An indirection is quite fast, but it's better to say:
+@example
+(1-
+(&
+("from" "Lars")
+("subject" "Gnus")))
+@end example
+than it is to say:
+@example
+(&
+(1- ("from" "Lars"))
+(1- ("subject" "Gnus")))
+@end example
+@node Score Decays
+@section Score Decays
+@cindex score decays
+@cindex decays
+You may find that your scores have a tendency to grow without
+bounds, especially if you're using adaptive scoring.  If scores get too
+big, they lose all meaning---they simply max out and it's difficult to
+use them in any sensible way.
+@vindex gnus-decay-scores
+@findex gnus-decay-score
+@vindex gnus-score-decay-function
+Gnus provides a mechanism for decaying scores to help with this problem.
+When score files are loaded and @code{gnus-decay-scores} is
+non-@code{nil}, Gnus will run the score files through the decaying
+mechanism thereby lowering the scores of all non-permanent score rules.
+The decay itself if performed by the @code{gnus-score-decay-function}
+function, which is @code{gnus-decay-score} by default.  Here's the
+definition of that function:
+@lisp
+(defun gnus-decay-score (score)
+(floor
+(- score
+(* (if (< score 0) 1 -1)
+(min score
+(max gnus-score-decay-constant
+(* (abs score)
+gnus-score-decay-scale)))))))
+@end lisp
+@vindex gnus-score-decay-scale
+@vindex gnus-score-decay-constant
+@code{gnus-score-decay-constant} is 3 by default and
+@code{gnus-score-decay-scale} is 0.05.  This should cause the following:
+@enumerate
+@item
+Scores between -3 and 3 will be set to 0 when this function is called.
+@item
+Scores with magnitudes between 3 and 60 will be shrunk by 3.
+@item
+Scores with magnitudes greater than 60 will be shrunk by 5% of the
+score.
+@end enumerate
+If you don't like this decay function, write your own.  It is called
+with the score to be decayed as its only parameter, and it should return
+the new score, which should be an integer.
+Gnus will try to decay scores once a day.  If you haven't run Gnus for
+four days, Gnus will decay the scores four times, for instance.
 @node Various
 @chapter Various
 * Highlighting and Menus::     Making buffers look all nice and cozy.
 * Buttons::                    Get tendonitis in ten easy steps!
 * Daemons::                    Gnus can do things behind your back.
 * NoCeM::                      How to avoid spam and other fatty foods.
 * Picons::                     How to display pictures of what your reading.
+* Undo::                       Some actions can be undone.
+* Moderation::                 What to do if you're a moderator.
+* XEmacs Enhancements::        There are more pictures and stuff under XEmacs.
 * Various Various::            Things that are really various.
 @end menu
 @node Process/Prefix
 If there is neither a numeric prefix nor any articles marked with the
 process mark, just perform the operation on the current article.
 Quite simple, really, but it needs to be made clear so that surprises
 are avoided.
+Commands that react to the process mark will push the current list of
+process marked articles onto a stack and will then clear all process
+marked articles.  You can restore the previous configuration with the
+@kbd{M P y} command (@pxref{Setting Process Marks}).
 @vindex gnus-summary-goto-unread
 One thing that seems to shock & horrify lots of people is that, for
 instance, @kbd{3 d} does exactly the same as @kbd{d} @kbd{d} @kbd{d}.
 Since each @kbd{d} (which marks the current article as read) by default
 Here's an example format spec (from the group buffer): @samp{%M%S%5y:
 %(%g%)\n}.  We see that it is indeed extremely ugly, and that there are
 lots of percentages everywhere.
+@menu
+* Formatting Basics::     A formatting variable is basically a format string.
+* Advanced Formatting::   Modifying output in various ways.
+* User-Defined Specs::    Having Gnus call your own functions.
+* Formatting Fonts::      Making the formatting look colorful and nice.
+@end menu
+Currently Gnus uses the following formatting variables:
+@code{gnus-group-line-format}, @code{gnus-summary-line-format},
+@code{gnus-server-line-format}, @code{gnus-topic-line-format},
+@code{gnus-group-mode-line-format},
+@code{gnus-summary-mode-line-format},
+@code{gnus-article-mode-line-format},
+@code{gnus-server-mode-line-format}, and
+@code{gnus-summary-pick-line-format}.
+All these format variables can also be arbitrary elisp forms.  In that
+case, they will be @code{eval}ed to insert the required lines.
+@kindex M-x gnus-update-format
+@findex gnus-update-format
+Gnus includes a command to help you while creating your own format
+specs.  @kbd{M-x gnus-update-format} will @code{eval} the current form,
+update the spec in question and pop you to a buffer where you can
+examine the resulting lisp code to be run to generate the line.
+@node Formatting Basics
+@subsection Formatting Basics
 Each @samp{%} element will be replaced by some string or other when the
 buffer in question is generated.  @samp{%5y} means ``insert the @samp{y}
-spec, and pad with spaces to get a 5-character field''.  Just like a
+spec, and pad with spaces to get a 5-character field''.
-normal format spec, almost.
+As with normal C and Emacs Lisp formatting strings, the numerical
-You can also say @samp{%6,4y}, which means that the field will never be
+modifier between the @samp{%} and the formatting type character will
-more than 4 characters wide and never less than 6 characters wide.
+@dfn{pad} the output so that it is always at least that long.
+@samp{%5y} will make the field always (at least) five characters wide by
-There are also specs for highlighting, and these are shared by all the
+padding with spaces to the left.  If you say @samp{%-5y}, it will pad to
-format variables.  Text inside the @samp{%(} and @samp{%)} specifiers
+the right instead.
-will get the special @code{mouse-face} property set, which means that it
-will be highlighted (with @code{gnus-mouse-face}) when you put the mouse
+You may also wish to limit the length of the field to protect against
-pointer over it.
+particularly wide values.  For that you can say @samp{%4,6y}, which
+means that the field will never be more than 6 characters wide and never
+less than 4 characters wide.
+@node Advanced Formatting
+@subsection Advanced Formatting
+It is frequently useful to post-process the fields in some way.
+Padding, limiting, cutting off parts and suppressing certain values can
+be achieved by using @dfn{tilde modifiers}.  A typical tilde spec might
+look like @samp{%~(cut 3)~(ignore "0")y}.
+These are the legal modifiers:
+@table @code
+@item pad
+@itemx pad-left
+Pad the field to the left with spaces until it reaches the required
+length.
+@item pad-right
+Pad the field to the right with spaces until it reaches the required
+length.
+@item max
+@itemx max-left
+Cut off characters from the left until it reaches the specified length.
+@item max-right
+Cut off characters from the right until it reaches the specified
+length.
+@item cut
+@itemx cut-left
+Cut off the specified number of characters from the left.
+@item cut-right
+Cut off the specified number of characters from the right.
+@item ignore
+Return an empty string if the field is equal to the specified value.
+@item form
+Use the specified form as the field value when the @samp{@@} spec is
+used.
+@end table
+Let's take an example.  The @samp{%o} spec in the summary mode lines
+will return a date in compact ISO8601 format---@samp{19960809T230410}.
+This is quite a mouthful, so we want to shave off the century number and
+the time, leaving us with a six-character date.  That would be
+@samp{%~(cut-left 2)~(max-right 6)~(pad 6)o}.  (Cutting is done before
+maxing, and we need the padding to ensure that the date is never less
+than 6 characters to make it look nice in columns.)
+Ignoring is done first; then cutting; then maxing; and then as the very
+last operation, padding.
+If you use lots of these advanced thingies, you'll find that Gnus gets
+quite slow.  This can be helped enormously by running @kbd{M-x
+gnus-compile} when you are satisfied with the look of your lines.
+@xref{Compilation}.
+@node User-Defined Specs
+@subsection User-Defined Specs
+All the specs allow for inserting user defined specifiers---@samp{u}.
+The next character in the format string should be a letter.  Gnus
+will call the function @code{gnus-user-format-function-}@samp{X}, where
+@samp{X} is the letter following @samp{%u}.  The function will be passed
+a single parameter---what the parameter means depends on what buffer
+it's being called from.  The function should return a string, which will
+be inserted into the buffer just like information from any other
+specifier.  This function may also be called with dummy values, so it
+should protect against that.
+You can also use tilde modifiers (@pxref{Advanced Formatting} to achieve
+much the same without defining new functions.  Here's an example:
+@samp{%~(form (count-lines (point-min) (point)))@@}.  The form
+given here will be evaluated to yield the current line number, and then
+inserted.
+@node Formatting Fonts
+@subsection Formatting Fonts
+There are specs for highlighting, and these are shared by all the format
+variables.  Text inside the @samp{%(} and @samp{%)} specifiers will get
+the special @code{mouse-face} property set, which means that it will be
+highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
+over it.
 Text inside the @samp{%[} and @samp{%]} specifiers will have their
 normal faces set using @code{gnus-face-0}, which is @code{bold} by
 default.  If you say @samp{%1[} instead, you'll get @code{gnus-face-1}
 instead, and so on.  Create as many faces as you wish.  The same goes
 @end lisp
 I'm sure you'll be able to use this scheme to create totally unreadable
 and extremely vulgar displays.  Have fun!
-Currently Gnus uses the following formatting variables:
-@code{gnus-group-line-format}, @code{gnus-summary-line-format},
-@code{gnus-server-line-format}, @code{gnus-topic-line-format},
-@code{gnus-group-mode-line-format},
-@code{gnus-summary-mode-line-format},
-@code{gnus-article-mode-line-format},
-@code{gnus-server-mode-line-format}.
 Note that the @samp{%(} specs (and friends) do not make any sense on the
 mode-line variables.
-All these format variables can also be arbitrary elisp forms.  In that
-case, they will be @code{eval}ed to insert the required lines.
-@kindex M-x gnus-update-format
-@findex gnus-update-format
-Gnus includes a command to help you while creating your own format
-specs.  @kbd{M-x gnus-update-format} will @code{eval} the current form,
-update the spec in question and pop you to a buffer where you can
-examine the resulting lisp code to be run to generate the line.
 @node Windows Configuration
 @section Windows Configuration
 @cindex windows configuration
 This is an alist.  The @dfn{key} is a symbol that names some action or
 other.  For instance, when displaying the group buffer, the window
 configuration function will use @code{group} as the key.  A full list of
 possible names is listed below.
-The @dfn{value} (i. e., the @dfn{split}) says how much space each buffer
+The @dfn{value} (i.e., the @dfn{split}) says how much space each buffer
 should occupy.  To take the @code{article} split as an example -
 @lisp
 (article (vertical 1.0 (summary 0.25 point)
 (article 1.0)))
 @code{reply-yank}, @code{mail-bounce}, @code{draft},
 @code{pipe}, @code{bug}, @code{compose-bounce}.
 Note that the @code{message} key is used for both
 @code{gnus-group-mail} and @code{gnus-summary-mail-other-window}.  If
-it is desireable to distinguish between the two, something like this
+it is desirable to distinguish between the two, something like this
 might be used:
 @lisp
 (message (horizontal 1.0
-		     (vertical 1.0 (message 1.0 point))
+(vertical 1.0 (message 1.0 point))
-		     (vertical 0.24
+(vertical 0.24
-			       (if (buffer-live-p gnus-summary-buffer)
+(if (buffer-live-p gnus-summary-buffer)
-				   '(summary 0.5))
+'(summary 0.5))
-			       (group 1.0)))))
+(group 1.0)))))
 @end lisp
 @findex gnus-add-configuration
 Since the @code{gnus-buffer-configuration} variable is so long and
 complicated, there's a function you can use to ease changing the config
 (summary .25 point)
 (article 1.0))))
 @end lisp
 You'd typically stick these @code{gnus-add-configuration} calls in your
-@file{.gnus} file or in some startup hook---they should be run after
+@file{.gnus.el} file or in some startup hook---they should be run after
 Gnus has been loaded.
+@vindex gnus-always-force-window-configuration
-@node Compilation
+If all windows mentioned in the configuration are already visible, Gnus
-@section Compilation
+won't change the window configuration.  If you always want to force the
+``right'' window configuration, you can set
+@code{gnus-always-force-window-configuration} to non-@code{nil}.
+@node Compilation
+@section Compilation
 @cindex compilation
 @cindex byte-compilation
 @findex gnus-compile
 course.)
 To help with this, you can run @kbd{M-x gnus-compile} after you've
 fiddled around with the variables and feel that you're (kind of)
 satisfied.  This will result in the new specs being byte-compiled, and
-you'll get top speed again.
+you'll get top speed again.  Gnus will save these compiled specs in the
+@file{.newsrc.eld} file.  (User-defined functions aren't compiled by
+this function, though---you should compile them yourself by sticking
+them into the @code{.gnus.el} file and byte-compiling that file.)
 @node Mode Lines
 @section Mode Lines
 @cindex mode lines
 @cindex display-time
 @vindex gnus-mode-non-string-length
 By default, Gnus displays information on the current article in the mode
 lines of the summary and article buffers.  The information Gnus wishes
-to display (eg. the subject of the article) is often longer than the
+to display (e.g. the subject of the article) is often longer than the
 mode lines, and therefore have to be cut off at some point.  The
 @code{gnus-mode-non-string-length} variable says how long the other
 elements on the line is (i.e., the non-info part).  If you put
-additional elements on the mode line (eg. a clock), you should modify
+additional elements on the mode line (e.g. a clock), you should modify
 this variable:
 @c Hook written by Francesco Potorti` <pot@cnuce.cnr.it>
 @lisp
 (add-hook 'display-time-hook
 (length display-time-string)))))
 @end lisp
 If this variable is @code{nil} (which is the default), the mode line
 strings won't be chopped off, and they won't be padded either.
+Note that the default is unlikely to be desirable, as even the
+percentage complete in the buffer may be crowded off the mode line;
+the user should configure this variable appropriately for their
+configuration.
 @node Highlighting and Menus
 @section Highlighting and Menus
 @cindex visual
 @item gnus-mouse-face
 @vindex gnus-mouse-face
 This is the face (i.e., font) used for mouse highlighting in Gnus.  No
 mouse highlights will be done if @code{gnus-visual} is @code{nil}.
-@item gnus-display-type
-@vindex gnus-display-type
-This variable is symbol indicating the display type Emacs is running
-under.  The symbol should be one of @code{color}, @code{grayscale} or
-@code{mono}.  If Gnus guesses this display attribute wrongly, either set
-this variable in your @file{~/.emacs} or set the resource
-@code{Emacs.displayType} in your @file{~/.Xdefaults}.
-@item gnus-background-mode
-@vindex gnus-background-mode
-This is a symbol indicating the Emacs background brightness.  The symbol
-should be one of @code{light} or @code{dark}.  If Gnus guesses this
-frame attribute wrongly, either set this variable in your @file{~/.emacs} or
-set the resource @code{Emacs.backgroundMode} in your @file{~/.Xdefaults}.
-`gnus-display-type'.
 @end table
 There are hooks associated with the creation of all the different menus:
 @table @code
 the function will then be called once every day somewhere near that
 time.  Modified by the @var{idle} parameter, of course.
 @vindex gnus-demon-timestep
 (When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
-seconds.  This is @code{60} by default.  If you change that variable,
+seconds.  This is 60 by default.  If you change that variable,
 all the timings in the handlers will be affected.)
 @vindex gnus-use-demon
 To set the whole thing in motion, though, you have to set
 @code{gnus-use-demon} to @code{t}.
 (gnus-demon-add-handler 'gnus-demon-close-connections nil 30)
 @end lisp
 @findex gnus-demon-add-nocem
 @findex gnus-demon-add-scanmail
+@findex gnus-demon-add-rescan
 @findex gnus-demon-add-disconnection
 Some ready-made functions to do this has been created:
-@code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection}, and
+@code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
-@code{gnus-demon-add-scanmail}.  Just put those functions in your
+@code{gnus-demon-add-rescan}, and @code{gnus-demon-add-scanmail}.  Just
-@file{.gnus} if you want those abilities.
+put those functions in your @file{.gnus} if you want those abilities.
 @findex gnus-demon-init
 @findex gnus-demon-cancel
 @vindex gnus-demon-handlers
 If you add handlers to @code{gnus-demon-handlers} directly, you should
 by default.
 @item gnus-nocem-groups
 @vindex gnus-nocem-groups
 Gnus will look for NoCeM messages in the groups in this list.  The
-default is @code{("alt.nocem.misc" "news.admin.net-abuse.announce")}.
+default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
+"alt.nocem.misc" "news.admin.net-abuse.announce")}.
 @item gnus-nocem-issuers
 @vindex gnus-nocem-issuers
 There are many people issuing NoCeM messages.  This list says what
 people you want to listen to.  The default is @code{("Automoose-1"
 The CancelMoose[tm] on autopilot.  The CancelMoose[tm] is reputed to be
 Norwegian, and was the person(s) who invented NoCeM.
 @item jem@@xpat.com;
 @cindex Jem
-Jem---Korean despammer who is getting very busy these days.
+John Milburn---despammer located in Korea who is getting very busy these
+days.
 @item red@@redpoll.mrfs.oh.us (Richard E. Depew)
 Richard E. Depew---lone American despammer.  He mostly cancels binary
 postings to non-binary groups and removes spews (regurgitated articles).
 @end table
 You do not have to heed NoCeM messages from all these people---just the
 ones you want to listen to.
+@item gnus-nocem-verifyer
+@vindex gnus-nocem-verifyer
+@findex mc-verify
+This should be a function for verifying that the NoCeM issuer is who she
+says she is.  The default is @code{mc-verify}, which is a Mailcrypt
+function.  If this is too slow and you don't care for verification
+(which may be dangerous), you can set this variable to @code{nil}.
 @item gnus-nocem-directory
 @vindex gnus-nocem-directory
 This is where Gnus will store its NoCeM cache files.  The default is
 @file{~/News/NoCeM/}.
 @node Picon Basics
 @subsection Picon Basics
-What are Picons?  To quote directly from the Picons Web site
+What are Picons?  To quote directly from the Picons Web site:
-(@samp{http://www.cs.indiana.edu/picons/ftp/index.html}):
 @quotation
 @dfn{Picons} is short for ``personal icons''.  They're small,
 constrained images used to represent users and domains on the net,
 organized into databases so that the appropriate image for a given
 databases for Usenet newsgroups and weather forecasts.  The picons are
 in either monochrome @code{XBM} format or color @code{XPM} and
 @code{GIF} formats.
 @end quotation
-Please see the above mentioned web site for instructions on obtaining
+For instructions on obtaining and installing the picons databases, point
-and installing the picons databases, or the following ftp site:
+your Web browser at
-@samp{http://www.cs.indiana.edu/picons/ftp/index.html}.
+@file{http://www.cs.indiana.edu/picons/ftp/index.html}.
 @vindex gnus-picons-database
 Gnus expects picons to be installed into a location pointed to by
 @code{gnus-picons-database}.
 @item gnus-picons-display-where
 @vindex gnus-picons-display-where
 Where the picon images should be displayed.  It is @code{picons} by
 default (which by default maps to the buffer @samp{*Picons*}).  Other
 valid places could be @code{article}, @code{summary}, or
-@samp{"*scratch*"} for all I care.  Just make sure that you've made the
+@samp{*scratch*} for all I care.  Just make sure that you've made the
 buffer visible using the standard Gnus window configuration
-routines---@xref{Windows Configuration}.
+routines---@pxref{Windows Configuration}.
 @end table
 Note: If you set @code{gnus-use-picons} to @code{t}, it will set up your
 window configuration for you to include the @code{picons} buffer.
 newsgroups.
 @item gnus-picons-user-directories
 @vindex gnus-picons-user-directories
 List of subdirectories to search in @code{gnus-picons-database} for user
-faces.  Defaults to @code{("local" "users" "usenix" "misc/MISC")}.
+faces.  @code{("local" "users" "usenix" "misc/MISC")} is the default.
 @item gnus-picons-domain-directories
 @vindex gnus-picons-domain-directories
 List of subdirectories to search in @code{gnus-picons-database} for
 domain name faces.  Defaults to @code{("domains")}.  Some people may
 @samp{*Icon Buffer*}.
 @end table
+@node Undo
+@section Undo
+@cindex undo
+It is very useful to be able to undo actions one has done.  In normal
+Emacs buffers, it's easy enough---you just push the @code{undo} button.
+In Gnus buffers, however, it isn't that simple.
+The things Gnus displays in its buffer is of no value whatsoever to
+Gnus---it's all just data that is designed to look nice to the user.
+Killing a group in the group buffer with @kbd{C-k} makes the line
+disappear, but that's just a side-effect of the real action---the
+removal of the group in question from the internal Gnus structures.
+Undoing something like that can't be done by the normal Emacs
+@code{undo} function.
+Gnus tries to remedy this somewhat by keeping track of what the user
+does and coming up with actions that would reverse the actions the user
+takes.  When the user then presses the @code{undo} key, Gnus will run
+the code to reverse the previous action, or the previous actions.
+However, not all actions are easily reversible, so Gnus currently offers
+a few key functions to be undoable.  These include killing groups,
+yanking groups, and changing the list of read articles of groups.
+That's it, really.  More functions may be added in the future, but each
+added function means an increase in data to be stored, so Gnus will
+never be totally undoable.
+@findex gnus-undo-mode
+@vindex gnus-use-undo
+@findex gnus-undo
+The undoability is provided by the @code{gnus-undo-mode} minor mode.  It
+is used if @code{gnus-use-undo} is non-@code{nil}, which is the
+default.  The @kbd{M-C-_} key performs the @code{gnus-undo} command
+command, which should feel kinda like the normal Emacs @code{undo}
+command.
+@node Moderation
+@section Moderation
+@cindex moderation
+If you are a moderator, you can use the @file{gnus-mdrtn.el} package.
+It is not included in the standard Gnus package.  Write a mail to
+@samp{larsi@@ifi.uio.no} and state what group you moderate, and you'll
+get a copy.
+The moderation package is implemented as a minor mode for summary
+buffers.  Put
+@lisp
+(add-hook 'gnus-summary-mode-hook 'gnus-moderate)
+@end lisp
+in your @file{.gnus.el} file.
+If you are the moderation of @samp{rec.zoofle}, this is how it's
+supposed to work:
+@enumerate
+@item
+You split your incoming mail by matching on
+@samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
+articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
+@item
+You enter that group once in a while and post articles using the @kbd{e}
+(edit-and-post) or @kbd{s} (just send unedited) commands.
+@item
+If, while reading the @samp{rec.zoofle} newsgroup, you happen upon some
+articles that weren't approved by you, you can cancel them with the
+@kbd{c} command.
+@end enumerate
+To use moderation mode in these two groups, say:
+@lisp
+(setq gnus-moderated-list
+"^nnml:rec.zoofle$\\|^rec.zoofle$")
+@end lisp
+@node XEmacs Enhancements
+@section XEmacs Enhancements
+@cindex XEmacs
+XEmacs is able to display pictures and stuff, so Gnus has taken
+advantage of that.  Relevant variables include:
+@table @code
+@item gnus-xmas-glyph-directory
+@vindex gnus-xmas-glyph-directory
+This is where Gnus will look for pictures.  Gnus will normally
+auto-detect this directory, but you may set it manually if you have an
+unusual directory structure.
+@item gnus-xmas-logo-color-alist
+@vindex gnus-xmas-logo-color-alist
+This is an alist where the key is a type symbol and the values are the
+foreground and background color of the splash page glyph.
+@item gnus-xmas-logo-color-style
+@vindex gnus-xmas-logo-color-style
+This is the key used to look up the color in the alist described above.
+Legal values include @code{flame}, @code{pine}, @code{moss},
+@code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
+@code{labia}, @code{berry}, @code{neutral}, and @code{september}.
+@item gnus-use-toolbar
+@vindex gnus-use-toolbar
+If @code{nil}, don't display toolbars.  If non-@code{nil}, it should be
+one of @code{default-toolbar}, @code{top-toolbar}, @code{bottom-toolbar},
+@code{right-toolbar}, or @code{left-toolbar}.
+@item gnus-group-toolbar
+@vindex gnus-group-toolbar
+The toolbar in the group buffer.
+@item gnus-summary-toolbar
+@vindex gnus-summary-toolbar
+The toolbar in the summary buffer.
+@item gnus-summary-mail-toolbar
+@vindex gnus-summary-mail-toolbar
+The toolbar in the summary buffer of mail groups.
+@item gnus-xmas-modeline-glyph
+@vindex gnus-xmas-modeline-glyph
+A glyph displayed in all Gnus mode lines.  It is a tiny gnu head by
+default.
+@end table
 @node Various Various
 @section Various Various
 @cindex mode lines
 @cindex highlights
 @table @code
+@item gnus-directory
+@vindex gnus-directory
+All Gnus directories will be initialized from this variable, which
+defaults to the @samp{SAVEDIR} environment variable, or @file{~/News/}
+if that variable isn't set.
+@item gnus-default-directory
+@vindex gnus-default-directory
+Not related to the above variable at all---this variable says what the
+default directory of all Gnus buffers should be.  If you issue commands
+like @kbd{C-x C-f}, the prompt you'll get starts in the current buffer's
+default directory.  If this variable is @code{nil} (which is the
+default), the default directory will be the default directory of the
+buffer you were in when you started Gnus.
 @item gnus-verbose
 @vindex gnus-verbose
 This variable is an integer between zero and ten.  The higher the value,
 the more messages will be displayed.  If this variable is zero, Gnus
 to the Gnus backends instead of Gnus proper.
 @item nnheader-max-head-length
 @vindex nnheader-max-head-length
 When the backends read straight heads of articles, they all try to read
-as little as possible.  This variable (default @code{4096}) specifies
+as little as possible.  This variable (default 4096) specifies
 the absolute max length the backends will try to read before giving up
 on finding a separator line between the head and the body.  If this
 variable is @code{nil}, there is no upper read bound.  If it is
 @code{t}, the backends won't try to read the articles piece by piece,
 but read the entire articles.  This makes sense with some versions of
 @code{ange-ftp}.
+@item nnheader-head-chop-length
+@vindex nnheader-head-chop-length
+This variable says how big a piece of each article to read when doing
+the operation described above.
 @item nnheader-file-name-translation-alist
 @vindex nnheader-file-name-translation-alist
 @cindex file names
 @cindex illegal characters in file names
 Ol' Charles Reznikoff said it pretty well, so I leave the floor to him:
 @quotation
 @strong{Te Deum}
 @sp 1
 Not because of victories @*
 I sing,@*
 having none,@*
 but for the common sunshine,@*
 the breeze,@*
 the largess of the spring.
 @sp 1
 Not for victory@*
 but for the day's work done@*
 as well as I was able;@*
 not for a seat upon the dais@*
 @file{http://www.ifi.uio.no/~larsi/}.  This is also the primary
 distribution point for the new and spiffy versions of Gnus, and is known
 as The Site That Destroys Newsrcs And Drives People Mad.
 During the first extended alpha period of development, the new Gnus was
-called ``(ding) Gnus''.  @dfn{(ding)}, is, of course, short for
+called ``(ding) Gnus''.  @dfn{(ding)} is, of course, short for
 @dfn{ding is not Gnus}, which is a total and utter lie, but who cares?
 (Besides, the ``Gnus'' in this abbreviation should probably be
 pronounced ``news'' as @sc{Umeda} intended, which makes it a more
 appropriate name, don't you think?)
 spunky name, we decided that the name was @emph{too} spunky, so we
 renamed it back again to ``Gnus''.  But in mixed case.  ``Gnus'' vs.
 ``@sc{gnus}''.  New vs. old.
 The first ``proper'' release of Gnus 5 was done in November 1995 when it
-was included in the Emacs 19.30 distribution.
+was included in the Emacs 19.30 distribution (132 (ding) Gnus releases
+plus 15 Gnus 5.0 releases).
-In May 1996 the next Gnus generation (aka.  ``September Gnus'') was
-released under the name ``Gnus 5.2''.
+In May 1996 the next Gnus generation (aka. ``September Gnus'' (after 99
+releases)) was released under the name ``Gnus 5.2'' (40 releases).
+On July 28th 1996 work on Red Gnus was begun, and it was released on
+January 25th 1997 (after 84 releases) as ``Gnus 5.4''.
+If you happen upon a version of Gnus that has a name that is prefixed --
+``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'' --
+don't panic.  Don't let it know that you're frightened.  Back away.
+Slowly.  Whatever you do, don't run.  Walk away, calmly, until you're
+out of its reach.  Find a proper released version of Gnus and snuggle up
+to that instead.
 @menu
 * Why?::                What's the point of Gnus?
 * Compatibility::       Just how compatible is Gnus with @sc{gnus}?
 * Conformity::          Gnus tries to conform to all standards.
 This is considered to be a ``vanity header'', while I consider it to be
 consumer information.  After seeing so many badly formatted articles
 coming from @code{tin} and @code{Netscape} I know not to use either of
 those for posting articles.  I would not have known that if it wasn't
 for the @code{X-Newsreader} header.
-@item References
-Gnus does line breaking on this header.  I infer from RFC1036 that being
-conservative in what you output is not creating 5000-character lines, so
-it seems like a good idea to me.  However, this standard-to-be says that
-whitespace in the @code{References} header is to be preserved, so...  It
-doesn't matter one way or the other to Gnus, so if somebody tells me
-what The Way is, I'll change it.  Or not.
 @end table
 @end table
 If you ever notice Gnus acting non-compliantly with regards to the texts
 Gnus should work on :
 @itemize @bullet
 @item
-Emacs 19.30 and up.
+Emacs 19.32 and up.
 @item
-XEmacs 19.13 and up.
+XEmacs 19.14 and up.
 @item
-Mule versions based on Emacs 19.30 and up.
+Mule versions based on Emacs 19.32 and up.
 @end itemize
 Gnus will absolutely not work on any Emacsen older than that.  Not
 reliably, at least.
-There are some vague differences between Gnus on the various platforms:
+There are some vague differences between Gnus on the various
+platforms---XEmacs features more graphics (a logo and a toolbar)---but
-@itemize @bullet
+other than that, things should look pretty much the same under all
+Emacsen.
-@item
-The mouse-face on Gnus lines under Emacs and Mule is delimited to
-certain parts of the lines while they cover the entire line under
-XEmacs.
-@item
-The same with current-article marking---XEmacs puts an underline under
-the entire summary line while Emacs and Mule are nicer and kinder.
-@item
-XEmacs features more graphics---a logo and a toolbar.
-@item
-Citation highlighting us better under Emacs and Mule than under XEmacs.
-@item
-Emacs 19.26-19.28 have tangible hidden headers, which can be a bit
-confusing.
-@end itemize
 @node Contributors
 @subsection Contributors
 @cindex contributors
 I would like to take this opportunity to thank the Academy for...  oops,
 wrong show.
 @itemize @bullet
-@item Masanobu @sc{Umeda}
+@item
-The writer of the original @sc{gnus}.
+Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
-@item Per Abrahamsen
+@item
-Custom, scoring, highlighting and @sc{soup} code (as well as numerous
+Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
-other things).
+well as numerous other things).
-@item Luis Fernandes
+@item
-Design and graphics.
+Luis Fernandes---design and graphics.
-@item Wes Hardaker
+@item
-@file{gnus-picon.el} and the manual section on @dfn{picons}
+Erik Naggum---help, ideas, support, code and stuff.
-(@pxref{Picons}).
+@item
-@item Brad Miller
+Wes Hardaker---@file{gnus-picon.el} and the manual section on
-@file{gnus-gl.el} and the GroupLens manual section (@pxref{GroupLens}).
+@dfn{picons} (@pxref{Picons}).
-@item Sudish Joseph
+@item
-Innumerable bug fixes.
+Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
+(@pxref{GroupLens}).
-@item Ilja Weis
-@file{gnus-topic.el}.
+@item
+Sudish Joseph---innumerable bug fixes.
-@item Steven L. Baur
-Lots and lots of bugs detections and fixes.
+@item
+Ilja Weis---@file{gnus-topic.el}.
-@item Vladimir Alexiev
-The refcard and reference booklets.
+@item
+Steven L. Baur---lots and lots and lots of bugs detections and fixes.
-@item Felix Lee & JWZ
-I stole some pieces from the XGnus distribution by Felix Lee and JWZ.
+@item
+Vladimir Alexiev---the refcard and reference booklets.
-@item Scott Byer
-@file{nnfolder.el} enhancements & rewrite.
+@item
+Felix Lee & Jamie Zawinsky---I stole some pieces from the XGnus
-@item Peter Mutsaers
+distribution by Felix Lee and JWZ.
-Orphan article scoring code.
+@item
-@item Ken Raeburn
+Scott Byer---@file{nnfolder.el} enhancements & rewrite.
-POP mail support.
+@item
-@item Hallvard B Furuseth
+Peter Mutsaers---orphan article scoring code.
-Various bits and pieces, especially dealing with .newsrc files.
+@item
-@item Brian Edmonds
+Ken Raeburn---POP mail support.
-@file{gnus-bbdb.el}.
+@item
-@item Ricardo Nassif and Mark Borges
+Hallvard B Furuseth---various bits and pieces, especially dealing with
-Proof-reading.
+.newsrc files.
-@item Kevin Davidson
+@item
-Came up with the name @dfn{ding}, so blame him.
+Brian Edmonds---@file{gnus-bbdb.el}.
+@item
+David Moore---rewrite of @file{nnvirtual.el} and many other things.
+@item
+Ricardo Nassif, Mark Borges, and Jost Krieger---proof-reading.
+@item
+Kevin Davidson---came up with the name @dfn{ding}, so blame him.
+@item
+Fran�ois Pinard---many, many interesting and thorough bug reports.
 @end itemize
-Peter Arius, Stainless Steel Rat, Ulrik Dickow, Jack Vinson, Daniel
+The following people have contributed many patches and suggestions:
-Quinlan, Frank D. Cringle, Geoffrey T. Dairiki, Fabrice Popineau and
-Andrew Eskilsson have all contributed code and suggestions.
+Christopher Davis,
+Andrew Eskilsson,
+Kai Grossjohann,
+David K�gedal,
+Richard Pieri,
+Fabrice Popineau,
+Daniel Quinlan,
+Jason L. Tibbitts, III,
+and
+Jack Vinson.
+Also thanks to the following for patches and stuff:
+Peter Arius,
+Marc Auslander,
+Chris Bone,
+Mark Borges,
+Lance A. Brown,
+Kees de Bruin,
+Martin Buchholz,
+Kevin Buhr,
+Alastair Burt,
+Joao Cachopo,
+Massimo Campostrini,
+Michael R. Cook,
+Glenn Coombs,
+Frank D. Cringle,
+Geoffrey T. Dairiki,
+Andre Deparade,
+Ulrik Dickow,
+Dave Disser,
+Joev Dubach,
+Paul Eggert,
+Michael Ernst,
+Luc Van Eycken,
+Sam Falkner,
+Paul Franklin,
+David S. Goldberg,
+D. Hall,
+Magnus Hammerin,
+Raja R. Harinath,
+Hisashige Kenji, @c Hisashige
+Marc Horowitz,
+Fran�ois Felix Ingrand,
+Ishikawa Ichiro, @c Ishikawa
+Lee Iverson,
+Rajappa Iyer,
+Randell Jesup,
+Fred Johansen,
+Greg Klanderman,
+Peter Skov Knudsen,
+Shuhei Kobayashi, @c Kobayashi
+Thor Kristoffersen,
+Jens Lautenbacher,
+Carsten Leonhardt,
+Christian Limpach,
+Markus Linnala,
+Dave Love,
+Tonny Madsen,
+Shlomo Mahlab,
+Nat Makarevitch,
+Timo Metzemakers,
+Richard Mlynarik,
+Lantz Moore,
+Morioka Tomohiko, @c Morioka
+Erik Toubro Nielsen,
+Hrvoje Niksic,
+Andy Norman,
+C. R. Oldham,
+Alexandre Oliva,
+Ken Olstad,
+Masaharu Onishi, @c Onishi
+Hideki Ono, @c Ono
+William Perry,
+Stephen Peters,
+Ulrich Pfeifer,
+John McClary Prevost,
+Colin Rafferty,
+Bart Robinson,
+Jason Rumney,
+Loren Schall,
+Dan Schmidt,
+Ralph Schleicher,
+Randal L. Schwartz,
+Danny Siu,
+Paul D. Smith,
+Jeff Sparkes,
+Michael Sperber,
+Richard Stallman,
+Greg Stark,
+Paul Stodghill,
+Kurt Swanson,
+Samuel Tardieu,
+Teddy,
+Chuck Thompson,
+Philippe Troin,
+Jan Vroonhof,
+Barry A. Warsaw,
+Christoph Wedler,
+Joe Wells,
+and
+Katsumi Yamaoka. @c Yamaoka
+For a full overview of what each person has done, the ChangeLogs
+included in the Gnus alpha distributions should give ample reading
+(550kB and counting).
+Apologies to everybody that I've forgotten, of which there are many, I'm
+sure.
+Gee, that's quite a list of people.  I guess that must mean that there
+actually are people who are using Gnus.  Who'd'a thunk it!
 @node New Features
 @subsection New Features
 @cindex new features
+@menu
+* ding Gnus::          New things in Gnus 5.0/5.1, the first new Gnus.
+* September Gnus::     The Thing Formally Known As Gnus 5.3/5.3.
+* Red Gnus::           Third time best---Gnus 5.4/5.5.
+@end menu
+These lists are, of course, just @emph{short} overviews of the
+@emph{most} important new features.  No, really.  There are tons more.
+Yes, we have feeping creaturism in full effect.
+@node ding Gnus
+@subsubsection (ding) Gnus
+New features in Gnus 5.0/5.1:
 @itemize @bullet
 @item
 The look of all buffers can be changed by setting format-like variables
 @item
 You can click on buttons instead of using the keyboard
 (@pxref{Buttons}).
-@item
-Gnus can use NoCeM files to weed out spam (@pxref{NoCeM}).
 @end itemize
-This is, of course, just a @emph{short} overview of the @emph{most}
-important new features.  No, really.  There are tons more.  Yes, we have
+@node September Gnus
-feeping creaturism in full effect, but nothing too gratuitous, I would
+@subsubsection September Gnus
-hope.
+New features in Gnus 5.2/5.3:
+@itemize @bullet
+@item
+A new message composition mode is used.  All old customization variables
+for @code{mail-mode}, @code{rnews-reply-mode} and @code{gnus-msg} are
+now obsolete.
+@item
+Gnus is now able to generate @dfn{sparse} threads---threads where
+missing articles are represented by empty nodes (@pxref{Customizing
+Threading}).
+@lisp
+(setq gnus-build-sparse-threads 'some)
+@end lisp
+@item
+Outgoing articles are stored on a special archive server
+(@pxref{Archived Messages}).
+@item
+Partial thread regeneration now happens when articles are
+referred.
+@item
+Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
+@item
+Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
+@item
+A @code{trn}-line tree buffer can be displayed (@pxref{Tree Display}).
+@lisp
+(setq gnus-use-trees t)
+@end lisp
+@item
+An @code{nn}-like pick-and-read minor mode is available for the summary
+buffers (@pxref{Pick and Read}).
+@lisp
+(add-hook 'gnus-summary-mode-hook 'gnus-pick-mode)
+@end lisp
+@item
+In binary groups you can use a special binary minor mode (@pxref{Binary
+Groups}).
+@item
+Groups can be grouped in a folding topic hierarchy (@pxref{Group
+Topics}).
+@lisp
+(add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
+@end lisp
+@item
+Gnus can re-send and bounce mail (@pxref{Summary Mail Commands}).
+@item
+Groups can now have a score, and bubbling based on entry frequency
+is possible (@pxref{Group Score}).
+@lisp
+(add-hook 'gnus-summary-exit-hook 'gnus-summary-bubble-group)
+@end lisp
+@item
+Groups can be process-marked, and commands can be performed on
+groups of groups (@pxref{Marking Groups}).
+@item
+Caching is possible in virtual groups.
+@item
+@code{nndoc} now understands all kinds of digests, mail boxes, rnews
+news batches, ClariNet briefs collections, and just about everything
+else (@pxref{Document Groups}).
+@item
+Gnus has a new backend (@code{nnsoup}) to create/read SOUP packets
+(@pxref{SOUP}).
+@item
+The Gnus cache is much faster.
+@item
+Groups can be sorted according to many criteria (@pxref{Sorting
+Groups}).
+@item
+New group parameters have been introduced to set list-address and
+expiry times (@pxref{Group Parameters}).
+@item
+All formatting specs allow specifying faces to be used
+(@pxref{Formatting Fonts}).
+@item
+There are several more commands for setting/removing/acting on process
+marked articles on the @kbd{M P} submap (@pxref{Setting Process Marks}).
+@item
+The summary buffer can be limited to show parts of the available
+articles based on a wide range of criteria.  These commands have been
+bound to keys on the @kbd{/} submap (@pxref{Limiting}).
+@item
+Articles can be made persistent with the @kbd{*} command
+(@pxref{Persistent Articles}).
+@item
+All functions for hiding article elements are now toggles.
+@item
+Article headers can be buttonized (@pxref{Article Washing}).
+@lisp
+(add-hook 'gnus-article-display-hook
+'gnus-article-add-buttons-to-head)
+@end lisp
+@item
+All mail backends support fetching articles by @code{Message-ID}.
+@item
+Duplicate mail can now be treated properly (@pxref{Duplicates}).
+@item
+All summary mode commands are available directly from the article
+buffer (@pxref{Article Keymap}).
+@item
+Frames can be part of @code{gnus-buffer-configuration} (@pxref{Windows
+Configuration}).
+@item
+Mail can be re-scanned by a daemonic process (@pxref{Daemons}).
+@item
+Gnus can make use of NoCeM files to weed out spam (@pxref{NoCeM}).
+@lisp
+(setq gnus-use-nocem t)
+@end lisp
+@item
+Groups can be made permanently visible (@pxref{Listing Groups}).
+@lisp
+(setq gnus-permanently-visible-groups "^nnml:")
+@end lisp
+@item
+Many new hooks have been introduced to make customizing easier.
+@item
+Gnus respects the @code{Mail-Copies-To} header.
+@item
+Threads can be gathered by looking at the @code{References} header
+(@pxref{Customizing Threading}).
+@lisp
+(setq gnus-summary-thread-gathering-function
+'gnus-gather-threads-by-references)
+@end lisp
+@item
+Read articles can be stored in a special backlog buffer to avoid
+refetching (@pxref{Article Backlog}).
+@lisp
+(setq gnus-keep-backlog 50)
+@end lisp
+@item
+A clean copy of the current article is always stored in a separate
+buffer to allow easier treatment.
+@item
+Gnus can suggest where to save articles (@pxref{Saving Articles}).
+@item
+Gnus doesn't have to do as much prompting when saving (@pxref{Saving
+Articles}).
+@lisp
+(setq gnus-prompt-before-saving t)
+@end lisp
+@item
+@code{gnus-uu} can view decoded files asynchronously while fetching
+articles (@pxref{Other Decode Variables}).
+@lisp
+(setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
+@end lisp
+@item
+Filling in the article buffer now works properly on cited text
+(@pxref{Article Washing}).
+@item
+Hiding cited text adds buttons to toggle hiding, and how much
+cited text to hide is now customizable (@pxref{Article Hiding}).
+@lisp
+(setq gnus-cited-lines-visible 2)
+@end lisp
+@item
+Boring headers can be hidden (@pxref{Article Hiding}).
+@lisp
+(add-hook 'gnus-article-display-hook
+'gnus-article-hide-boring-headers t)
+@end lisp
+@item
+Default scoring values can now be set from the menu bar.
+@item
+Further syntax checking of outgoing articles have been added.
+@end itemize
+@node Red Gnus
+@subsubsection Red Gnus
+New features in Gnus 5.4/5.5:
+@itemize @bullet
+@item
+@file{nntp.el} has been totally rewritten in an asynchronous fashion.
+@item
+Article prefetching functionality has been moved up into
+Gnus (@pxref{Asynchronous Fetching}).
+@item
+Scoring can now be performed with logical operators like @code{and},
+@code{or}, @code{not}, and parent redirection (@pxref{Advanced
+Scoring}).
+@item
+Article washing status can be displayed in the
+article mode line (@pxref{Misc Article}).
+@item
+@file{gnus.el} has been split into many smaller files.
+@item
+Suppression of duplicate articles based on Message-ID can be done
+(@pxref{Duplicate Suppression}).
+@lisp
+(setq gnus-suppress-duplicates t)
+@end lisp
+@item
+New variables for specifying what score and adapt files are to be
+considered home score and adapt files (@pxref{Home Score File}).
+@item
+@code{nndoc} was rewritten to be easily extendable (@pxref{Document
+Server Internals}).
+@item
+Groups can inherit group parameters from parent topics (@pxref{Topic
+Parameters}).
+@item
+Article editing has been revamped and is now actually usable.
+@item
+Signatures can be recognized in more intelligent fashions
+(@pxref{Article Signature}).
+@item
+Summary pick mode has been made to look more @code{nn}-like.  Line
+numbers are displayed and the @kbd{.} command can be used to pick
+articles (@code{Pick and Read}).
+@item
+Commands for moving the @file{.newsrc.eld} from one server to
+another have been added (@pxref{Changing Servers}).
+@item
+A way to specify that ``uninteresting'' fields be suppressed when
+generating lines in buffers (@pxref{Advanced Formatting}).
+@item
+Several commands in the group buffer can be undone with @kbd{M-C-_}
+(@pxref{Undo}).
+@item
+Scoring can be done on words using the new score type @code{w}
+(@pxref{Score File Format}).
+@item
+Adaptive scoring can be done on a Subject word-by-word basis
+(@pxref{Adaptive Scoring}).
+@lisp
+(setq gnus-use-adaptive-scoring '(word))
+@end lisp
+@item
+Scores can be decayed (@pxref{Score Decays}).
+@lisp
+(setq gnus-decay-scores t)
+@end lisp
+@item
+Scoring can be performed using a regexp on the Date header.  The Date is
+normalized to compact ISO 8601 format first (@pxref{Score File Format}).
+@item
+A new command has been added to remove all data on articles from
+the native server (@pxref{Changing Servers}).
+@item
+A new command for reading collections of documents
+(@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{M-C-d}
+(@pxref{Really Various Summary Commands}).
+@item
+Process mark sets can be pushed and popped (@pxref{Setting Process
+Marks}).
+@item
+A new mail-to-news backend makes it possible to post even when the NNTP
+server doesn't allow posting (@pxref{Mail-To-News Gateways}).
+@item
+A new backend for reading searches from Web search engines
+(@dfn{DejaNews}, @dfn{Alta Vista}, @dfn{InReference}) has been added
+(@pxref{Web Searches}).
+@item
+Groups inside topics can now be sorted using the standard sorting
+functions, and each topic can be sorted independently (@pxref{Topic
+Sorting}).
+@item
+Subsets of the groups can be sorted independently (@code{Sorting
+Groups}).
+@item
+Cached articles can be pulled into the groups (@pxref{Summary Generation
+Commands}).
+@item
+Score files are now applied in a more reliable order (@pxref{Score
+Variables}).
+@item
+Reports on where mail messages end up can be generated (@pxref{Splitting
+Mail}).
+@item
+More hooks and functions have been added to remove junk from incoming
+mail before saving the mail (@pxref{Washing Mail}).
+@item
+Emphasized text can be properly fontisized:
+@lisp
+(add-hook 'gnus-article-display-hook 'gnus-article-emphasize)
+@end lisp
+@end itemize
 @node Newest Features
 @subsection Newest Features
 @cindex todo
 @itemize @bullet
 @item
 Native @sc{mime} support is something that should be done.
 @item
-A better and simpler method for specifying mail composing methods.
-@item
-Allow posting through mail-to-news gateways.
-@item
 Really do unbinhexing.
 @end itemize
 And much, much, much more.  There is more to come than has already been
 implemented.  (But that's always true, isn't it?)
-@code{<URL:http://www.ifi.uio.no/~larsi/sgnus/todo>} is where the actual
+@file{<URL:http://www.ifi.uio.no/~larsi/rgnus/todo>} is where the actual
 up-to-the-second todo list is located, so if you're really curious, you
 could point your Web browser over that-a-way.
+@iftex
+@node The Manual
+@section The Manual
+@cindex colophon
+@cindex manual
+This manual was generated from a TeXinfo file and then run through
+either @code{texi2dvi}
+@iflatex
+or my own home-brewed TeXinfo to \LaTeX\ transformer,
+and then run through @code{latex} and @code{dvips}
+@end iflatex
+to get what you hold in your hands now.
+The following conventions have been used:
+@enumerate
+@item
+This is a @samp{string}
+@item
+This is a @kbd{keystroke}
+@item
+This is a @file{file}
+@item
+This is a @code{symbol}
+@end enumerate
+So if I were to say ``set @code{flargnoze} to @samp{yes}'', that would
+mean:
+@lisp
+(setq flargnoze "yes")
+@end lisp
+If I say ``set @code{flumphel} to @code{yes}'', that would mean:
+@lisp
+(setq flumphel 'yes)
+@end lisp
+@samp{yes} and @code{yes} are two @emph{very} different things---don't
+ever get them confused.
+@iflatex
+@c @head
+Of course, everything in this manual is of vital interest, so you should
+read it all.  Several times.  However, if you feel like skimming the
+manual, look for that gnu head you should see in the margin over
+there---it means that what's being discussed is of more importance than
+the rest of the stuff.  (On the other hand, if everything is infinitely
+important, how can anything be more important than that?  Just one more
+of the mysteries of this world, I guess.)
+@end iflatex
+@end iftex
 @node Terminology
 @section Terminology
 Secondary backends are somewhere half-way between being native and being
 foreign, but they mostly act like they are native.
 @item article
 @cindex article
-A nessage that has been posted as news.
+A message that has been posted as news.
 @item mail message
 @cindex mail message
 A message that has been mailed.
 is rather large, as you might surmise.
 @item bogus groups
 @cindex bogus groups
 A group that exists in the @file{.newsrc} file, but isn't known to the
-server (i. e.,  it isn't in the active file), is a @emph{bogus group}.
+server (i.e.,  it isn't in the active file), is a @emph{bogus group}.
 This means that the group probably doesn't exist (any more).
 @item server
 @cindex server
 A machine than one can connect to and get news (or mail) from.
 server parameters.
 @item virtual server
 @cindex virtual server
 A named select method.  Since a select methods defines all there is to
-know about connecting to a (physical) server, taking the who things as a
+know about connecting to a (physical) server, taking the things as a
 whole is a virtual server.
+@item washing
+@cindex washing
+Taking a buffer and running it through a filter of some sort.  The
+result will (more often than not) be cleaner and more pleasing than the
+original.
+@item ephemeral groups
+@cindex ephemeral groups
+Most groups store data on what articles you have read.  @dfn{Ephemeral}
+groups are groups that will have no data stored---when you exit the
+group, it'll disappear into the aether.
+@item solid groups
+@cindex solid groups
+This is the opposite of ephemeral groups.  All groups listed in the
+group buffer are solid groups.
+@item sparse articles
+@cindex sparse articles
+These are article placeholders shown in the summary buffer when
+@code{gnus-build-sparse-threads} has been switched on.
 @end table
 @node Customization
 @table @code
 @item gnus-read-active-file
 Set this to @code{nil}, which will inhibit Gnus from requesting the
 entire active file from the server.  This file is often v.  large.  You
-also have to set @code{gnus-check-new-news} and
+also have to set @code{gnus-check-new-newsgroups} and
 @code{gnus-check-bogus-newsgroups} to @code{nil} to make sure that Gnus
 doesn't suddenly decide to fetch the active file anyway.
 @item gnus-nov-is-evil
 This one has to be @code{nil}.  If not, grabbing article headers from
 flee}, you have some old @file{.el} files lying around.  Delete these.
 @item
 Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
 how-to.
+@item
+@vindex max-lisp-eval-depth
+Gnus works on many recursive structures, and in some extreme (and very
+rare) cases Gnus may recurse down ``too deeply'' and Emacs will beep at
+you.  If this happens to you, set @code{max-lisp-eval-depth} to 500 or
+something like that.
 @end enumerate
 If all else fails, report the problem as a bug.
 @cindex bugs
 mail you and ask for more info, and everything takes more time.
 If the problem you're seeing is very visual, and you can't quite explain
 it, copy the Emacs window to a file (with @code{xwd}, for instance), put
 it somewhere it can be reached, and include the URL of the picture in
-the bug report.a
+the bug report.
 If you just need help, you are better off asking on
 @samp{gnu.emacs.gnus}.  I'm not very helpful.
 @cindex gnu.emacs.gnus
 You can also ask on the ding mailing list---@samp{ding@@ifi.uio.no}.
 Write to @samp{ding-request@@ifi.uio.no} to subscribe.
 @node A Programmers Guide to Gnus
-@section A Programmer's Guide to Gnus
+@section A Programmer@'s Guide to Gnus
 It is my hope that other people will figure out smart stuff that Gnus
 can do, and that other people will write those smart things as well.  To
 facilitate that I thought it would be a good idea to describe the inner
 workings of Gnus.  And some of the not-so-inner workings, while I'm at
 always check whether are present before attempting to call.
 All these functions are expected to return data in the buffer
 @code{nntp-server-buffer} (@samp{ *nntpd*}), which is somewhat
 unfortunately named, but we'll have to live with it.  When I talk about
-``resulting data'', I always refer to the data in that buffer.  When I
+@dfn{resulting data}, I always refer to the data in that buffer.  When I
-talk about ``return value'', I talk about the function value returned by
+talk about @dfn{return value}, I talk about the function value returned by
-the function call.
+the function call.  Functions that fail should return @code{nil} as the
+return value.
 Some backends could be said to be @dfn{server-forming} backends, and
 some might be said to not be.  The latter are backends that generally
 only operate on one group at a time, and have no concept of ``server''
 -- they have a group, and they deliver info on that group and nothing
 @cindex @code{nnchoke}
 @menu
 * Required Backend Functions::        Functions that must be implemented.
 * Optional Backend Functions::        Functions that need not be implemented.
+* Error Messaging::                   How to get messages and report errors.
 * Writing New Backends::              Extending old backends.
+* Hooking New Backends Into Gnus::    What has to be done on the Gnus end.
+* Mail-like Backends::                Some tips on mail backends.
 @end menu
 @node Required Backend Functions
 @subsubsection Required Backend Functions
 group and article numbers are when fetching articles by
 @code{Message-ID}.  If this isn't possible, @code{t} should be returned
 on successful article retrievement.
-@item (nnchoke-open-group GROUP &optional SERVER)
+@item (nnchoke-request-group GROUP &optional SERVER FAST)
-Make @var{group} the current group.
-There should be no data returned by this function.
-@item (nnchoke-request-group GROUP &optional SERVER)
 Get data on @var{group}.  This function also has the side effect of
 making @var{group} the current group.
+If @var{FAST}, don't bother to return useful data, just make @var{group}
+the current group.
 Here's an example of some result data and a definition of the same:
 @example
 211 56 1000 1059 ifi.discussion
 @end example
-The first number is the status, which should be @code{211}.  Next is the
+The first number is the status, which should be 211.  Next is the
 total number of articles in the group, the lowest article number, the
 highest article number, and finally the group name.  Note that the total
 number of articles may be less than one might think while just
 considering the highest and lowest article numbers, but some articles
 may have been canceled.  Gnus just discards the total-number, so
 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
 A Gnus group info (@pxref{Group Info}) is handed to the backend for
 alterations.  This comes in handy if the backend really carries all the
 information (as is the case with virtual an imap groups).  This function
-may alter the info in any manner it sees fit, and should return the
+should destructively alter the info to suit its needs, and should return
-(altered) group info.  This function may alter the group info
+the (altered) group info.
-destructively, so no copying is needed before boogeying.
 There should be no result data from this function.
 @item (nnchoke-request-type GROUP &optional ARTICLE)
 summary buffer, for instance), Gnus has to know whether the article the
 user is following up is news or mail.  This function should return
 @code{news} if @var{article} in @var{group} is news, @code{mail} if it
 is mail and @code{unknown} if the type can't be decided.  (The
 @var{article} parameter is necessary in @code{nnvirtual} groups which
-might very well combine mail groups and news groups.)
+might very well combine mail groups and news groups.)  Both @var{group}
+and @var{article} may be @code{nil}.
 There should be no result data from this function.
 @item (nnchoke-request-update-mark GROUP ARTICLE MARK)
 would be nice, however, to keep things local if that's practical.
 There should be no result data from this function.
-@item (nnchoke-request-asynchronous GROUP &optional SERVER ARTICLES)
-This is a request to fetch articles asynchronously later.
-@var{articles} is an alist of @var{(article-number line-number)}.  One
-would generally expect that if one later fetches article number 4, for
-instance, some sort of asynchronous fetching of the articles after 4
-(which might be 5, 6, 7 or 11, 3, 909 depending on the order in that
-alist) would be fetched asynchronously, but that is left up to the
-backend.  Gnus doesn't care.
-There should be no result data from this function.
 @item (nnchoke-request-group-description GROUP &optional SERVER)
 The result data from this function should be a description of
 @var{group}.
 There should be no data returned.
 @end table
+@node Error Messaging
+@subsubsection Error Messaging
+@findex nnheader-report
+@findex nnheader-get-report
+The backends should use the function @code{nnheader-report} to report
+error conditions---they should not raise errors when they aren't able to
+perform a request.  The first argument to this function is the backend
+symbol, and the rest are interpreted as arguments to @code{format} if
+there are many of them, or just a string if there is one of them.
+This function always returns @code{nil}.
+@lisp
+(nnheader-report 'nnchoke "You did something totally bogus")
+(nnheader-report 'nnchoke "Could not request group %s" group)
+@end lisp
+Gnus, in turn, will call @code{nnheader-get-report} when it gets a
+@code{nil} back from a server, and this function returns the most
+recently reported message for the backend in question.  This function
+takes one argument---the server symbol.
+Internally, these function access @var{backend}@code{-status-string}, so
+the @code{nnchoke} backend will have its error message stored in
+@code{nnchoke-status-string}.
 @node Writing New Backends
 @subsubsection Writing New Backends
-The various backends share many similarities.  @code{nnml} is just like
+Many backends are quite similar.  @code{nnml} is just like
 @code{nnspool}, but it allows you to edit the articles on the server.
 @code{nnmh} is just like @code{nnml}, but it doesn't use an active file,
 and it doesn't maintain overview databases.  @code{nndir} is just like
 @code{nnml}, but it has no concept of ``groups'', and it doesn't allow
 editing articles.
 (nnoo-define-basics nndir)
 (deffoo nndir-open-server (server &optional defs)
 (setq nndir-directory
-	(or (cadr (assq 'nndir-directory defs))
+(or (cadr (assq 'nndir-directory defs))
-	    server))
+server))
 (unless (assq 'nndir-directory defs)
 (push `(nndir-directory ,server) defs))
 (push `(nndir-current-group
-	  ,(file-name-nondirectory (directory-file-name nndir-directory)))
+,(file-name-nondirectory (directory-file-name nndir-directory)))
-	defs)
+defs)
 (push `(nndir-top-directory
-	  ,(file-name-directory (directory-file-name nndir-directory)))
+,(file-name-directory (directory-file-name nndir-directory)))
-	defs)
+defs)
 (nnoo-change-server 'nndir server defs))
 (nnoo-map-functions nndir
 (nnml-retrieve-headers 0 nndir-current-group 0 0)
 (nnmh-request-article 0 nndir-current-group 0 0)
 nnmh-request-newgroups))
 (provide 'nndir)
 @end lisp
+@node Hooking New Backends Into Gnus
+@subsubsection Hooking New Backends Into Gnus
+@vindex gnus-valid-select-methods
+Having Gnus start using your new backend is rather easy---you just
+declare it with the @code{gnus-declare-backend} functions.  This will
+enter the backend into the @code{gnus-valid-select-methods} variable.
+@code{gnus-declare-backend} takes two parameters---the backend name and
+an arbitrary number of @dfn{abilities}.
+Here's an example:
+@lisp
+(gnus-declare-backend "nnchoke" 'mail 'respool 'address)
+@end lisp
+The abilities can be:
+@table @code
+@item mail
+This is a mailish backend---followups should (probably) go via mail.
+@item post
+This is a newsish backend---followups should (probably) go via news.
+@item post-mail
+This backend supports both mail and news.
+@item none
+This is neither a post or mail backend---it's something completely
+different.
+@item respool
+It supports respooling---or rather, it is able to modify its source
+articles and groups.
+@item address
+The name of the server should be in the virtual server name.  This is
+true for almost all backends.
+@item prompt-address
+The user should be prompted for an address when doing commands like
+@kbd{B} in the group buffer.  This is true for backends like
+@code{nntp}, but not @code{nnmbox}, for instance.
+@end table
+@node Mail-like Backends
+@subsubsection Mail-like Backends
+One of the things that separate the mail backends from the rest of the
+backends is the heavy dependence by the mail backends on common
+functions in @file{nnmail.el}.  For instance, here's the definition of
+@code{nnml-request-scan}:
+@lisp
+(deffoo nnml-request-scan (&optional group server)
+(setq nnml-article-file-alist nil)
+(nnmail-get-new-mail 'nnml 'nnml-save-nov nnml-directory group))
+@end lisp
+It simply just calls @code{nnmail-get-new-mail} will a few parameters,
+and @code{nnmail} takes care of all the moving and splitting of the
+mail.
+This function takes four parameters.
+@table @var
+@item method
+This should be a symbol to designate which backend is responsible for
+the call.
+@item exit-function
+This function should be called after the splitting has been performed.
+@item temp-directory
+Where the temporary files should be stored.
+@item group
+This optional argument should be a group name if the splitting is to be
+performed for one group only.
+@end table
+@code{nnmail-get-new-mail} will call @var{backend}@code{-save-mail} to
+save each article.  @var{backend}@code{-active-number} will be called to
+find the article number assigned to this article.
+The function also uses the following variables:
+@var{backend}@code{-get-new-mail} (to see whether to get new mail for
+this backend); and @var{backend}@code{-group-alist} and
+@var{backend}@code{-active-file} to generate the new active file.
+@var{backend}@code{-group-alist} should be a group-active alist, like
+this:
+@example
+(("a-group" (1 . 10))
+("some-group" (34 . 39)))
+@end example
 @node Score File Syntax
 @subsection Score File Syntax
 corresponds to the @sc{nov} format in a mysterious fashion.  One could
 almost suspect that the author looked at the @sc{nov} specification and
 just shamelessly @emph{stole} the entire thing, and one would be right.
 @dfn{Header} is a severely overloaded term.  ``Header'' is used in
-RFC1036 to talk about lines in the head of an article (eg.,
+RFC1036 to talk about lines in the head of an article (e.g.,
 @code{From}).  It is used by many people as a synonym for
 ``head''---``the header and the body''.  (That should be avoided, in my
 opinion.)  And Gnus uses a format internally that it calls ``header'',
 which is what I'm talking about here.  This is a 9-element vector,
 basically, with each header (ouch) having one slot.
 @sc{gnus} introduced a concept that I found so useful that I've started
 using it a lot and have elaborated on it greatly.
 The question is simple: If you have a large amount of objects that are
 identified by numbers (say, articles, to take a @emph{wild} example)
-that you want to callify as being ``included'', a normal sequence isn't
+that you want to qualify as being ``included'', a normal sequence isn't
 very useful.  (A 200,000 length sequence is a bit long-winded.)
 The solution is as simple as the question: You just collapse the
 sequence.
 ((tick (15 . 19)) (replied 3 6 (19 . 3)))
 (nnml "")
 (auto-expire (to-address "ding@@ifi.uio.no")))
 @end example
-The first element is the group name as Gnus knows the group; the second
+The first element is the @dfn{group name}---as Gnus knows the group,
-is the group level; the third is the read articles in range format; the
+anyway.  The second element is the @dfn{subscription level}, which
-fourth is a list of article marks lists; the fifth is the select method;
+normally is a small integer.  The third element is a list of ranges of
-and the sixth contains the group parameters.
+read articles.  The fourth element is a list of lists of article marks
+of various kinds.  The fifth element is the select method (or virtual
+server, if you like).  The sixth element is a list of @dfn{group
+parameters}, which is what this section is about.
+Any of the last three elements may be missing if they are not required.
+In fact, the vast majority of groups will normally only have the first
+three elements, which saves quite a lot of cons cells.
 Here's a BNF definition of the group info format:
 @example
 info          = "(" group space level space read

Mercurial > hg > xemacs-beta

comparison man/gnus.texi @ 98:0d2f883870bc r20-1b1