This is ../info/gnus, produced by makeinfo version 4.6 from gnus.texi.

INFO-DIR-SECTION The Emacs editor and associated tools
START-INFO-DIR-ENTRY
* GNUS: (gnus).			The news reader GNUS.
END-INFO-DIR-ENTRY

   This file documents Gnus, the GNU Emacs newsreader.

   Copyright (C) 1995,96 Free Software Foundation, Inc.

   Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.

   Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided also
that the entire resulting derived work is distributed under the terms
of a permission notice identical to this one.

   Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions.


File: gnus,  Node: Windows Configuration,  Next: Compilation,  Prev: Formatting Variables,  Up: Various

Windows Configuration
=====================

No, there's nothing here about X, so be quiet.

   If `gnus-use-full-window' non-`nil', Gnus will delete all other
windows and occupy the entire Emacs screen by itself.  It is `t' by
default.

   `gnus-buffer-configuration' describes how much space each Gnus
buffer should be given.  Here's an excerpt of this variable:

     ((group (vertical 1.0 (group 1.0 point)
                           (if gnus-carpal (group-carpal 4))))
      (article (vertical 1.0 (summary 0.25 point)
                             (article 1.0))))

   This is an alist.  The "key" is a symbol that names some action or
other.  For instance, when displaying the group buffer, the window
configuration function will use `group' as the key.  A full list of
possible names is listed below.

   The "value" (i. e., the "split") says how much space each buffer
should occupy.  To take the `article' split as an example -

     (article (vertical 1.0 (summary 0.25 point)
                            (article 1.0)))

   This "split" says that the summary buffer should occupy 25% of upper
half of the screen, and that it is placed over the article buffer.  As
you may have noticed, 100% + 25% is actually 125% (yup, I saw y'all
reaching for that calculator there).  However, the special number `1.0'
is used to signal that this buffer should soak up all the rest of the
space available after the rest of the buffers have taken whatever they
need.  There should be only one buffer with the `1.0' size spec per
split.

   Point will be put in the buffer that has the optional third element
`point'.

   Here's a more complicated example:

     (article (vertical 1.0 (group 4)
                            (summary 0.25 point)
                            (if gnus-carpal (summary-carpal 4))
                            (article 1.0)))

   If the size spec is an integer instead of a floating point number,
then that number will be used to say how many lines a buffer should
occupy, not a percentage.

   If the "split" looks like something that can be `eval'ed (to be
precise--if the `car' of the split is a function or a subr), this split
will be `eval'ed.  If the result is non-`nil', it will be used as a
split.  This means that there will be three buffers if `gnus-carpal' is
`nil', and four buffers if `gnus-carpal' is non-`nil'.

   Not complicated enough for you?  Well, try this on for size:

     (article (horizontal 1.0
                  (vertical 0.5
                      (group 1.0)
                      (gnus-carpal 4))
                  (vertical 1.0
                      (summary 0.25 point)
                      (summary-carpal 4)
                      (article 1.0))))

   Whoops.  Two buffers with the mystery 100% tag.  And what's that
`horizontal' thingie?

   If the first element in one of the split is `horizontal', Gnus will
split the window horizontally, giving you two windows side-by-side.
Inside each of these strips you may carry on all you like in the normal
fashion.  The number following `horizontal' says what percentage of the
screen is to be given to this strip.

   For each split, there _must_ be one element that has the 100% tag.
The splitting is never accurate, and this buffer will eat any leftover
lines from the splits.

   To be slightly more formal, here's a definition of what a legal split
may look like:

     split       = frame | horizontal | vertical | buffer | form
     frame       = "(frame " size *split ")"
     horizontal  = "(horizontal " size *split ")"
     vertical    = "(vertical " size *split ")"
     buffer      = "(" buffer-name " " size *[ "point" ] ")"
     size        = number | frame-params
     buffer-name = group | article | summary ...

   The limitations are that the `frame' split can only appear as the
top-level split.  FORM should be an Emacs Lisp form that should return
a valid split.  We see that each split is fully recursive, and may
contain any number of `vertical' and `horizontal' splits.

   Finding the right sizes can be a bit complicated.  No window may be
less than `gnus-window-min-height' (default 2) characters high, and all
windows must be at least `gnus-window-min-width' (default 1) characters
wide.  Gnus will try to enforce this before applying the splits.  If
you want to use the normal Emacs window width/height limit, you can
just set these two variables to `nil'.

   If you're not familiar with Emacs terminology, `horizontal' and
`vertical' splits may work the opposite way of what you'd expect.
Windows inside a `horizontal' split are shown side-by-side, and windows
within a `vertical' split are shown above each other.

   If you want to experiment with window placement, a good tip is to
call `gnus-configure-frame' directly with a split.  This is the function
that does all the real work when splitting buffers.  Below is a pretty
nonsensical configuration with 5 windows; two for the group buffer and
three for the article buffer.  (I said it was nonsensical.)  If you
`eval' the statement below, you can get an idea of how that would look
straight away, without going through the normal Gnus channels.  Play
with it until you're satisfied, and then use `gnus-add-configuration'
to add your new creation to the buffer configuration list.

     (gnus-configure-frame
      '(horizontal 1.0
         (vertical 10
           (group 1.0)
           (article 0.3 point))
         (vertical 1.0
           (article 1.0)
           (horizontal 4
             (group 1.0)
             (article 10)))))

   You might want to have several frames as well.  No prob--just use the
`frame' split:

     (gnus-configure-frame
      '(frame 1.0
              (vertical 1.0
                        (summary 0.25 point)
                        (article 1.0))
              (vertical ((height . 5) (width . 15)
                         (user-position . t)
                         (left . -1) (top . 1))
                        (picon 1.0))))

   This split will result in the familiar summary/article window
configuration in the first (or "main") frame, while a small additional
frame will be created where picons will be shown.  As you can see,
instead of the normal `1.0' top-level spec, each additional split
should have a frame parameter alist as the size spec.  *Note Frame
Parameters: (elisp)Frame Parameters.

   Here's a list of all possible keys for `gnus-buffer-configuration':

   `group', `summary', `article', `server', `browse', `group-mail',
`summary-mail', `summary-reply', `info', `summary-faq', `edit-group',
`edit-server', `reply', `reply-yank', `followup', `followup-yank',
`edit-score'.

   Since the `gnus-buffer-configuration' variable is so long and
complicated, there's a function you can use to ease changing the config
of a single setting: `gnus-add-configuration'.  If, for instance, you
want to change the `article' setting, you could say:

     (gnus-add-configuration
      '(article (vertical 1.0
                    (group 4)
                    (summary .25 point)
                    (article 1.0))))

   You'd typically stick these `gnus-add-configuration' calls in your
`.gnus' file or in some startup hook - they should be run after Gnus
has been loaded.


File: gnus,  Node: Compilation,  Next: Mode Lines,  Prev: Windows Configuration,  Up: Various

Compilation
===========

Remember all those line format specification variables?
`gnus-summary-line-format', `gnus-group-line-format', and so on.  Now,
Gnus will of course heed whatever these variables are, but,
unfortunately, changing them will mean a quite significant slow-down.
(The default values of these variables have byte-compiled functions
associated with them, while the user-generated versions do not, of
course.)

   To help with this, you can run `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.


File: gnus,  Node: Mode Lines,  Next: Highlighting and Menus,  Prev: Compilation,  Up: Various

Mode Lines
==========

`gnus-updated-mode-lines' says what buffers should keep their mode
lines updated.  It is a list of symbols.  Supported symbols include
`group', `article', `summary', `server', `browse', and `tree'.  If the
corresponding symbol is present, Gnus will keep that mode line updated
with information that may be pertinent.  If this variable is `nil',
screen refresh may be quicker.

   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 mode lines, and therefore have to be cut off at some point.  The
`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 this
variable:

     (add-hook 'display-time-hook
               (lambda () (setq gnus-mode-non-string-length
                                (+ 21
                                   (if line-number-mode 5 0)
                                   (if column-number-mode 4 0)
                                   (length display-time-string)))))

   If this variable is `nil' (which is the default), the mode line
strings won't be chopped off, and they won't be padded either.


File: gnus,  Node: Highlighting and Menus,  Next: Buttons,  Prev: Mode Lines,  Up: Various

Highlighting and Menus
======================

The `gnus-visual' variable controls most of the prettifying Gnus
aspects.  If `nil', Gnus won't attempt to create menus or use fancy
colors or fonts.  This will also inhibit loading the `gnus-vis.el' file.

   This variable can be a list of visual properties that are enabled.
The following elements are legal, and are all included by default:

`group-highlight'
     Do highlights in the group buffer.

`summary-highlight'
     Do highlights in the summary buffer.

`article-highlight'
     Do highlights in the article buffer.

`highlight'
     Turn on highlighting in all buffers.

`group-menu'
     Create menus in the group buffer.

`summary-menu'
     Create menus in the summary buffers.

`article-menu'
     Create menus in the article buffer.

`browse-menu'
     Create menus in the browse buffer.

`server-menu'
     Create menus in the server buffer.

`score-menu'
     Create menus in the score buffers.

`menu'
     Create menus in all buffers.

   So if you only want highlighting in the article buffer and menus in
all buffers, you could say something like:

     (setq gnus-visual '(article-highlight menu))

   If you want only highlighting and no menus whatsoever, you'd say:

     (setq gnus-visual '(highlight))

   If `gnus-visual' is `t', highlighting and menus will be used in all
Gnus buffers.

   Other general variables that influence the look of all buffers
include:

`gnus-mouse-face'
     This is the face (i.e., font) used for mouse highlighting in Gnus.
     No mouse highlights will be done if `gnus-visual' is `nil'.

`gnus-display-type'
     This variable is symbol indicating the display type Emacs is
     running under.  The symbol should be one of `color', `grayscale' or
     `mono'.  If Gnus guesses this display attribute wrongly, either set
     this variable in your `~/.emacs' or set the resource
     `Emacs.displayType' in your `~/.Xdefaults'.

`gnus-background-mode'
     This is a symbol indicating the Emacs background brightness.  The
     symbol should be one of `light' or `dark'.  If Gnus guesses this
     frame attribute wrongly, either set this variable in your
     `~/.emacs' or set the resource `Emacs.backgroundMode' in your
     `~/.Xdefaults'.  `gnus-display-type'.

   There are hooks associated with the creation of all the different
menus:

`gnus-article-menu-hook'
     Hook called after creating the article mode menu.

`gnus-group-menu-hook'
     Hook called after creating the group mode menu.

`gnus-summary-menu-hook'
     Hook called after creating the summary mode menu.

`gnus-server-menu-hook'
     Hook called after creating the server mode menu.

`gnus-browse-menu-hook'
     Hook called after creating the browse mode menu.

`gnus-score-menu-hook'
     Hook called after creating the score mode menu.



File: gnus,  Node: Buttons,  Next: Daemons,  Prev: Highlighting and Menus,  Up: Various

Buttons
=======

Those new-fangled "mouse" contraptions is very popular with the young,
hep kids who don't want to learn the proper way to do things these
days.  Why, I remember way back in the summer of '89, when I was using
Emacs on a Tops 20 system.  Three hundred users on one single machine,
and every user was running Simula compilers.  Bah!

   Right.

   Well, you can make Gnus display bufferfuls of buttons you can click
to do anything by setting `gnus-carpal' to `t'.  Pretty simple, really.
Tell the chiropractor I sent you.

`gnus-carpal-mode-hook'
     Hook run in all carpal mode buffers.

`gnus-carpal-button-face'
     Face used on buttons.

`gnus-carpal-header-face'
     Face used on carpal buffer headers.

`gnus-carpal-group-buffer-buttons'
     Buttons in the group buffer.

`gnus-carpal-summary-buffer-buttons'
     Buttons in the summary buffer.

`gnus-carpal-server-buffer-buttons'
     Buttons in the server buffer.

`gnus-carpal-browse-buffer-buttons'
     Buttons in the browse buffer.

   All the `buttons' variables are lists.  The elements in these list
is either a cons cell where the car contains a text to be displayed and
the cdr contains a function symbol, or a simple string.


File: gnus,  Node: Daemons,  Next: NoCeM,  Prev: Buttons,  Up: Various

Daemons
=======

Gnus, being larger than any program ever written (allegedly), does lots
of strange stuff that you may wish to have done while you're not
present.  For instance, you may want it to check for new mail once in a
while.  Or you may want it to close down all connections to all servers
when you leave Emacs idle.  And stuff like that.

   Gnus will let you do stuff like that by defining various "handlers".
Each handler consists of three elements:  A FUNCTION, a TIME, and an
IDLE parameter.

   Here's an example of a handler that closes connections when Emacs has
been idle for thirty minutes:

     (gnus-demon-close-connections nil 30)

   Here's a handler that scans for PGP headers every hour when Emacs is
idle:

     (gnus-demon-scan-pgp 60 t)

   This TIME parameter and than IDLE parameter works together in a
strange, but wonderful fashion.  Basically, if IDLE is `nil', then the
function will be called every TIME minutes.

   If IDLE is `t', then the function will be called after TIME minutes
only if Emacs is idle.  So if Emacs is never idle, the function will
never be called.  But once Emacs goes idle, the function will be called
every TIME minutes.

   If IDLE is a number and TIME is a number, the function will be
called every TIME minutes only when Emacs has been idle for IDLE
minutes.

   If IDLE is a number and TIME is `nil', the function will be called
once every time Emacs has been idle for IDLE minutes.

   And if TIME is a string, it should look like `07:31', and the
function will then be called once every day somewhere near that time.
Modified by the IDLE parameter, of course.

   (When I say "minute" here, I really mean `gnus-demon-timestep'
seconds.  This is `60' by default.  If you change that variable, all
the timings in the handlers will be affected.)

   To set the whole thing in motion, though, you have to set
`gnus-use-demon' to `t'.

   So, if you want to add a handler, you could put something like this
in your `.gnus' file:

     (gnus-demon-add-handler 'gnus-demon-close-connections nil 30)

   Some ready-made functions to do this has been created:
`gnus-demon-add-nocem', `gnus-demon-add-disconnection', and
`gnus-demon-add-scanmail'.  Just put those functions in your `.gnus' if
you want those abilities.

   If you add handlers to `gnus-demon-handlers' directly, you should
run `gnus-demon-init' to make the changes take hold.  To cancel all
daemons, you can use the `gnus-demon-cancel' function.

   Note that adding daemons can be pretty naughty if you overdo it.
Adding functions that scan all news and mail from all servers every two
seconds is a sure-fire way of getting booted off any respectable
system.  So behave.


File: gnus,  Node: NoCeM,  Next: Picons,  Prev: Daemons,  Up: Various

NoCeM
=====

"Spamming" is posting the same article lots and lots of times.
Spamming is bad.  Spamming is evil.

   Spamming is usually canceled within a day or so by various
anti-spamming agencies.  These agencies usually also send out "NoCeM"
messages.  NoCeM is pronounced "no see-'em", and means what the name
implies--these are messages that make the offending articles, like, go
away.

   What use are these NoCeM messages if the articles are canceled
anyway?  Some sites do not honor cancel messages and some sites just
honor cancels from a select few people.  Then you may wish to make use
of the NoCeM messages, which are distributed in the `alt.nocem.misc'
newsgroup.

   Gnus can read and parse the messages in this group automatically, and
this will make spam disappear.

   There are some variables to customize, of course:

`gnus-use-nocem'
     Set this variable to `t' to set the ball rolling.  It is `nil' by
     default.

`gnus-nocem-groups'
     Gnus will look for NoCeM messages in the groups in this list.  The
     default is `("alt.nocem.misc" "news.admin.net-abuse.announce")'.

`gnus-nocem-issuers'
     There are many people issuing NoCeM messages.  This list says what
     people you want to listen to.  The default is `("Automoose-1"
     "clewis@ferret.ocunix.on.ca;" "jem@xpat.com;"
     "red@redpoll.mrfs.oh.us (Richard E. Depew)")'; fine, upstanding
     citizens all of them.

     Known despammers that you can put in this list include:

    `clewis@ferret.ocunix.on.ca;'
          Chris Lewis--Major Canadian despammer who has probably
          canceled more usenet abuse than anybody else.

    `Automoose-1'
          The CancelMoose[tm] on autopilot.  The CancelMoose[tm] is
          reputed to be Norwegian, and was the person(s) who invented
          NoCeM.

    `jem@xpat.com;'
          Jem--Korean despammer who is getting very busy these days.

    `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).

     You do not have to heed NoCeM messages from all these people--just
     the ones you want to listen to.

`gnus-nocem-directory'
     This is where Gnus will store its NoCeM cache files.  The default
     is `~/News/NoCeM/'.

`gnus-nocem-expiry-wait'
     The number of days before removing old NoCeM entries from the
     cache.  The default is 15.  If you make it shorter Gnus will be
     faster, but you might then see old spam.



File: gnus,  Node: Picons,  Next: Various Various,  Prev: NoCeM,  Up: Various

Picons
======

So...  You want to slow down your news reader even more!  This is a
good way to do so.  Its also a great way to impress people staring over
your shoulder as you read news.

* Menu:

* Picon Basics::           What are picons and How do I get them.
* Picon Requirements::     Don't go further if you aren't using XEmacs.
* Easy Picons::            Displaying Picons -- the easy way.
* Hard Picons::            The way you should do it.  You'll learn something.
* Picon Configuration::    Other variables you can trash/tweak/munge/play with.


File: gnus,  Node: Picon Basics,  Next: Picon Requirements,  Up: Picons

Picon Basics
------------

What are Picons?  To quote directly from the Picons Web site
(`http://www.cs.indiana.edu/picons/ftp/index.html'):

     "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
     e-mail address can be found.  Besides users and domains, there are
     picon databases for Usenet newsgroups and weather forecasts.  The
     picons are in either monochrome `XBM' format or color `XPM' and
     `GIF' formats.

   Please see the above mentioned web site for instructions on obtaining
and installing the picons databases, or the following ftp site:
`http://www.cs.indiana.edu/picons/ftp/index.html'.

   Gnus expects picons to be installed into a location pointed to by
`gnus-picons-database'.


File: gnus,  Node: Picon Requirements,  Next: Easy Picons,  Prev: Picon Basics,  Up: Picons

Picon Requirements
------------------

To use have Gnus display Picons for you, you must be running XEmacs
19.13 or greater since all other versions of Emacs aren't yet able to
display images.

   Additionally, you must have `xpm' support compiled into XEmacs.

   If you want to display faces from `X-Face' headers, you must have
the `netpbm' utilities installed, or munge the
`gnus-picons-convert-x-face' variable to use something else.


File: gnus,  Node: Easy Picons,  Next: Hard Picons,  Prev: Picon Requirements,  Up: Picons

Easy Picons
-----------

To enable displaying picons, simply put the following line in your
`~/.gnus' file and start Gnus.

     (setq gnus-use-picons t)
     (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
     (add-hook 'gnus-summary-prepare-hook 'gnus-group-display-picons t)
     (add-hook 'gnus-article-display-hook 'gnus-picons-article-display-x-face)


File: gnus,  Node: Hard Picons,  Next: Picon Configuration,  Prev: Easy Picons,  Up: Picons

Hard Picons
-----------

Gnus can display picons for you as you enter and leave groups and
articles.  It knows how to interact with three sections of the picons
database.  Namely, it can display the picons newsgroup pictures,
author's face picture(s), and the authors domain.  To enable this
feature, you need to first decide where to display them.

`gnus-picons-display-where'
     Where the picon images should be displayed.  It is `picons' by
     default (which by default maps to the buffer `*Picons*').  Other
     valid places could be `article', `summary', or `"*scratch*"' for
     all I care.  Just make sure that you've made the buffer visible
     using the standard Gnus window configuration routines - *Note
     Windows Configuration::.


   Note: If you set `gnus-use-picons' to `t', it will set up your
window configuration for you to include the `picons' buffer.

   Now that you've made that decision, you need to add the following
functions to the appropriate hooks so these pictures will get displayed
at the right time.

`gnus-article-display-picons'
     Looks up and display the picons for the author and the author's
     domain in the `gnus-picons-display-where' buffer.  Should be added
     to the `gnus-article-display-hook'.

`gnus-group-display-picons'
     Displays picons representing the current group.  This function
     should be added to the `gnus-summary-prepare-hook' or to the
     `gnus-article-display-hook' if `gnus-picons-display-where' is set
     to `article'.

`gnus-picons-article-display-x-face'
     Decodes and displays the X-Face header if present.  This function
     should be added to `gnus-article-display-hook'.


   Note:  You must append them to the hook, so make sure to specify 't'
to the append flag of `add-hook':

     (add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)


File: gnus,  Node: Picon Configuration,  Prev: Hard Picons,  Up: Picons

Picon Configuration
-------------------

The following variables offer further control over how things are done,
where things are located, and other useless stuff you really don't need
to worry about.

`gnus-picons-database'
     The location of the picons database.  Should point to a directory
     containing the `news', `domains', `users' (and so on)
     subdirectories.  Defaults to `/usr/local/faces'.

`gnus-picons-news-directory'
     Sub-directory of the faces database containing the icons for
     newsgroups.

`gnus-picons-user-directories'
     List of subdirectories to search in `gnus-picons-database' for user
     faces.  Defaults to `("local" "users" "usenix" "misc/MISC")'.

`gnus-picons-domain-directories'
     List of subdirectories to search in `gnus-picons-database' for
     domain name faces.  Defaults to `("domains")'.  Some people may
     want to add `unknown' to this list.

`gnus-picons-convert-x-face'
     The command to use to convert the `X-Face' header to an X bitmap
     (`xbm').  Defaults to `(format "{ echo '/* Width=48, Height=48
     */'; uncompface; } | icontopbm | pbmtoxbm > %s"
     gnus-picons-x-face-file-name)'

`gnus-picons-x-face-file-name'
     Names a temporary file to store the `X-Face' bitmap in.  Defaults
     to `(format "/tmp/picon-xface.%s.xbm" (user-login-name))'.

`gnus-picons-buffer'
     The name of the buffer that `picons' points to.  Defaults to
     `*Icon Buffer*'.



File: gnus,  Node: Various Various,  Prev: Picons,  Up: Various

Various Various
===============

`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 will never flash any messages, if it is seven (which is
     the default), most important messages will be shown, and if it is
     ten, Gnus won't ever shut up, but will flash so many messages it
     will make your head swim.

`gnus-verbose-backends'
     This variable works the same way as `gnus-verbose', but it applies
     to the Gnus backends instead of Gnus proper.

`nnheader-max-head-length'
     When the backends read straight heads of articles, they all try to
     read 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 `nil', there is no upper read
     bound.  If it is `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 `ange-ftp'.

`nnheader-file-name-translation-alist'
     This is an alist that says how to translate characters in file
     names.  For instance, if `:' is illegal as a file character in
     file names on your system (you OS/2 user you), you could say
     something like:

          (setq nnheader-file-name-translation-alist
                '((?: . ?_)))

     In fact, this is the default value for this variable on OS/2 and MS
     Windows (phooey) systems.

`gnus-hidden-properties'
     This is a list of properties to use to hide "invisible" text.  It
     is `(invisible t intangible t)' by default on most systems, which
     makes invisible text invisible and intangible.

`gnus-parse-headers-hook'
     A hook called before parsing headers.  It can be used, for
     instance, to gather statistics on the headers fetched, or perhaps
     you'd like to prune some headers.  I don't see why you'd want
     that, though.



File: gnus,  Node: The End,  Next: Appendices,  Prev: Various,  Up: Top

The End
*******

Well, that's the manual--you can get on with your life now.  Keep in
touch.  Say hello to your cats from me.

   My *ghod*--I just can't stand goodbyes.  Sniffle.

   Ol' Charles Reznikoff said it pretty well, so I leave the floor to
him:

     *Te Deum*

     Not because of victories
     I sing,
     having none,
     but for the common sunshine,
     the breeze,
     the largess of the spring.

     Not for victory
     but for the day's work done
     as well as I was able;
     not for a seat upon the dais
     but at the common table.


File: gnus,  Node: Appendices,  Next: Index,  Prev: The End,  Up: Top

Appendices
**********

* Menu:

* History::                        How Gnus got where it is today.
* Terminology::                    We use really difficult, like, words here.
* Customization::                  Tailoring Gnus to your needs.
* Troubleshooting::                What you might try if things do not work.
* A Programmers Guide to Gnus::    Rilly, rilly technical stuff.
* Emacs for Heathens::             A short introduction to Emacsian terms.
* Frequently Asked Questions::     A question-and-answer session.


File: gnus,  Node: History,  Next: Terminology,  Up: Appendices

History
=======

GNUS was written by Masanobu UMEDA.  When autumn crept up in '94, Lars
Magne Ingebrigtsen grew bored and decided to rewrite Gnus.

   If you want to investigate the person responsible for this outrage,
you can point your (feh!) web browser to
`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".  "(ding)", is, of course, short for "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
UMEDA intended, which makes it a more appropriate name, don't you
think?)

   In any case, after spending all that energy on coming up with a new
and spunky name, we decided that the name was _too_ spunky, so we
renamed it back again to "Gnus".  But in mixed case.  "Gnus" vs.
"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.

   In May 1996 the next Gnus generation (aka.  "September Gnus") was
released under the name "Gnus 5.2".

* Menu:

* Why?::                What's the point of Gnus?
* Compatibility::       Just how compatible is Gnus with GNUS?
* Conformity::          Gnus tries to conform to all standards.
* Emacsen::             Gnus can be run on a few modern Emacsen.
* Contributors::        Oodles of people.
* New Features::        Pointers to some of the new stuff in Gnus.
* Newest Features::     Features so new that they haven't been written yet.


File: gnus,  Node: Why?,  Next: Compatibility,  Up: History

Why?
----

What's the point of Gnus?

   I want to provide a "rad", "happening", "way cool" and "hep"
newsreader, that lets you do anything you can think of.  That was my
original motivation, but while working on Gnus, it has become clear to
me that this generation of newsreaders really belong in the stone age.
Newsreaders haven't developed much since the infancy of the net.  If the
volume continues to rise with the current rate of increase, all current
newsreaders will be pretty much useless.  How do you deal with
newsgroups that have thousands of new articles each day?  How do you
keep track of millions of people who post?

   Gnus offers no real solutions to these questions, but I would very
much like to see Gnus being used as a testing ground for new methods of
reading and fetching news.  Expanding on UMEDA-san's wise decision to
separate the newsreader from the backends, Gnus now offers a simple
interface for anybody who wants to write new backends for fetching mail
and news from different sources.  I have added hooks for customizations
everywhere I could imagine useful.  By doing so, I'm inviting every one
of you to explore and invent.

   May Gnus never be complete. `C-u 100 M-x hail-emacs'.


File: gnus,  Node: Compatibility,  Next: Conformity,  Prev: Why?,  Up: History

Compatibility
-------------

Gnus was designed to be fully compatible with GNUS.  Almost all key
bindings have been kept.  More key bindings have been added, of course,
but only in one or two obscure cases have old bindings been changed.

   Our motto is:

                         In a cloud bones of steel.

   All commands have kept their names.  Some internal functions have
changed their names.

   The `gnus-uu' package has changed drastically. *note Decoding
Articles::.

   One major compatibility question is the presence of several summary
buffers.  All variables that are relevant while reading a group are
buffer-local to the summary buffer they belong in.  Although many
important variables have their values copied into their global
counterparts whenever a command is executed in the summary buffer, this
change might lead to incorrect values being used unless you are careful.

   All code that relies on knowledge of GNUS internals will probably
fail.  To take two examples: Sorting `gnus-newsrc-alist' (or changing
it in any way, as a matter of fact) is strictly verboten.  Gnus
maintains a hash table that points to the entries in this alist (which
speeds up many functions), and changing the alist directly will lead to
peculiar results.

   Old hilit19 code does not work at all.  In fact, you should probably
remove all hilit code from all Gnus hooks (`gnus-group-prepare-hook'
and `gnus-summary-prepare-hook').  Gnus provides various integrated
functions for highlighting.  These are faster and more accurate.  To
make life easier for everybody, Gnus will by default remove all hilit
calls from all hilit hooks.  Uncleanliness!  Away!

   Packages like `expire-kill' will no longer work.  As a matter of
fact, you should probably remove all old GNUS packages (and other code)
when you start using Gnus.  More likely than not, Gnus already does
what you have written code to make GNUS do.  (Snicker.)

   Even though old methods of doing things are still supported, only the
new methods are documented in this manual.  If you detect a new method
of doing something while reading this manual, that does not mean you
have to stop doing it the old way.

   Gnus understands all GNUS startup files.

   Overall, a casual user who hasn't written much code that depends on
GNUS internals should suffer no problems.  If problems occur, please
let me know by issuing that magic command `M-x gnus-bug'.


File: gnus,  Node: Conformity,  Next: Emacsen,  Prev: Compatibility,  Up: History

Conformity
----------

No rebels without a clue here, ma'am.  We conform to all standards known
to (wo)man.  Except for those standards and/or conventions we disagree
with, of course.

*RFC 822*
     There are no known breaches of this standard.

*RFC 1036*
     There are no known breaches of this standard, either.

*Usenet Seal of Approval*
     Gnus hasn't been formally through the Seal process, but I have read
     through the Seal text and I think Gnus would pass.

*Son-of-RFC 1036*
     We do have some breaches to this one.

    _MIME_
          Gnus does no MIME handling, and this standard-to-be seems to
          think that MIME is the bees' knees, so we have major breakage
          here.

    _X-Newsreader_
          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 `tin' and `Netscape' I know
          not to use either of those for posting articles.  I would not
          have known that if it wasn't for the `X-Newsreader' header.

    _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
          `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.


   If you ever notice Gnus acting non-compliantly with regards to the
texts mentioned above, don't hesitate to drop a note to Gnus Towers and
let us know.


File: gnus,  Node: Emacsen,  Next: Contributors,  Prev: Conformity,  Up: History

Emacsen
-------

Gnus should work on :

   * Emacs 19.30 and up.

   * XEmacs 19.13 and up.

   * Mule versions based on Emacs 19.30 and up.


   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:

   * 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.

   * The same with current-article marking--XEmacs puts an underline
     under the entire summary line while Emacs and Mule are nicer and
     kinder.

   * XEmacs features more graphics--a logo and a toolbar.

   * Citation highlighting us better under Emacs and Mule than under
     XEmacs.

   * Emacs 19.26-19.28 have tangible hidden headers, which can be a bit
     confusing.



File: gnus,  Node: Contributors,  Next: New Features,  Prev: Emacsen,  Up: History

Contributors
------------

The new Gnus version couldn't have been done without the help of all the
people on the (ding) mailing list.  Every day for over a year I have
gotten billions of nice bug reports from them, filling me with joy,
every single one of them.  Smooches.  The people on the list have been
tried beyond endurance, what with my "oh, that's a neat idea <type
type>, yup, I'll release it right away <ship off> no wait, that doesn't
work at all <type type>, yup, I'll ship that one off right away <ship
off> no, wait, that absolutely does not work" policy for releases.
Micro$oft--bah.  Amateurs.  I'm _much_ worse.  (Or is that "worser"?
"much worser"?  "worsest"?)

   I would like to take this opportunity to thank the Academy for...
oops, wrong show.

   * Masanobu UMEDA The writer of the original GNUS.

   * Per Abrahamsen Custom, scoring, highlighting and SOUP code (as
     well as numerous other things).

   * Luis Fernandes Design and graphics.

   * Wes Hardaker `gnus-picon.el' and the manual section on "picons"
     (*note Picons::).

   * Brad Miller `gnus-gl.el' and the GroupLens manual section (*note
     GroupLens::).

   * Sudish Joseph Innumerable bug fixes.

   * Ilja Weis `gnus-topic.el'.

   * Steven L. Baur Lots and lots of bugs detections and fixes.

   * Vladimir Alexiev The refcard and reference booklets.

   * Felix Lee & JWZ I stole some pieces from the XGnus distribution by
     Felix Lee and JWZ.

   * Scott Byer `nnfolder.el' enhancements & rewrite.

   * Peter Mutsaers Orphan article scoring code.

   * Ken Raeburn POP mail support.

   * Hallvard B Furuseth Various bits and pieces, especially dealing
     with .newsrc files.

   * Brian Edmonds `gnus-bbdb.el'.

   * Ricardo Nassif and Mark Borges Proof-reading.

   * Kevin Davidson Came up with the name "ding", so blame him.


   Peter Arius, Stainless Steel Rat, Ulrik Dickow, Jack Vinson, Daniel
Quinlan, Frank D. Cringle, Geoffrey T. Dairiki, Fabrice Popineau and
Andrew Eskilsson have all contributed code and suggestions.


File: gnus,  Node: New Features,  Next: Newest Features,  Prev: Contributors,  Up: History

New Features
------------

   * The look of all buffers can be changed by setting format-like
     variables (*note Group Buffer Format:: and *note Summary Buffer
     Format::).

   * Local spool and several NNTP servers can be used at once (*note
     Select Methods::).

   * You can combine groups into virtual groups (*note Virtual
     Groups::).

   * You can read a number of different mail formats (*note Getting
     Mail::).  All the mail backends implement a convenient mail expiry
     scheme (*note Expiring Mail::).

   * Gnus can use various strategies for gathering threads that have
     lost their roots (thereby gathering loose sub-threads into one
     thread) or it can go back and retrieve enough headers to build a
     complete thread (*note Customizing Threading::).

   * Killed groups can be displayed in the group buffer, and you can
     read them as well (*note Listing Groups::).

   * Gnus can do partial group updates--you do not have to retrieve the
     entire active file just to check for new articles in a few groups
     (*note The Active File::).

   * Gnus implements a sliding scale of subscribedness to groups (*note
     Group Levels::).

   * You can score articles according to any number of criteria (*note
     Scoring::).  You can even get Gnus to find out how to score
     articles for you (*note Adaptive Scoring::).

   * Gnus maintains a dribble buffer that is auto-saved the normal Emacs
     manner, so it should be difficult to lose much data on what you
     have read if your machine should go down (*note Auto Save::).

   * Gnus now has its own startup file (`.gnus') to avoid cluttering up
     the `.emacs' file.

   * You can set the process mark on both groups and articles and
     perform operations on all the marked items (*note
     Process/Prefix::).

   * You can grep through a subset of groups and create a group from the
     results (*note Kibozed Groups::).

   * You can list subsets of groups according to, well, anything (*note
     Listing Groups::).

   * You can browse foreign servers and subscribe to groups from those
     servers (*note Browse Foreign Server::).

   * Gnus can fetch articles asynchronously on a second connection to
     the server (*note Asynchronous Fetching::).

   * You can cache articles locally (*note Article Caching::).

   * The uudecode functions have been expanded and generalized (*note
     Decoding Articles::).

   * You can still post uuencoded articles, which was a little-known
     feature of GNUS' past (*note Uuencoding and Posting::).

   * Fetching parents (and other articles) now actually works without
     glitches (*note Finding the Parent::).

   * Gnus can fetch FAQs and group descriptions (*note Group
     Information::).

   * Digests (and other files) can be used as the basis for groups
     (*note Document Groups::).

   * Articles can be highlighted and customized (*note Customizing
     Articles::).

   * URLs and other external references can be buttonized (*note
     Article Buttons::).

   * You can do lots of strange stuff with the Gnus window & frame
     configuration (*note Windows Configuration::).

   * You can click on buttons instead of using the keyboard (*note
     Buttons::).

   * Gnus can use NoCeM files to weed out spam (*note NoCeM::).


   This is, of course, just a _short_ overview of the _most_ important
new features.  No, really.  There are tons more.  Yes, we have feeping
creaturism in full effect, but nothing too gratuitous, I would hope.


File: gnus,  Node: Newest Features,  Prev: New Features,  Up: History

Newest Features
---------------

Also known as the "todo list".  Sure to be implemented before the next
millennium.

   Be afraid.  Be very afraid.

   * Native MIME support is something that should be done.

   * A better and simpler method for specifying mail composing methods.

   * Allow posting through mail-to-news gateways.

   * Really do unbinhexing.

   And much, much, much more.  There is more to come than has already
been implemented.  (But that's always true, isn't it?)

   `<URL:http://www.ifi.uio.no/~larsi/sgnus/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.


File: gnus,  Node: Terminology,  Next: Customization,  Prev: History,  Up: Appendices

Terminology
===========

"news"
     This is what you are supposed to use this thing for--reading news.
     News is generally fetched from a nearby NNTP server, and is
     generally publicly available to everybody.  If you post news, the
     entire world is likely to read just what you have written, and
     they'll all snigger mischievously.  Behind your back.

"mail"
     Everything that's delivered to you personally is mail.  Some
     news/mail readers (like Gnus) blur the distinction between mail
     and news, but there is a difference.  Mail is private.  News is
     public.  Mailing is not posting, and replying is not following up.

"reply"
     Send a mail to the person who has written what you are reading.

"follow up"
     Post an article to the current newsgroup responding to the article
     you are reading.

"backend"
     Gnus gets fed articles from a number of backends, both news and
     mail backends.  Gnus does not handle the underlying media, so to
     speak--this is all done by the backends.

"native"
     Gnus will always use one method (and backend) as the "native", or
     default, way of getting news.

"foreign"
     You can also have any number of foreign groups active at the same
     time.  These are groups that use different backends for getting
     news.

"secondary"
     Secondary backends are somewhere half-way between being native and
     being foreign, but they mostly act like they are native.

"article"
     A nessage that has been posted as news.

"mail message"
     A message that has been mailed.

"message"
     A mail message or news article

"head"
     The top part of a message, where administrative information (etc.)
     is put.

"body"
     The rest of an article.  Everything that is not in the head is in
     the body.

"header"
     A line from the head of an article.

"headers"
     A collection of such lines, or a collection of heads.  Or even a
     collection of NOV lines.

"NOV"
     When Gnus enters a group, it asks the backend for the headers of
     all unread articles in the group.  Most servers support the News
     OverView format, which is more compact and much faster to read and
     parse than the normal HEAD format.

"level"
     Each group is subscribed at some "level" or other (1-9).  The ones
     that have a lower level are "more" subscribed than the groups with
     a higher level.  In fact, groups on levels 1-5 are considered
     "subscribed"; 6-7 are "unsubscribed"; 8 are "zombies"; and 9 are
     "killed".  Commands for listing groups and scanning for new
     articles will all use the numeric prefix as "working level".

"killed groups"
     No information on killed groups is stored or updated, which makes
     killed groups much easier to handle than subscribed groups.

"zombie groups"
     Just like killed groups, only slightly less dead.

"active file"
     The news server has to keep track of what articles it carries, and
     what groups exist.  All this information in stored in the active
     file, which is rather large, as you might surmise.

"bogus groups"
     A group that exists in the `.newsrc' file, but isn't known to the
     server (i. e.,  it isn't in the active file), is a _bogus group_.
     This means that the group probably doesn't exist (any more).

"server"
     A machine than one can connect to and get news (or mail) from.

"select method"
     A structure that specifies the backend, the server and the virtual
     server parameters.

"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 whole is a virtual server.



File: gnus,  Node: Customization,  Next: Troubleshooting,  Prev: Terminology,  Up: Appendices

Customization
=============

All variables are properly documented elsewhere in this manual.  This
section is designed to give general pointers on how to customize Gnus
for some quite common situations.

* Menu:

* Slow/Expensive Connection:: You run a local Emacs and get the news elsewhere.
* Slow Terminal Connection::  You run a remote Emacs.
* Little Disk Space::         You feel that having large setup files is icky.
* Slow Machine::              You feel like buying a faster machine.


File: gnus,  Node: Slow/Expensive Connection,  Next: Slow Terminal Connection,  Up: Customization

Slow/Expensive NNTP Connection
------------------------------

If you run Emacs on a machine locally, and get your news from a machine
over some very thin strings, you want to cut down on the amount of data
Gnus has to get from the NNTP server.

`gnus-read-active-file'
     Set this to `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 `gnus-check-new-news' and
     `gnus-check-bogus-newsgroups' to `nil' to make sure that Gnus
     doesn't suddenly decide to fetch the active file anyway.

`gnus-nov-is-evil'
     This one has to be `nil'.  If not, grabbing article headers from
     the NNTP server will not be very fast.  Not all NNTP servers
     support XOVER; Gnus will detect this by itself.


File: gnus,  Node: Slow Terminal Connection,  Next: Little Disk Space,  Prev: Slow/Expensive Connection,  Up: Customization

Slow Terminal Connection
------------------------

Let's say you use your home computer for dialing up the system that
runs Emacs and Gnus.  If your modem is slow, you want to reduce the
amount of data that is sent over the wires as much as possible.

`gnus-auto-center-summary'
     Set this to `nil' to inhibit Gnus from re-centering the summary
     buffer all the time.  If it is `vertical', do only vertical
     re-centering.  If it is neither `nil' nor `vertical', do both
     horizontal and vertical recentering.

`gnus-visible-headers'
     Cut down on the headers that are included in the articles to the
     minimum.  You can, in fact, make do without them altogether--most
     of the useful data is in the summary buffer, anyway.  Set this
     variable to `^NEVVVVER' or `From:', or whatever you feel you need.

`gnus-article-display-hook'
     Set this hook to all the available hiding commands:
          (setq gnus-article-display-hook
                '(gnus-article-hide-headers gnus-article-hide-signature
                  gnus-article-hide-citation))

`gnus-use-full-window'
     By setting this to `nil', you can make all the windows smaller.
     While this doesn't really cut down much generally, it means that
     you have to see smaller portions of articles before deciding that
     you didn't want to read them anyway.

`gnus-thread-hide-subtree'
     If this is non-`nil', all threads in the summary buffer will be
     hidden initially.

`gnus-updated-mode-lines'
     If this is `nil', Gnus will not put information in the buffer mode
     lines, which might save some time.


File: gnus,  Node: Little Disk Space,  Next: Slow Machine,  Prev: Slow Terminal Connection,  Up: Customization

Little Disk Space
-----------------

The startup files can get rather large, so you may want to cut their
sizes a bit if you are running out of space.

`gnus-save-newsrc-file'
     If this is `nil', Gnus will never save `.newsrc'--it will only
     save `.newsrc.eld'.  This means that you will not be able to use
     any other newsreaders than Gnus.  This variable is `t' by default.

`gnus-save-killed-list'
     If this is `nil', Gnus will not save the list of dead groups.  You
     should also set `gnus-check-new-newsgroups' to `ask-server' and
     `gnus-check-bogus-newsgroups' to `nil' if you set this variable to
     `nil'.  This variable is `t' by default.



File: gnus,  Node: Slow Machine,  Prev: Little Disk Space,  Up: Customization

Slow Machine
------------

If you have a slow machine, or are just really impatient, there are a
few things you can do to make Gnus run faster.

   Set`gnus-check-new-newsgroups' and `gnus-check-bogus-newsgroups' to
`nil' to make startup faster.

   Set `gnus-show-threads', `gnus-use-cross-reference' and
`gnus-nov-is-evil' to `nil' to make entering and exiting the summary
buffer faster.

   Set `gnus-article-display-hook' to `nil' to make article processing
a bit faster.


File: gnus,  Node: Troubleshooting,  Next: A Programmers Guide to Gnus,  Prev: Customization,  Up: Appendices

Troubleshooting
===============

Gnus works _so_ well straight out of the box--I can't imagine any
problems, really.

   Ahem.

  1. Make sure your computer is switched on.

  2. Make sure that you really load the current Gnus version.  If you
     have been running GNUS, you need to exit Emacs and start it up
     again before Gnus will work.

  3. Try doing an `M-x gnus-version'.  If you get something that looks
     like `Gnus v5.46; nntp 4.0' you have the right files loaded.  If,
     on the other hand, you get something like `NNTP 3.x' or `nntp
     flee', you have some old `.el' files lying around.  Delete these.

  4. Read the help group (`G h' in the group buffer) for a FAQ and a
     how-to.

   If all else fails, report the problem as a bug.

   If you find a bug in Gnus, you can report it with the `M-x gnus-bug'
command. `M-x set-variable RET debug-on-error RET t RET', and send me
the backtrace.  I will fix bugs, but I can only fix them if you send me
a precise description as to how to reproduce the bug.

   You really can never be too detailed in a bug report.  Always use the
`M-x gnus-bug' command when you make bug reports, even if it creates a
10Kb mail each time you use it, and even if you have sent me your
environment 500 times before.  I don't care.  I want the full info each
time.

   It is also important to remember that I have no memory whatsoever.
If you send a bug report, and I send you a reply, and then you send back
just "No, it's not! Moron!", I will have no idea what you are insulting
me about.  Always over-explain everything.  It's much easier for all of
us--if I don't have all the information I need, I will just 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 `xwd', for instance),
put it somewhere it can be reached, and include the URL of the picture
in the bug report.a

   If you just need help, you are better off asking on
`gnu.emacs.gnus'.  I'm not very helpful.

   You can also ask on the ding mailing list--`ding@ifi.uio.no'.  Write
to `ding-request@ifi.uio.no' to subscribe.


File: gnus,  Node: A Programmers Guide to Gnus,  Next: Emacs for Heathens,  Prev: Troubleshooting,  Up: Appendices

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
it.

   You can never expect the internals of a program not to change, but I
will be defining (in some details) the interface between Gnus and its
backends (this is written in stone), the format of the score files
(ditto), data structures (some are less likely to change than others)
and general method of operations.

* Menu:

* Backend Interface::        How Gnus communicates with the servers.
* Score File Syntax::        A BNF definition of the score file standard.
* Headers::                  How Gnus stores headers internally.
* Ranges::                   A handy format for storing mucho numbers.
* Group Info::               The group info format.
* Emacs/XEmacs Code::        Gnus can be run under all modern Emacsen.
* Various File Formats::     Formats of files that Gnus use.


File: gnus,  Node: Backend Interface,  Next: Score File Syntax,  Up: A Programmers Guide to Gnus

Backend Interface
-----------------

Gnus doesn't know anything about NNTP, spools, mail or virtual groups.
It only knows how to talk to "virtual servers".  A virtual server is a
"backend" and some "backend variables".  As examples of the first, we
have `nntp', `nnspool' and `nnmbox'.  As examples of the latter we have
`nntp-port-number' and `nnmbox-directory'.

   When Gnus asks for information from a backend--say `nntp'--on
something, it will normally include a virtual server name in the
function parameters.  (If not, the backend should use the "current"
virtual server.)  For instance, `nntp-request-list' takes a virtual
server as its only (optional) parameter.  If this virtual server hasn't
been opened, the function should fail.

   Note that a virtual server name has no relation to some physical
server name.  Take this example:

     (nntp "odd-one"
           (nntp-address "ifi.uio.no")
           (nntp-port-number 4324))

   Here the virtual server name is `odd-one' while the name of the
physical server is `ifi.uio.no'.

   The backends should be able to switch between several virtual
servers.  The standard backends implement this by keeping an alist of
virtual server environments that it pulls down/pushes up when needed.

   There are two groups of interface functions: "required functions",
which must be present, and "optional functions", which Gnus will always
check whether are present before attempting to call.

   All these functions are expected to return data in the buffer
`nntp-server-buffer' (` *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 talk about
"return value", I talk about the function value returned by the
function call.

   Some backends could be said to be "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 more.

   In the examples and definitions I will refer to the imaginary backend
`nnchoke'.

* Menu:

* Required Backend Functions::        Functions that must be implemented.
* Optional Backend Functions::        Functions that need not be implemented.
* Writing New Backends::              Extending old backends.


File: gnus,  Node: Required Backend Functions,  Next: Optional Backend Functions,  Up: Backend Interface

Required Backend Functions
..........................

`(nnchoke-retrieve-headers ARTICLES &optional GROUP SERVER FETCH-OLD)'
     ARTICLES is either a range of article numbers or a list of
     `Message-ID's.  Current backends do not fully support either--only
     sequences (lists) of article numbers, and most backends do not
     support retrieval of `Message-ID's.  But they should try for both.

     The result data should either be HEADs or NOV lines, and the result
     value should either be `headers' or `nov' to reflect this.  This
     might later be expanded to `various', which will be a mixture of
     HEADs and NOV lines, but this is currently not supported by Gnus.

     If FETCH-OLD is non-`nil' it says to try to fetch "extra headers,
     in some meaning of the word.  This is generally done by fetching
     (at most) FETCH-OLD extra headers less than the smallest article
     number in `articles', and fill in the gaps as well.  The presence
     of this parameter can be ignored if the backend finds it
     cumbersome to follow the request.  If this is non-`nil' and not a
     number, do maximum fetches.

     Here's an example HEAD:

          221 1056 Article retrieved.
          Path: ifi.uio.no!sturles
          From: sturles@ifi.uio.no (Sturle Sunde)
          Newsgroups: ifi.discussion
          Subject: Re: Something very droll
          Date: 27 Oct 1994 14:02:57 +0100
          Organization: Dept. of Informatics, University of Oslo, Norway
          Lines: 26
          Message-ID: <38o8e1$a0o@holmenkollen.ifi.uio.no>
          References: <38jdmq$4qu@visbur.ifi.uio.no>
          NNTP-Posting-Host: holmenkollen.ifi.uio.no
          .

     So a `headers' return value would imply that there's a number of
     these in the data buffer.

     Here's a BNF definition of such a buffer:

          headers        = *head
          head           = error / valid-head
          error-message  = [ "4" / "5" ] 2number " " <error message> eol
          valid-head     = valid-message *header "." eol
          valid-message  = "221 " <number> " Article retrieved." eol
          header         = <text> eol

     If the return value is `nov', the data buffer should contain
     "network overview database" lines.  These are basically fields
     separated by tabs.

          nov-buffer = *nov-line
          nov-line   = 8*9 [ field <TAB> ] eol
          field      = <text except TAB>

     For a closer explanation what should be in those fields, *note
     Headers::.

`(nnchoke-open-server SERVER &optional DEFINITIONS)'
     SERVER is here the virtual server name.  DEFINITIONS is a list of
     `(VARIABLE VALUE)' pairs that defines this virtual server.

     If the server can't be opened, no error should be signaled.  The
     backend may then choose to refuse further attempts at connecting
     to this server.  In fact, it should do so.

     If the server is opened already, this function should return a
     non-`nil' value.  There should be no data returned.

`(nnchoke-close-server &optional SERVER)'
     Close connection to SERVER and free all resources connected to it.
     Return `nil' if the server couldn't be closed for some reason.

     There should be no data returned.

`(nnchoke-request-close)'
     Close connection to all servers and free all resources that the
     backend have reserved.  All buffers that have been created by that
     backend should be killed.  (Not the `nntp-server-buffer', though.)
     This function is generally only called when Gnus is shutting down.

     There should be no data returned.

`(nnchoke-server-opened &optional SERVER)'
     If SERVER is the current virtual server, and the connection to the
     physical server is alive, then this function should return a
     non-`nil' vlue.  This function should under no circumstances
     attempt to reconnect to a server that is has lost connection to.

     There should be no data returned.

`(nnchoke-status-message &optional SERVER)'
     This function should return the last error message from SERVER.

     There should be no data returned.

`(nnchoke-request-article ARTICLE &optional GROUP SERVER TO-BUFFER)'
     The result data from this function should be the article specified
     by ARTICLE.  This might either be a `Message-ID' or a number.  It
     is optional whether to implement retrieval by `Message-ID', but it
     would be nice if that were possible.

     If TO-BUFFER is non-`nil', the result data should be returned in
     this buffer instead of the normal data buffer.  This is to make it
     possible to avoid copying large amounts of data from one buffer to
     another, and Gnus mainly request articles to be inserted directly
     into its article buffer.

     If it is at all possible, this function should return a cons cell
     where the car is the group name the article was fetched from, and
     the cdr is the article number.  This will enable Gnus to find out
     what the real group and article numbers are when fetching articles
     by `Message-ID'.  If this isn't possible, `t' should be returned
     on successful article retrievement.

`(nnchoke-open-group GROUP &optional SERVER)'
     Make GROUP the current group.

     There should be no data returned by this function.

`(nnchoke-request-group GROUP &optional SERVER)'
     Get data on GROUP.  This function also has the side effect of
     making GROUP the current group.

     Here's an example of some result data and a definition of the same:

          211 56 1000 1059 ifi.discussion

     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 whether one should take the bother to generate it
     properly (if that is a problem) is left as an exercise to the
     reader.

          group-status = [ error / info ] eol
          error        = [ "4" / "5" ] 2<number> " " <Error message>
          info         = "211 " 3* [ <number> " " ] <string>

`(nnchoke-close-group GROUP &optional SERVER)'
     Close GROUP and free any resources connected to it.  This will be
     a no-op on most backends.

     There should be no data returned.

`(nnchoke-request-list &optional SERVER)'
     Return a list of all groups available on SERVER.  And that means
     _all_.

     Here's an example from a server that only carries two groups:

          ifi.test 0000002200 0000002000 y
          ifi.discussion 3324 3300 n

     On each line we have a group name, then the highest article number
     in that group, the lowest article number, and finally a flag.

          active-file = *active-line
          active-line = name " " <number> " " <number> " " flags eol
          name        = <string>
          flags       = "n" / "y" / "m" / "x" / "j" / "=" name

     The flag says whether the group is read-only (`n'), is moderated
     (`m'), is dead (`x'), is aliased to some other group
     (`=other-group' or none of the above (`y').

`(nnchoke-request-post &optional SERVER)'
     This function should post the current buffer.  It might return
     whether the posting was successful or not, but that's not
     required.  If, for instance, the posting is done asynchronously,
     it has generally not been completed by the time this function
     concludes.  In that case, this function should set up some kind of
     sentinel to beep the user loud and clear if the posting could not
     be completed.

     There should be no result data from this function.



File: gnus,  Node: Optional Backend Functions,  Next: Writing New Backends,  Prev: Required Backend Functions,  Up: Backend Interface

Optional Backend Functions
..........................

`(nnchoke-retrieve-groups GROUPS &optional SERVER)'
     GROUPS is a list of groups, and this function should request data
     on all those groups.  How it does it is of no concern to Gnus, but
     it should attempt to do this in a speedy fashion.

     The return value of this function can be either `active' or
     `group', which says what the format of the result data is.  The
     former is in the same format as the data from
     `nnchoke-request-list', while the latter is a buffer full of lines
     in the same format as `nnchoke-request-group' gives.

          group-buffer = *active-line / *group-status

`(nnchoke-request-update-info GROUP INFO &optional SERVER)'
     A Gnus group info (*note 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 (altered) group info.  This function may alter
     the group info destructively, so no copying is needed before
     boogeying.

     There should be no result data from this function.

`(nnchoke-request-type GROUP &optional ARTICLE)'
     When the user issues commands for "sending news" (`F' in the
     summary buffer, for instance), Gnus has to know whether the
     article the user is following up is news or mail.  This function
     should return `news' if ARTICLE in GROUP is news, `mail' if it is
     mail and `unknown' if the type can't be decided.  (The ARTICLE
     parameter is necessary in `nnvirtual' groups which might very well
     combine mail groups and news groups.)

     There should be no result data from this function.

`(nnchoke-request-update-mark GROUP ARTICLE MARK)'
     If the user tries to set a mark that the backend doesn't like, this
     function may change the mark.  Gnus will use whatever this function
     returns as the mark for ARTICLE instead of the original MARK.  If
     the backend doesn't care, it must return the original MARK, and
     not `nil' or any other type of garbage.

     The only use for this that I can see is what `nnvirtual' does with
     it--if a component group is auto-expirable, marking an article as
     read in the virtual group should result in the article being
     marked as expirable.

     There should be no result data from this function.

`(nnchoke-request-scan &optional GROUP SERVER)'
     This function may be called at any time (by Gnus or anything else)
     to request that the backend check for incoming articles, in one
     way or another.  A mail backend will typically read the spool file
     or query the POP server when this function is invoked.  The GROUP
     doesn't have to be heeded--if the backend decides that it is too
     much work just scanning for a single group, it may do a total scan
     of all groups.  It would be nice, however, to keep things local if
     that's practical.

     There should be no result data from this function.

`(nnchoke-request-asynchronous GROUP &optional SERVER ARTICLES)'
     This is a request to fetch articles asynchronously later.
     ARTICLES is an alist of (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.

`(nnchoke-request-group-description GROUP &optional SERVER)'
     The result data from this function should be a description of
     GROUP.

          description-line = name <TAB> description eol
          name             = <string>
          description      = <text>

`(nnchoke-request-list-newsgroups &optional SERVER)'
     The result data from this function should be the description of all
     groups available on the server.

          description-buffer = *description-line

`(nnchoke-request-newgroups DATE &optional SERVER)'
     The result data from this function should be all groups that were
     created after `date', which is in normal human-readable date
     format.  The data should be in the active buffer format.

`(nnchoke-request-create-group GROUP &optional SERVER)'
     This function should create an empty group with name GROUP.

     There should be no return data.

`(nnchoke-request-expire-articles ARTICLES &optional GROUP SERVER FORCE)'
     This function should run the expiry process on all articles in the
     ARTICLES range (which is currently a simple list of article
     numbers.)  It is left up to the backend to decide how old articles
     should be before they are removed by this function.  If FORCE is
     non-`nil', all ARTICLES should be deleted, no matter how new they
     are.

     This function should return a list of articles that it did not/was
     not able to delete.

     There should be no result data returned.

`(nnchoke-request-move-article ARTICLE GROUP SERVER ACCEPT-FORM'
     &optional LAST)

     This function should move ARTICLE (which is a number) from GROUP
     by calling ACCEPT-FORM.

     This function should ready the article in question for moving by
     removing any header lines it has added to the article, and
     generally should "tidy up" the article.  Then it should `eval'
     ACCEPT-FORM in the buffer where the "tidy" article is.  This will
     do the actual copying.  If this `eval' returns a non-`nil' value,
     the article should be removed.

     If LAST is `nil', that means that there is a high likelihood that
     there will be more requests issued shortly, so that allows some
     optimizations.

     The function should return a cons where the car is the group name
     and the cdr is the article number that the article was entered as.

     There should be no data returned.

`(nnchoke-request-accept-article GROUP &optional SERVER LAST)'
     This function takes the current buffer and inserts it into GROUP.
     If LAST in `nil', that means that there will be more calls to this
     function in short order.

     The function should return a cons where the car is the group name
     and the cdr is the article number that the article was entered as.

     There should be no data returned.

`(nnchoke-request-replace-article ARTICLE GROUP BUFFER)'
     This function should remove ARTICLE (which is a number) from GROUP
     and insert BUFFER there instead.

     There should be no data returned.

`(nnchoke-request-delete-group GROUP FORCE &optional SERVER)'
     This function should delete GROUP.  If FORCE, it should really
     delete all the articles in the group, and then delete the group
     itself.  (If there is such a thing as "the group itself".)

     There should be no data returned.

`(nnchoke-request-rename-group GROUP NEW-NAME &optional SERVER)'
     This function should rename GROUP into NEW-NAME.  All articles
     that are in GROUP should move to NEW-NAME.

     There should be no data returned.



File: gnus,  Node: Writing New Backends,  Prev: Optional Backend Functions,  Up: Backend Interface

Writing New Backends
....................

The various backends share many similarities.  `nnml' is just like
`nnspool', but it allows you to edit the articles on the server.
`nnmh' is just like `nnml', but it doesn't use an active file, and it
doesn't maintain overview databases.  `nndir' is just like `nnml', but
it has no concept of "groups", and it doesn't allow editing articles.

   It would make sense if it were possible to "inherit" functions from
backends when writing new backends.  And, indeed, you can do that if you
want to.  (You don't have to if you don't want to, of course.)

   All the backends declare their public variables and functions by
using a package called `nnoo'.

   To inherit functions from other backends (and allow other backends to
inherit functions from the current backend), you should use the
following macros: following.

`nnoo-declare'
     This macro declares the first parameter to be a child of the
     subsequent parameters.  For instance:

          (nnoo-declare nndir
            nnml nnmh)

     `nndir' has here declared that it intends to inherit functions from
     both `nnml' and `nnmh'.

`defvoo'
     This macro is equivalent to `defvar', but registers the variable as
     a public server variable.  Most state-oriented variables should be
     declared with `defvoo' instead of `defvar'.

     In addition to the normal `defvar' parameters, it takes a list of
     variables in the parent backends to map the variable to when
     executing a function in those backends.

          (defvoo nndir-directory nil
            "Where nndir will look for groups."
            nnml-current-directory nnmh-current-directory)

     This means that `nnml-current-directory' will be set to
     `nndir-directory' when an `nnml' function is called on behalf of
     `nndir'.  (The same with `nnmh'.)

`nnoo-define-basics'
     This macro defines some common functions that almost all backends
     should have.

          (nnoo-define-basics nndir)

`deffoo'
     This macro is just like `defun' and takes the same parameters.  In
     addition to doing the normal `defun' things, it registers the
     function as being public so that other backends can inherit it.

`nnoo-map-functions'
     This macro allows mapping of functions from the current backend to
     functions from the parent backends.

          (nnoo-map-functions nndir
            (nnml-retrieve-headers 0 nndir-current-group 0 0)
            (nnmh-request-article 0 nndir-current-group 0 0))

     This means that when `nndir-retrieve-headers' is called, the first,
     third, and fourth parameters will be passed on to
     `nnml-retrieve-headers', while the second parameter is set to the
     value of `nndir-current-group'.

`nnoo-import'
     This macro allows importing functions from backends.  It should be
     the last thing in the source file, since it will only define
     functions that haven't already been defined.

          (nnoo-import nndir
            (nnmh
             nnmh-request-list
             nnmh-request-newgroups)
            (nnml))

     This means that calls to `nndir-request-list' should just be passed
     on to `nnmh-request-list', while all public functions from `nnml'
     that haven't been defined in `nndir' yet should be defined now.


   Below is a slightly shortened version of the `nndir' backend.

     ;;; nndir.el --- single directory newsgroup access for Gnus
     ;; Copyright (C) 1995,96 Free Software Foundation, Inc.
     
     ;;; Code:
     
     (require 'nnheader)
     (require 'nnmh)
     (require 'nnml)
     (require 'nnoo)
     (eval-when-compile (require 'cl))
     
     (nnoo-declare nndir
       nnml nnmh)
     
     (defvoo nndir-directory nil
       "Where nndir will look for groups."
       nnml-current-directory nnmh-current-directory)
     
     (defvoo nndir-nov-is-evil nil
       "*Non-nil means that nndir will never retrieve NOV headers."
       nnml-nov-is-evil)
     
     (defvoo nndir-current-group "" nil nnml-current-group nnmh-current-group)
     (defvoo nndir-top-directory nil nil nnml-directory nnmh-directory)
     (defvoo nndir-get-new-mail nil nil nnml-get-new-mail nnmh-get-new-mail)
     
     (defvoo nndir-status-string "" nil nnmh-status-string)
     (defconst nndir-version "nndir 1.0")
     
     ;;; Interface functions.
     
     (nnoo-define-basics nndir)
     
     (deffoo nndir-open-server (server &optional defs)
       (setq nndir-directory
     	(or (cadr (assq 'nndir-directory defs))
     	    server))
       (unless (assq 'nndir-directory defs)
         (push `(nndir-directory ,server) defs))
       (push `(nndir-current-group
     	  ,(file-name-nondirectory (directory-file-name nndir-directory)))
     	defs)
       (push `(nndir-top-directory
     	  ,(file-name-directory (directory-file-name nndir-directory)))
     	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-group nndir-current-group 0 0)
       (nnmh-close-group nndir-current-group 0))
     
     (nnoo-import nndir
       (nnmh
        nnmh-status-message
        nnmh-request-list
        nnmh-request-newgroups))
     
     (provide 'nndir)


File: gnus,  Node: Score File Syntax,  Next: Headers,  Prev: Backend Interface,  Up: A Programmers Guide to Gnus

Score File Syntax
-----------------

Score files are meant to be easily parsable, but yet extremely
mallable.   It was decided that something that had the same read syntax
as an Emacs Lisp list would fit that spec.

   Here's a typical score file:

     (("summary"
       ("win95" -10000 nil s)
       ("Gnus"))
      ("from"
       ("Lars" -1000))
      (mark -100))

   BNF definition of a score file:

     score-file       = "" / "(" *element ")"
     element          = rule / atom
     rule             = string-rule / number-rule / date-rule
     string-rule      = "(" quote string-header quote space *string-match ")"
     number-rule      = "(" quote number-header quote space *number-match ")"
     date-rule        = "(" quote date-header quote space *date-match ")"
     quote            = <ascii 34>
     string-header    = "subject" / "from" / "references" / "message-id" /
                        "xref" / "body" / "head" / "all" / "followup"
     number-header    = "lines" / "chars"
     date-header      = "date"
     string-match     = "(" quote <string> quote [ "" / [ space score [ "" /
                        space date [ "" / [ space string-match-t ] ] ] ] ] ")"
     score            = "nil" / <integer>
     date             = "nil" / <natural number>
     string-match-t   = "nil" / "s" / "substring" / "S" / "Substring" /
                        "r" / "regex" / "R" / "Regex" /
                        "e" / "exact" / "E" / "Exact" /
                        "f" / "fuzzy" / "F" / "Fuzzy"
     number-match     = "(" <integer> [ "" / [ space score [ "" /
                        space date [ "" / [ space number-match-t ] ] ] ] ] ")"
     number-match-t   = "nil" / "=" / "<" / ">" / ">=" / "<="
     date-match       = "(" quote <string> quote [ "" / [ space score [ "" /
                        space date [ "" / [ space date-match-t ] ] ] ] ")"
     date-match-t     = "nil" / "at" / "before" / "after"
     atom             = "(" [ required-atom / optional-atom ] ")"
     required-atom    = mark / expunge / mark-and-expunge / files /
                        exclude-files / read-only / touched
     optional-atom    = adapt / local / eval
     mark             = "mark" space nil-or-number
     nil-or-number    = "nil" / <integer>
     expunge          = "expunge" space nil-or-number
     mark-and-expunge = "mark-and-expunge" space nil-or-number
     files            = "files" *[ space <string> ]
     exclude-files    = "exclude-files" *[ space <string> ]
     read-only        = "read-only" [ space "nil" / space "t" ]
     adapt            = "adapt" [ space "nil" / space "t" / space adapt-rule ]
     adapt-rule       = "(" *[ <string> *[ "(" <string> <integer> ")" ] ")"
     local            = "local" *[ space "(" <string> space <form> ")" ]
     eval             = "eval" space <form>
     space            = *[ " " / <TAB> / <NEWLINE> ]

   Any unrecognized elements in a score file should be ignored, but not
discarded.

   As you can see, white space is needed, but the type and amount of
white space is irrelevant.  This means that formatting of the score
file is left up to the programmer--if it's simpler to just spew it all
out on one looong line, then that's ok.

   The meaning of the various atoms are explained elsewhere in this
manual.


File: gnus,  Node: Headers,  Next: Ranges,  Prev: Score File Syntax,  Up: A Programmers Guide to Gnus

Headers
-------

Gnus uses internally a format for storing article headers that
corresponds to the NOV format in a mysterious fashion.  One could
almost suspect that the author looked at the NOV specification and just
shamelessly _stole_ the entire thing, and one would be right.

   "Header" is a severely overloaded term.  "Header" is used in RFC1036
to talk about lines in the head of an article (eg., `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.

   These slots are, in order: `number', `subject', `from', `date',
`id', `references', `chars', `lines', `xref'.  There are macros for
accessing and setting these slots - they all have predictable names
beginning with `mail-header-' and `mail-header-set-', respectively.

   The `xref' slot is really a `misc' slot.  Any extra info will be put
in there.


File: gnus,  Node: Ranges,  Next: Group Info,  Prev: Headers,  Up: A Programmers Guide to Gnus

Ranges
------

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 _wild_ example)
that you want to callify 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.

     (1 2 3 4 5 6 10 11 12)

   is transformed into

     ((1 . 6) (10 . 12))

   To avoid having those nasty `(13 . 13)' elements to denote a
lonesome object, a `13' is a valid element:

     ((1 . 6) 7 (10 . 12))

   This means that comparing two ranges to find out whether they are
equal is slightly tricky:

     ((1 . 5) 7 8 (10 . 12))

   and

     ((1 . 5) (7 . 8) (10 . 12))

   are equal.  In fact, any non-descending list is a range:

     (1 2 3 4 5)

   is a perfectly valid range, although a pretty long-winded one.  This
is also legal:

     (1 . 5)

   and is equal to the previous range.

   Here's a BNF definition of ranges.  Of course, one must remember the
semantic requirement that the numbers are non-descending.  (Any number
of repetition of the same number is allowed, but apt to disappear in
range handling.)

     range           = simple-range / normal-range
     simple-range    = "(" number " . " number ")"
     normal-range    = "(" start-contents ")"
     contents        = "" / simple-range *[ " " contents ] /
                       number *[ " " contents ]

   Gnus currently uses ranges to keep track of read articles and article
marks.  I plan on implementing a number of range operators in C if The
Powers That Be are willing to let me.  (I haven't asked yet, because I
need to do some more thinking on what operators I need to make life
totally range-based without ever having to convert back to normal
sequences.)


File: gnus,  Node: Group Info,  Next: Emacs/XEmacs Code,  Prev: Ranges,  Up: A Programmers Guide to Gnus

Group Info
----------

Gnus stores all permanent info on groups in a "group info" list.  This
list is from three to six elements (or more) long and exhaustively
describes the group.

   Here are two example group infos; one is a very simple group while
the second is a more complex one:

     ("no.group" 5 (1 . 54324))
     
     ("nnml:my.mail" 3 ((1 . 5) 9 (20 . 55))
                     ((tick (15 . 19)) (replied 3 6 (19 . 3)))
                     (nnml "")
                     (auto-expire (to-address "ding@ifi.uio.no")))

   The first element is the group name as Gnus knows the group; the
second is the group level; the third is the read articles in range
format; the fourth is a list of article marks lists; the fifth is the
select method; and the sixth contains the group parameters.

   Here's a BNF definition of the group info format:

     info          = "(" group space level space read
                     [ "" / [ space marks-list [ "" / [ space method [ "" /
                     space parameters ] ] ] ] ] ")"
     group         = quote <string> quote
     level         = <integer in the range of 1 to inf>
     read          = range
     marks-lists   = nil / "(" *marks ")"
     marks         = "(" <string> range ")"
     method        = "(" <string> *elisp-forms ")"
     parameters    = "(" *elisp-forms ")"

   Actually that `marks' rule is a fib.  A `marks' is a `<string>'
consed on to a `range', but that's a bitch to say in pseudo-BNF.


File: gnus,  Node: Emacs/XEmacs Code,  Next: Various File Formats,  Prev: Group Info,  Up: A Programmers Guide to Gnus

Emacs/XEmacs Code
-----------------

While Gnus runs under Emacs, XEmacs and Mule, I decided that one of the
platforms must be the primary one.  I chose Emacs.  Not because I don't
like XEmacs or Mule, but because it comes first alphabetically.

   This means that Gnus will byte-compile under Emacs with nary a
warning, while XEmacs will pump out gigabytes of warnings while
byte-compiling.  As I use byte-compilation warnings to help me root out
trivial errors in Gnus, that's very useful.

   I've also consistently used Emacs function interfaces, but have used
Gnusey aliases for the functions.  To take an example:  Emacs defines a
`run-at-time' function while XEmacs defines a `start-itimer' function.
I then define a function called `gnus-run-at-time' that takes the same
parameters as the Emacs `run-at-time'.  When running Gnus under Emacs,
the former function is just an alias for the latter.  However, when
running under XEmacs, the former is an alias for the following function:

     (defun gnus-xmas-run-at-time (time repeat function &rest args)
       (start-itimer
        "gnus-run-at-time"
        `(lambda ()
           (,function ,@args))
        time repeat))

   This sort of thing has been done for bunches of functions.  Gnus does
not redefine any native Emacs functions while running under XEmacs - it
does this `defalias' thing with Gnus equivalents instead.  Cleaner all
over.

   Of course, I could have chosen XEmacs as my native platform and done
mapping functions the other way around.  But I didn't.  The performance
hit these indirections impose on Gnus under XEmacs should be slight.


File: gnus,  Node: Various File Formats,  Prev: Emacs/XEmacs Code,  Up: A Programmers Guide to Gnus

Various File Formats
--------------------

* Menu:

* Active File Format::      Information on articles and groups available.
* Newsgroups File Format::  Group descriptions.


File: gnus,  Node: Active File Format,  Next: Newsgroups File Format,  Up: Various File Formats

Active File Format
..................

The active file lists all groups that are available on the server in
question.  It also lists the highest and lowest current article numbers
in each group.

   Here's an excerpt from a typical active file:

     soc.motss 296030 293865 y
     alt.binaries.pictures.fractals 3922 3913 n
     comp.sources.unix 1605 1593 m
     comp.binaries.ibm.pc 5097 5089 y
     no.general 1000 900 y

   Here's a pseudo-BNF definition of this file:

     active      = *group-line
     group-line  = group space high-number space low-number space flag <NEWLINE>
     group       = <non-white-space string>
     space       = " "
     high-number = <non-negative integer>
     low-number  = <positive integer>
     flag        = "y" / "n" / "m" / "j" / "x" / "=" group


File: gnus,  Node: Newsgroups File Format,  Prev: Active File Format,  Up: Various File Formats

Newsgroups File Format
......................

The newsgroups file lists groups along with their descriptions.  Not all
groups on the server have to be listed,  and not all groups in the file
have to exist on the server.  The file is meant purely as information to
the user.

   The format is quite simple; a group name, a tab, and the description.
Here's the definition:

     newsgroups    = *line
     line          = group tab description <NEWLINE>
     group         = <non-white-space string>
     tab           = <TAB>
     description   = <string>


File: gnus,  Node: Emacs for Heathens,  Next: Frequently Asked Questions,  Prev: A Programmers Guide to Gnus,  Up: Appendices

Emacs for Heathens
==================

Believe it or not, but some people who use Gnus haven't really used
Emacs much before they embarked on their journey on the Gnus Love Boat.
If you are one of those unfortunates whom "`M-C-a'", "kill the region",
and "set `gnus-flargblossen' to an alist where the key is a regexp that
is used for matching on the group name" are magical phrases with little
or no meaning, then this appendix is for you.  If you are already
familiar with Emacs, just ignore this and go fondle your cat instead.

* Menu:

* Keystrokes::      Entering text and executing commands.
* Emacs Lisp::      The built-in Emacs programming language.


File: gnus,  Node: Keystrokes,  Next: Emacs Lisp,  Up: Emacs for Heathens

Keystrokes
----------

   * Q: What is an experienced Emacs user?

   * A: A person who wishes that the terminal had pedals.

   Yes, when you use Emacs, you are apt to use the control key, the
shift key and the meta key a lot.  This is very annoying to some people
(notably `vi'le users), and the rest of us just love the hell out of
it.  Just give up and submit.  Emacs really does stand for
"Escape-Meta-Alt-Control-Shift", and not "Editing Macros", as you may
have heard from other disreputable sources (like the Emacs author).

   The shift key is normally located near your pinky fingers, and are
normally used to get capital letters and stuff.  You probably use it all
the time.  The control key is normally marked "CTRL" or something like
that.  The meta key is, funnily enough, never marked as such on any
keyboards.  The one I'm currently at has a key that's marked "Alt",
which is the meta key on this keyboard.  It's usually located somewhere
to the left hand side of the keyboard, usually on the bottom row.

   Now, us Emacs people doesn't say "press the meta-control-m key",
because that's just too inconvenient.  We say "press the `M-C-m' key".
`M-' is the prefix that means "meta" and "C-" is the prefix that means
"control".  So "press `C-k'" means "press down the control key, and
hold it down while you press `k'".  "Press `M-C-k'" means "press down
and hold down the meta key and the control key and then press `k'".
Simple, ay?

   This is somewhat complicated by the fact that not all keyboards have
a meta key.  In that case you can use the "escape" key.  Then `M-k'
means "press escape, release escape, press `k'".  That's much more work
than if you have a meta key, so if that's the case, I respectfully
suggest you get a real keyboard with a meta key.  You can't live without
it.


File: gnus,  Node: Emacs Lisp,  Prev: Keystrokes,  Up: Emacs for Heathens

Emacs Lisp
----------

Emacs is the King of Editors because it's really a Lisp interpreter.
Each and every key you tap runs some Emacs Lisp code snippet, and since
Emacs Lisp is an interpreted language, that means that you can configure
any key to run any arbitrary code.  You just, like, do it.

   Gnus is written in Emacs Lisp, and is run as a bunch of interpreted
functions.  (These are byte-compiled for speed, but it's still
interpreted.)  If you decide that you don't like the way Gnus does
certain things, it's trivial to have it do something a different way.
(Well, at least if you know how to write Lisp code.)  However, that's
beyond the scope of this manual, so we are simply going to talk about
some common constructs that you normally use in your `.emacs' file to
customize Gnus.

   If you want to set the variable `gnus-florgbnize' to four (4), you
write the following:

     (setq gnus-florgbnize 4)

   This function (really "special form") `setq' is the one that can set
a variable to some value.  This is really all you need to know.  Now
you can go and fill your `.emacs' file with lots of these to change how
Gnus works.

   If you have put that thing in your `.emacs' file, it will be read
and `eval'ed (which is lisp-ese for "run") the next time you start
Emacs.  If you want to change the variable right away, simply say `C-x
C-e' after the closing parenthesis.  That will `eval' the previous
"form", which here is a simple `setq' statement.

   Go ahead--just try it, if you're located at your Emacs.  After you
`C-x C-e', you will see `4' appear in the echo area, which is the
return value of the form you `eval'ed.

   Some pitfalls:

   If the manual says "set `gnus-read-active-file' to `some'", that
means:

     (setq gnus-read-active-file 'some)

   On the other hand, if the manual says "set `gnus-nntp-server' to
`nntp.ifi.uio.no'", that means:

     (setq gnus-nntp-server "nntp.ifi.uio.no")

   So be careful not to mix up strings (the latter) with symbols (the
former).  The manual is unambiguous, but it can be confusing.

   \input texinfo


File: gnus,  Node: Frequently Asked Questions,  Prev: Emacs for Heathens,  Up: Appendices

Frequently Asked Questions
==========================

This is the Gnus Frequently Asked Questions list.  If you have a Web
browser, the official hypertext version is at
`http://www.miranova.com/~steve/gnus-faq.html>', and has probably been
updated since you got this manual.

* Menu:

* Installation FAQ::      Installation of Gnus.
* Customization FAQ::     Customizing Gnus.
* Reading News FAQ::      News Reading Questions.
* Reading Mail FAQ::      Mail Reading Questions.


File: gnus,  Node: Installation FAQ,  Next: Customization FAQ,  Up: Frequently Asked Questions

Installation
------------

   * Q1.1  What is the latest version of Gnus?

     The latest (and greatest) version is 5.0.10.  You might also run
     across something called _September Gnus_.  September Gnus is the
     alpha version of the next major release of Gnus.  It is currently
     not stable enough to run unless you are prepared to debug lisp.

   * Q1.2  Where do I get Gnus?

     Any of the following locations:

        - `ftp://ftp.ifi.uio.no/pub/emacs/gnus/gnus.tar.gz'

        - `ftp://ftp.pilgrim.umass.edu/pub/misc/ding/'

        - `gopher://gopher.pilgrim.umass.edu/11/pub/misc/ding/'

        - `ftp://aphrodite.nectar.cs.cmu.edu/pub/ding-gnus/'

        - `ftp://ftp.solace.mh.se:/pub/gnu/elisp/'


   * Q1.3  Which version of Emacs do I need?

     At least GNU Emacs 19.28, or XEmacs 19.12 is recommended.  GNU
     Emacs 19.25 has been reported to work under certain circumstances,
     but it doesn't _officially_ work on it.  19.27 has also been
     reported to work.  Gnus has been reported to work under OS/2 as
     well as Unix.

   * Q1.4  Where is timezone.el?

     Upgrade to XEmacs 19.13.  In earlier versions of XEmacs this file
     was placed with Gnus 4.1.3, but that has been corrected.

   * Q1.5  When I run Gnus on XEmacs 19.13 I get weird error messages.

     You're running an old version of Gnus.  Upgrade to at least version
     5.0.4.

   * Q1.6  How do I unsubscribe from the Mailing List?

     Send an e-mail message to `ding-request@ifi.uio.no' with the magic
     word _unsubscribe_ somewhere in it, and you will be removed.

     If you are reading the digest version of the list, send an e-mail
     message to
     `ding-rn-digests-d-request@moe.shore.net' with _unsubscribe_ as
     the subject and you will be removed.

   * Q1.7  How do I run Gnus on both Emacs and XEmacs?

     The basic answer is to byte-compile under XEmacs, and then you can
     run under either Emacsen.  There is, however, a potential version
     problem with easymenu.el with Gnu Emacs prior to 19.29.

     Per Abrahamsen <abraham@dina.kvl.dk> writes :
     The internal easymenu.el interface changed between 19.28 and 19.29
     in order to make it possible to create byte compiled files that
     can be shared between Gnu Emacs and XEmacs.  The change is upward
     compatible, but not downward compatible.  This gives the following
     compatibility table:

          Compiled with:  | Can be used with:
          ----------------+--------------------------------------
          19.28           | 19.28         19.29
          19.29           |               19.29           XEmacs
          XEmacs          |               19.29           XEmacs

     If you have Gnu Emacs 19.28 or earlier, or XEmacs 19.12 or
     earlier, get a recent version of auc-menu.el from
     `ftp://ftp.iesd.auc.dk/pub/emacs-lisp/auc-menu.el', and install it
     under the name easymenu.el somewhere early in your load path.

   * Q1.8 What resources are available?

     There is the newsgroup Gnu.emacs.gnus. Discussion of Gnus 5.x is
     now taking place there. There is also a mailing list, send mail to
     `ding-request@ifi.uio.no' with the magic word _subscribe_
     somewhere in it.

     _NOTE:_ the traffic on this list is heavy so you may not want to be
     on it (unless you use Gnus as your mailer reader, that is). The
     mailing list is mainly for developers and testers.

     Gnus has a home World Wide Web page at
     `http://www.ifi.uio.no/~larsi/ding.html'.

     Gnus has a write up in the X Windows Applications FAQ at
     `http://www.ee.ryerson.ca:8080/~elf/xapps/Q-III.html'.

     The Gnus manual is also available on the World Wide Web. The
     canonical source is in Norway at
     `http://www.ifi.uio.no/~larsi/ding-manual/gnus_toc.html'.

     There are three mirrors in the United States:
       1. `http://www.miranova.com/gnus-man/'

       2.
          `http://www.pilgrim.umass.edu/pub/misc/ding/manual/gnus_toc.html'

       3. `http://www.rtd.com/~woo/gnus/'


     PostScript copies of the Gnus Reference card are available from
     `ftp://ftp.cs.ualberta.ca/pub/oolog/gnus/'.  They are mirrored at
     `ftp://ftp.pilgrim.umass.edu/pub/misc/ding/refcard/' in the United
     States. And
     `ftp://marvin.fkphy.uni-duesseldorf.de/pub/gnus/' in Germany.

     An online version of the Gnus FAQ is available at
     `http://www.miranova.com/~steve/gnus-faq.html'. Off-line formats
     are also available:
     ASCII: `ftp://ftp.miranova.com/pub/gnus/gnus-faq'
     PostScript: `ftp://ftp.miranova.com/pub/gnus/gnus-faq.ps'.

   * Q1.9  Gnus hangs on connecting to NNTP server

     I am running XEmacs on SunOS and Gnus prints a message about
     Connecting to NNTP server and then just hangs.

     Ben Wing <wing@netcom.com> writes :
     I wonder if you're hitting the infamous _libresolv_ problem.  The
     basic problem is that under SunOS you can compile either with DNS
     or NIS name lookup libraries but not both.  Try substituting the
     IP address and see if that works; if so, you need to download the
     sources and recompile.

   * Q1.10  Mailcrypt 3.4 doesn't work

     This problem is verified to still exist in Gnus 5.0.9 and
     MailCrypt 3.4.  The answer comes from Peter Arius
     <arius@immd2.informatik.uni-erlangen.de>.

     I found out that mailcrypt uses `gnus-eval-in-buffer-window',
     which is a macro.  It seems as if you have compiled mailcrypt with
     plain old GNUS in load path, and the XEmacs byte compiler has
     inserted that macro definition into `mc-toplev.elc'.  The solution
     is to recompile `mc-toplev.el' with Gnus 5 in load-path, and it
     works fine.

     Steve Baur <steve@miranova.com> adds :
     The problem also manifests itself if neither GNUS 4 nor Gnus 5 is
     in the load-path.

   * Q1.11  What other packages work with Gnus?

        - Mailcrypt.

          Mailcrypt is an Emacs interface to PGP.  It works, it installs
          without hassle, and integrates very easily.  Mailcrypt can be
          obtained from
          `ftp://cag.lcs.mit.edu/pub/patl/mailcrypt-3.4.tar.gz'.

        - Tiny Mime.

          Tiny Mime is an Emacs MUA interface to MIME.  Installation is
          a two-step process unlike most other packages, so you should
          be prepared to move the byte-compiled code somewhere.  There
          are currently two versions of this package available.  It can
          be obtained from
          `ftp://ftp.jaist.ac.jp/pub/GNU/elisp/'.  Be sure to apply the
          supplied patch.  It works with Gnus through version 5.0.9.
          In order for all dependencies to work correctly the load
          sequence is as follows:
                 (load "tm-setup")
                 (load "gnus")
                 (load "mime-compose")

          _NOTE:_ Loading the package disables citation highlighting by
          default.  To get the old behavior back, use the `M-t' command.




File: gnus,  Node: Customization FAQ,  Next: Reading News FAQ,  Prev: Installation FAQ,  Up: Frequently Asked Questions

Customization
-------------

   * Q2.1  Custom Edit does not work under XEmacs

     The custom package has not been ported to XEmacs.

   * Q2.2  How do I quote messages?

     I see lots of messages with quoted material in them.  I am
     wondering how to have Gnus do it for me.

     This is Gnus, so there are a number of ways of doing this.  You
     can use the built-in commands to do this.  There are the `F' and
     `R' keys from the summary buffer which automatically include the
     article being responded to.  These commands are also selectable as
     Followup and Yank and Reply and Yank in the Post menu.

     `C-c C-y' grabs the previous message and prefixes each line with
     `ail-indentation-spaces' spaces or `mail-yank-prefix' if that is
     non-nil, unless you have set your own `mail-citation-hook', which
     will be called to to do the job.

     You might also consider the Supercite package, which allows for
     pretty arbitrarily complex quoting styles.  Some people love it,
     some people hate it.

   * Q2.3 How can I keep my nnvirtual:* groups sorted?

     How can I most efficiently arrange matters so as to keep my
     nnvirtual:* (etc) groups at the top of my group selection buffer,
     whilst keeping everything sorted in alphabetical order.

     If you don't subscribe often to new groups then the easiest way is
     to first sort the groups and then manually kill and yank the
     virtuals wherever you want them.

   * Q2.4  Any good suggestions on stuff for an all.SCORE file?

     Here is a collection of suggestions from the Gnus mailing list.

       1. From "Dave Disser" <disser@sdd.hp.com>
          I like blasting anything without lowercase letters.  Weeds
          out most of the make $$ fast, as well as the lame titles like
          "IBM" and "HP-UX" with no further description.
                (("Subject"
                 ("^\\(Re: \\)?[^a-z]*$" -200 nil R)))

       2. From "Peter Arius" <arius@immd2.informatik.uni-erlangen.de>
          The most vital entries in my (still young) all.SCORE:
               (("xref"
                 ("alt.fan.oj-simpson" -1000 nil s))
                ("subject"
                 ("\\<\\(make\\|fast\\|big\\)\\s-*\\(money\\|cash\\|bucks?\\)\\>" -1000 nil r)
                 ("$$$$" -1000 nil s)))

       3. From "Per Abrahamsen" <abraham@dina.kvl.dk>
               (("subject"
                 ;; CAPS OF THE WORLD, UNITE
                 ("^..[^a-z]+$" -1 nil R)
                 ;; $$$ Make Money $$$ (Try work)
                 ("$" -1 nil s)
                 ;; I'm important! And I have exclamation marks to prove it!
                 ("!" -1 nil s)))

       4. From "heddy boubaker" <boubaker@cenatls.cena.dgac.fr>
          I  would like to contribute with mine.
               (
                (read-only t)
                ("subject"
                 ;; ALL CAPS SUBJECTS
                 ("^\\([Rr][Ee]: +\\)?[^a-z]+$" -1 nil R)
                 ;; $$$ Make Money $$$
                 ("$$" -10 nil s)
                 ;; Empty subjects are worthless!
                 ("^ *\\([(<]none[>)]\\|(no subject\\( given\\)?)\\)? *$" -10 nil r)
                 ;; Sometimes interesting announces occur!
                 ("ANN?OU?NC\\(E\\|ING\\)" +10 nil r)
                 ;; Some people think they're on mailing lists
                 ("\\(un\\)?sub?scribe" -100 nil r)
                 ;; Stop Micro$oft NOW!!
                 ("\\(m\\(icro\\)?[s$]\\(oft\\|lot\\)?-?\\)?wind?\\(ows\\|aube\\|oze\\)?[- ]*\\('?95\\|NT\\|3[.]1\\|32\\)" -1001 nil r)
                 ;; I've nothing to buy
                 ("\\(for\\|4\\)[- ]*sale" -100 nil r)
                 ;; SELF-DISCIPLINED people
                 ("\\[[^a-z0-9 \t\n][^a-z0-9 \t\n]\\]" +100 nil r)
                 )
                ("from"
                 ;; To keep track of posters from my site
                 (".dgac.fr" +1000 nil s))
                ("followup"
                 ;; Keep track of answers to my posts
                 ("boubaker" +1000 nil s))
                ("lines"
                 ;; Some people have really nothing to say!!
                 (1 -10 nil <=))
                (mark -100)
                (expunge -1000)
                )

       5. From "Christopher Jones" <cjones@au.oracle.com>
          The sample `all.SCORE' files from Per and boubaker could be
          augmented with:
               	(("subject"
               	  ;; No junk mail please!
               	  ("please ignore" -500 nil s)
               	  ("test" -500 nil e))
               	)

       6. From "Brian Edmonds" <edmonds@cs.ubc.ca>
          Augment any of the above with a fast method of scoring down
          excessively cross posted articles.
                ("xref"
                 ;; the more cross posting, the exponentially worse the article
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+" -1 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -2 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -4 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -8 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -16 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -32 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -64 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -128 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -256 nil r)
                 ("^xref: \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+ \\S-+" -512 nil r))


   * Q2.5  What do I use to yank-through when replying?

     You should probably reply and followup with `R' and `F', instead
     of `r' and `f', which solves your problem.  But you could try
     something like:

          (defconst mail-yank-ignored-headers
            "^.*:"
            "Delete these headers from old message when it's inserted in a reply.")

   * Q2.6  I don't like the default WWW browser

     Now when choosing an URL Gnus starts up a W3 buffer, I would like
     it to always use Netscape (I don't browse in text-mode ;-).

       1. Activate `Customize...' from the `Help' menu.

       2. Scroll down to the `WWW Browser' field.

       3. Click `mouse-2' on `WWW Browser'.

       4. Select `Netscape' from the pop up menu.

       5. Press `C-c C-c'


     If you are using XEmacs then to specify Netscape do
            (setq gnus-button-url 'gnus-netscape-open-url)

   * Q2.7 What, if any, relation is between "ask-server" and "(setq
     gnus-read-active-file 'some)"?

     In order for Gnus to show you the complete list of newsgroups, it
     will either have to either store the list locally, or ask the
     server to transmit the list. You enable the first with

                  (setq gnus-save-killed-list t)

     and the second with

                  (setq gnus-read-active-file t)

     If both are disabled, Gnus will not know what newsgroups exists.
     There is no option to get the list by casting a spell.

   * Q2.8  Moving between groups is slow.

     Per Abrahamsen <abraham@dina.kvl.dk> writes:
     Do you call `define-key' or something like that in one of the
     summary mode hooks?  This would force Emacs to recalculate the
     keyboard shortcuts.  Removing the call should speed up `M-x
     gnus-summary-mode RET' by a couple of orders of magnitude.  You
     can use

          (define-key gnus-summary-mode-map KEY COMMAND)

     in your `.gnus' instead.



File: gnus,  Node: Reading News FAQ,  Next: Reading Mail FAQ,  Prev: Customization FAQ,  Up: Frequently Asked Questions

Reading News
------------

   * Q3.1  How do I convert my kill files to score files?

     A kill-to-score translator was written by Ethan Bradford
     <ethanb@ptolemy.astro.washington.edu>.  It is available from
     `http://baugi.ifi.uio.no/~larsi/ding-various/gnus-kill-to-score.el'.

   * Q3.2 My news server has a lot of groups, and killing groups is
     painfully slow.

     Don't do that then.  The best way to get rid of groups that should
     be dead is to edit your newsrc directly.  This problem will be
     addressed in the near future.

   * Q3.3  How do I use an NNTP server with authentication?

     Put the following into your .gnus:
           (add-hook 'nntp-server-opened-hook 'nntp-send-authinfo)

   * Q3.4  Not reading the first article.

     How do I avoid reading the first article when a group is selected?

       1. Use `RET' to select the group instead of `SPC'.

       2. `(setq gnus-auto-select first nil)'

       3. Luis Fernandes <elf@mailhost.ee.ryerson.ca>writes:
          This is what I use...customize as necessary...

               ;;; Don't auto-select first article if reading sources, or archives or
               ;;; jobs postings, etc. and just display the summary buffer
               (add-hook 'gnus-select-group-hook
               	  (function
               	   (lambda ()
               	     (cond ((string-match "sources" gnus-newsgroup-name)
               		    (setq gnus-auto-select-first nil))
               			   ((string-match "jobs" gnus-newsgroup-name)
               				(setq gnus-auto-select-first nil))
               		   ((string-match "comp\\.archives" gnus-newsgroup-name)
               		    (setq gnus-auto-select-first nil))
               		   ((string-match "reviews" gnus-newsgroup-name)
               		    (setq gnus-auto-select-first nil))
               		   ((string-match "announce" gnus-newsgroup-name)
               		    (setq gnus-auto-select-first nil))
               		   ((string-match "binaries" gnus-newsgroup-name)
               		    (setq gnus-auto-select-first nil))
               		   (t
               		    (setq gnus-auto-select-first t))))))

       4. Per Abrahamsen <abraham@dina.kvl.dk> writes:
          Another possibility is to create an `all.binaries.all.SCORE'
          file like this:

               ((local
                 (gnus-auto-select-first nil)))

          and insert
               	(setq gnus-auto-select-first t)

          in your `.gnus'.


   * Q3.5  Why aren't BBDB known posters marked in the summary buffer?

     Brian Edmonds <edmonds@cs.ubc.ca> writes:
     Due to changes in Gnus 5.0, `bbdb-gnus.el' no longer marks known
     posters in the summary buffer.  An updated version, `gnus-bbdb.el'
     is available at the locations listed below.  This package also
     supports autofiling of incoming mail to folders specified in the
     BBDB.  Extensive instructions are included as comments in the file.

     Send mail to `majordomo@edmonds.home.cs.ubc.ca' with the following
     line in the body of the message: _get misc gnus-bbdb.el_.

     Or get it from the World Wide Web:
     `http://www.cs.ubc.ca/spider/edmonds/gnus-bbdb.el'.



File: gnus,  Node: Reading Mail FAQ,  Prev: Reading News FAQ,  Up: Frequently Asked Questions

Reading Mail
------------

   * Q4.1 What does the message "Buffer has changed on disk" mean in a
     mail group?

     Your filter program should not deliver mail directly to your
     folders, instead it should put the mail into spool files.  Gnus
     will then move the mail safely from the spool files into the
     folders.  This will eliminate the problem.  Look it up in the
     manual, in the section entitled "Mail & Procmail".

   * Q4.2  How do you make articles un-expirable?

     I am using nnml to read news and have used
     `gnus-auto-expirable-newsgroups' to automagically expire articles
     in some groups (Gnus being one of them).  Sometimes there are
     interesting articles in these groups that I want to keep.  Is
     there any way of explicitly marking an article as un-expirable -
     that is mark it as read but not expirable?

     Use `u', `!', `d' or `M-u' in the summary buffer. You just remove
     the `E' mark by setting some other mark. It's not necessary to
     tick the articles.

   * Q4.3  How do I delete bogus nnml: groups?

     My problem is that I have various mail (nnml) groups generated
     while experimenting with Gnus. How do I remove them now? Setting
     the level to 9 does not help. Also `gnus-group-check-bogus-groups'
     does not recognize them.

     Removing mail groups is tricky at the moment. (It's on the to-do
     list, though.) You basically have to kill the groups in Gnus, shut
     down Gnus, edit the active file to exclude these groups, and
     probably remove the nnml directories that contained these groups
     as well. Then start Gnus back up again.

   * Q4.4  What happened to my new mail groups?

     I got new mail, but I have never seen the groups they should have
     been placed in.

     They are probably there, but as zombies. Press `A z' to list
     zombie groups, and then subscribe to the groups you want with `u'.
     This is all documented quite nicely in the user's manual.

   * Q4.5  Not scoring mail groups

     How do you _totally_ turn off scoring in mail groups?

     Use an nnbabyl:all.SCORE (or nnmh, or nnml, or whatever) file
     containing:

          ((adapt ignore)
           (local (gnus-use-scoring nil))
           (exclude-files "all.SCORE"))



File: gnus,  Node: Index,  Next: Key Index,  Prev: Appendices,  Up: Top

Index
*****

* Menu:

* *:                                     Group Line Specification.
* .newsrc:                               Startup Files.
* 1153 digest:                           Document Groups.
* <:                                     Customizing Threading.
* >:                                     Customizing Threading.
* activating groups:                     Scanning New Messages.
* active file <1>:                       Terminology.
* active file:                           The Active File.
* adaptive scoring:                      Adaptive Scoring.
* adopting articles:                     Customizing Threading.
* ange-ftp:                              Group Information.
* archived messages:                     Archived Messages.
* article:                               Terminology.
* article backlog:                       Article Backlog.
* article buffer:                        The Article Buffer.
* article caching:                       Article Caching.
* article customization:                 Customizing Articles.
* article expiry:                        Expiring Mail.
* article hiding:                        Article Hiding.
* article marking:                       Marking Articles.
* article scrolling:                     Paging the Article.
* article threading:                     Threading.
* article ticking:                       Marking Articles.
* article washing:                       Article Washing.
* asynchronous article fetching:         Asynchronous Fetching.
* authentification:                      NNTP.
* authinfo:                              NNTP.
* auto-expire:                           Group Parameters.
* auto-save:                             Auto Save.
* babyl:                                 Document Groups.
* backend:                               Terminology.
* backlog:                               Article Backlog.
* bbb-summary-rate-article:              Rating Articles.
* binary groups:                         Binary Groups.
* body:                                  Terminology.
* bogus groups <1>:                      Terminology.
* bogus groups:                          Group Maintenance.
* bookmarks:                             Other Marks.
* bouncing mail:                         Summary Mail Commands.
* broken-reply-to:                       Group Parameters.
* browsing servers:                      Browse Foreign Server.
* bugs <1>:                              Troubleshooting.
* bugs:                                  Compatibility.
* buttons <1>:                           Buttons.
* buttons:                               Article Buttons.
* byte-compilation:                      Compilation.
* caching:                               Article Caching.
* canceling articles:                    Canceling and Superseding.
* CancelMoose[tm]:                       NoCeM.
* characters in file names:              Various Various.
* Chris Lewis:                           NoCeM.
* ClariNet Briefs:                       Foreign Groups.
* click:                                 Buttons.
* compatibility:                         Compatibility.
* compilation:                           Compilation.
* composing mail:                        Summary Mail Commands.
* composing news:                        Summary Post Commands.
* contributors:                          Contributors.
* copy mail:                             Mail Group Commands.
* cross-posting:                         Exiting the Summary Buffer.
* crosspost:                             Splitting Mail.
* crosspost mail:                        Mail Group Commands.
* crossposts:                            Scoring Tips.
* customizing threading:                 Customizing Threading.
* daemons:                               Daemons.
* decoding articles:                     Decoding Articles.
* delete-file:                           Mail Backend Variables.
* deleting headers:                      Hiding Headers.
* deleting incoming files:               Mail Backend Variables.
* demons:                                Daemons.
* describing groups:                     Group Information.
* digest:                                Document Groups.
* ding mailing list:                     Troubleshooting.
* directory groups:                      Directory Groups.
* disk space:                            Little Disk Space.
* display-time:                          Mode Lines.
* documentation group:                   Document Groups.
* dribble file:                          Auto Save.
* duplicate mails:                       Duplicates.
* dynamic IP addresses:                  NNTP.
* elm:                                   Mail and Procmail.
* Emacs:                                 Emacsen.
* Emacsen <1>:                           Emacs/XEmacs Code.
* Emacsen:                               Emacsen.
* exiting Gnus:                          Exiting Gnus.
* exiting groups:                        Exiting the Summary Buffer.
* expirable mark:                        Read Articles.
* expiry-wait:                           Group Parameters.
* fancy mail splitting:                  Fancy Mail Splitting.
* FAQ:                                   Group Information.
* file commands:                         File Commands.
* file names:                            Various Various.
* first time usage:                      The First Time.
* follow up:                             Terminology.
* followup:                              Composing Messages.
* foreign:                               Terminology.
* foreign groups:                        Select Methods.
* foreign servers:                       Browse Foreign Server.
* formatting variables:                  Formatting Variables.
* forwarded messages:                    Document Groups.
* fuzzy article gathering:               Customizing Threading.
* Gcc:                                   Archived Messages.
* general customization:                 Customization.
* global score files:                    Global Score Files.
* gnu.emacs.gnus:                        Troubleshooting.
* gnus:                                  Starting Up.
* gnus-activate-all-groups:              Scanning New Messages.
* gnus-activate-foreign-newsgroups:      Foreign Groups.
* gnus-activate-level:                   Group Levels.
* gnus-adaptive-file-suffix:             Adaptive Scoring.
* gnus-add-configuration:                Windows Configuration.
* gnus-after-getting-new-news-hook:      Scanning New Messages.
* gnus-ancient-mark:                     Read Articles.
* gnus-apply-kill-file:                  Kill Files.
* gnus-apply-kill-file-unless-scored:    Kill Files.
* gnus-apply-kill-hook:                  Kill Files.
* gnus-article-add-buttons:              Article Washing.
* gnus-article-add-buttons-to-head:      Article Washing.
* gnus-article-button-face:              Article Buttons.
* gnus-article-date-lapsed:              Article Date.
* gnus-article-date-local:               Article Date.
* gnus-article-date-original:            Article Date.
* gnus-article-date-ut:                  Article Date.
* gnus-article-de-quoted-unreadable:     Article Washing.
* gnus-article-describe-briefly:         Article Keymap.
* gnus-article-display-hook <1>:         Hiding Headers.
* gnus-article-display-hook <2>:         Hard Picons.
* gnus-article-display-hook <3>:         Customizing Articles.
* gnus-article-display-hook:             Misc Article.
* gnus-article-display-picons:           Hard Picons.
* gnus-article-display-x-face:           Article Washing.
* gnus-article-fill-cited-article:       Article Washing.
* gnus-article-hide:                     Article Hiding.
* gnus-article-hide-boring-headers <1>:  Article Hiding.
* gnus-article-hide-boring-headers:      Hiding Headers.
* gnus-article-hide-citation:            Article Hiding.
* gnus-article-hide-citation-in-followups: Article Hiding.
* gnus-article-hide-headers:             Article Hiding.
* gnus-article-hide-pgp:                 Article Hiding.
* gnus-article-hide-signature:           Article Hiding.
* gnus-article-highlight:                Article Highlighting.
* gnus-article-highlight-citation:       Article Highlighting.
* gnus-article-highlight-headers:        Article Highlighting.
* gnus-article-highlight-signature:      Article Highlighting.
* gnus-article-mail:                     Article Keymap.
* gnus-article-maybe-highlight:          Customizing Articles.
* gnus-article-menu-hook:                Highlighting and Menus.
* gnus-article-mode-hook:                Misc Article.
* gnus-article-mode-line-format:         Misc Article.
* gnus-article-mouse-face:               Article Buttons.
* gnus-article-next-button:              Article Keymap.
* gnus-article-next-page:                Article Keymap.
* gnus-article-prepare-hook:             Misc Article.
* gnus-article-prev-button:              Article Keymap.
* gnus-article-prev-page:                Article Keymap.
* gnus-article-refer-article:            Article Keymap.
* gnus-article-remove-cr:                Article Washing.
* gnus-article-remove-trailing-blank-lines: Article Washing.
* gnus-article-save-directory:           Saving Articles.
* gnus-article-show-summary:             Article Keymap.
* gnus-article-sort-by-author:           Sorting.
* gnus-article-sort-by-date:             Sorting.
* gnus-article-sort-by-number:           Sorting.
* gnus-article-sort-by-score:            Sorting.
* gnus-article-sort-by-subject:          Sorting.
* gnus-article-sort-functions:           Sorting.
* gnus-article-treat-overstrike:         Article Washing.
* gnus-article-x-face-command:           Article Washing.
* gnus-article-x-face-too-ugly:          Article Washing.
* gnus-asynchronous:                     Asynchronous Fetching.
* gnus-asynchronous-article-function:    Asynchronous Fetching.
* gnus-auto-center-summary:              Summary Maneuvering.
* gnus-auto-expirable-newsgroups:        Expiring Mail.
* gnus-auto-extend-newsgroup:            Choosing Articles.
* gnus-auto-select-first:                Selecting a Group.
* gnus-auto-select-next:                 Summary Maneuvering.
* gnus-auto-select-same:                 Summary Maneuvering.
* gnus-auto-subscribed-groups:           New Groups.
* gnus-background-mode:                  Highlighting and Menus.
* gnus-binary-mode:                      Binary Groups.
* gnus-binary-mode-hook:                 Binary Groups.
* gnus-binary-show-article:              Binary Groups.
* gnus-boring-article-headers:           Hiding Headers.
* gnus-break-pages:                      Misc Article.
* gnus-browse-describe-briefly:          Browse Foreign Server.
* gnus-browse-exit:                      Browse Foreign Server.
* gnus-browse-menu-hook:                 Highlighting and Menus.
* gnus-browse-mode:                      Browse Foreign Server.
* gnus-browse-read-group:                Browse Foreign Server.
* gnus-browse-select-group:              Browse Foreign Server.
* gnus-browse-unsubscribe-current-group: Browse Foreign Server.
* gnus-buffer-configuration:             Windows Configuration.
* gnus-bug <1>:                          Compatibility.
* gnus-bug:                              Troubleshooting.
* gnus-build-sparse-threads:             Customizing Threading.
* gnus-button-alist:                     Article Buttons.
* gnus-button-url-regexp:                Article Buttons.
* gnus-cache-active-file:                Article Caching.
* gnus-cache-directory:                  Article Caching.
* gnus-cache-enter-article:              Persistent Articles.
* gnus-cache-enter-articles:             Article Caching.
* gnus-cache-generate-active:            Article Caching.
* gnus-cache-generate-nov-databases:     Article Caching.
* gnus-cache-remove-article:             Persistent Articles.
* gnus-cache-remove-articles:            Article Caching.
* gnus-cached-mark:                      Other Marks.
* gnus-canceled-mark:                    Read Articles.
* gnus-carpal:                           Buttons.
* gnus-carpal-browse-buffer-buttons:     Buttons.
* gnus-carpal-button-face:               Buttons.
* gnus-carpal-group-buffer-buttons:      Buttons.
* gnus-carpal-header-face:               Buttons.
* gnus-carpal-mode-hook:                 Buttons.
* gnus-carpal-server-buffer-buttons:     Buttons.
* gnus-carpal-summary-buffer-buttons:    Buttons.
* gnus-catchup-mark:                     Read Articles.
* gnus-check-bogus-newsgroups:           Startup Variables.
* gnus-check-new-newsgroups:             New Groups.
* gnus-cite-attribution-face:            Article Highlighting.
* gnus-cite-attribution-prefix:          Article Highlighting.
* gnus-cite-attribution-suffix:          Article Highlighting.
* gnus-cite-face-list:                   Article Highlighting.
* gnus-cite-hide-absolute:               Article Hiding.
* gnus-cite-hide-percentage:             Article Hiding.
* gnus-cite-max-prefix:                  Article Highlighting.
* gnus-cite-minimum-match-count:         Article Highlighting.
* gnus-cite-parse-max-size:              Article Highlighting.
* gnus-cite-prefix-regexp:               Article Highlighting.
* gnus-cited-lines-visible:              Article Hiding.
* gnus-cited-text-button-line-format:    Article Hiding.
* gnus-compile:                          Compilation.
* gnus-configure-frame:                  Windows Configuration.
* gnus-dead-summary-mode:                Exiting the Summary Buffer.
* gnus-default-adaptive-score-alist:     Adaptive Scoring.
* gnus-default-article-saver:            Saving Articles.
* gnus-default-subscribed-newsgroups:    The First Time.
* gnus-del-mark:                         Read Articles.
* gnus-demon-add-disconnection:          Daemons.
* gnus-demon-add-handler:                Daemons.
* gnus-demon-add-nocem:                  Daemons.
* gnus-demon-add-scanmail:               Daemons.
* gnus-demon-cancel:                     Daemons.
* gnus-demon-handlers:                   Daemons.
* gnus-demon-init:                       Daemons.
* gnus-demon-timestep:                   Daemons.
* gnus-display-type:                     Highlighting and Menus.
* gnus-dormant-mark:                     Unread Articles.
* gnus-dribble-directory:                Auto Save.
* gnus-empty-thread-mark:                Other Marks.
* gnus-exit-gnus-hook:                   Exiting Gnus.
* gnus-exit-group-hook:                  Exiting the Summary Buffer.
* gnus-expert-user:                      Interactive.
* gnus-expirable-mark:                   Read Articles.
* gnus-extract-address-components:       Summary Buffer Format.
* gnus-fetch-group:                      Fetching a Group.
* gnus-fetch-old-headers:                Customizing Threading.
* gnus-file-save-name:                   Saving Articles.
* gnus-find-new-newsgroups:              Group Maintenance.
* gnus-folder-save-name:                 Saving Articles.
* gnus-Folder-save-name:                 Saving Articles.
* gnus-folder-save-name:                 Saving Articles.
* gnus-gather-threads-by-references:     Customizing Threading.
* gnus-gather-threads-by-subject:        Customizing Threading.
* gnus-generate-horizontal-tree:         Tree Display.
* gnus-generate-tree-function:           Tree Display.
* gnus-generate-vertical-tree:           Tree Display.
* gnus-get-new-news-hook:                Scanning New Messages.
* gnus-global-score-files:               Global Score Files.
* gnus-goto-next-group-when-activating:  Scanning New Messages.
* gnus-group-add-to-virtual:             Foreign Groups.
* gnus-group-apropos:                    Listing Groups.
* gnus-group-archive-directory:          Foreign Groups.
* gnus-group-best-unread-group:          Group Maneuvering.
* gnus-group-brew-soup:                  SOUP Commands.
* gnus-group-browse-foreign-server <1>:  Browse Foreign Server.
* gnus-group-browse-foreign-server:      Finding the News.
* gnus-group-catchup-current:            Selecting a Group.
* gnus-group-catchup-current-all:        Selecting a Group.
* gnus-group-catchup-group-hook:         Selecting a Group.
* gnus-group-check-bogus-groups:         Group Maintenance.
* gnus-group-default-list-level:         Group Levels.
* gnus-group-delete-group:               Foreign Groups.
* gnus-group-describe-all-groups:        Group Information.
* gnus-group-describe-briefly:           Group Information.
* gnus-group-describe-group:             Group Information.
* gnus-group-description-apropos:        Listing Groups.
* gnus-group-edit-global-kill:           Kill Files.
* gnus-group-edit-group:                 Foreign Groups.
* gnus-group-edit-group-method:          Foreign Groups.
* gnus-group-edit-group-parameters:      Foreign Groups.
* gnus-group-edit-local-kill:            Kill Files.
* gnus-group-enter-directory:            Foreign Groups.
* gnus-group-enter-server-mode:          Misc Group Stuff.
* gnus-group-exit:                       Exiting Gnus.
* gnus-group-expire-all-groups:          Group Maintenance.
* gnus-group-expire-articles:            Group Maintenance.
* gnus-group-faq-directory:              Summary Group Information.
* gnus-group-fetch-faq:                  Group Information.
* gnus-group-first-unread-group:         Group Maneuvering.
* gnus-group-get-new-news:               Scanning New Messages.
* gnus-group-get-new-news-this-group:    Scanning New Messages.
* gnus-group-goto-unread:                Group Maneuvering.
* gnus-group-highlight:                  Group Highlighting.
* gnus-group-highlight-line:             Group Highlighting.
* gnus-group-jump-to-group:              Group Maneuvering.
* gnus-group-kill-all-zombies:           Subscription Commands.
* gnus-group-kill-group:                 Subscription Commands.
* gnus-group-kill-level:                 Subscription Commands.
* gnus-group-kill-region:                Subscription Commands.
* gnus-group-line-format:                Group Line Specification.
* gnus-group-list-active:                Listing Groups.
* gnus-group-list-all-groups:            Listing Groups.
* gnus-group-list-all-matching:          Listing Groups.
* gnus-group-list-groups:                Listing Groups.
* gnus-group-list-inactive-groups:       Group Levels.
* gnus-group-list-killed:                Listing Groups.
* gnus-group-list-level:                 Listing Groups.
* gnus-group-list-matching:              Listing Groups.
* gnus-group-list-zombies:               Listing Groups.
* gnus-group-mail:                       Misc Group Stuff.
* gnus-group-make-archive-group:         Foreign Groups.
* gnus-group-make-directory-group:       Foreign Groups.
* gnus-group-make-doc-group:             Foreign Groups.
* gnus-group-make-empty-virtual:         Foreign Groups.
* gnus-group-make-group:                 Foreign Groups.
* gnus-group-make-help-group:            Foreign Groups.
* gnus-group-make-kiboze-group:          Foreign Groups.
* gnus-group-mark-buffer:                Marking Groups.
* gnus-group-mark-group:                 Marking Groups.
* gnus-group-mark-regexp:                Marking Groups.
* gnus-group-mark-region:                Marking Groups.
* gnus-group-menu-hook:                  Highlighting and Menus.
* gnus-group-mode-hook:                  Misc Group Stuff.
* gnus-group-mode-line-format:           Group Modeline Specification.
* gnus-group-next-group <1>:             Group Maneuvering.
* gnus-group-next-group:                 Browse Foreign Server.
* gnus-group-next-unread-group:          Group Maneuvering.
* gnus-group-next-unread-group-same-level: Group Maneuvering.
* gnus-group-post-news:                  Misc Group Stuff.
* gnus-group-prepare-hook:               Misc Group Stuff.
* gnus-group-prev-group <1>:             Browse Foreign Server.
* gnus-group-prev-group:                 Group Maneuvering.
* gnus-group-prev-unread-group:          Group Maneuvering.
* gnus-group-prev-unread-group-same-level: Group Maneuvering.
* gnus-group-quick-select-group:         Selecting a Group.
* gnus-group-quit:                       Exiting Gnus.
* gnus-group-read-group:                 Selecting a Group.
* gnus-group-read-init-file:             File Commands.
* gnus-group-recent-archive-directory:   Foreign Groups.
* gnus-group-rename-group:               Foreign Groups.
* gnus-group-restart:                    Scanning New Messages.
* gnus-group-save-newsrc:                File Commands.
* gnus-group-select-group:               Selecting a Group.
* gnus-group-set-current-level:          Group Levels.
* gnus-group-sort-by-alphabet:           Sorting Groups.
* gnus-group-sort-by-level:              Sorting Groups.
* gnus-group-sort-by-method:             Sorting Groups.
* gnus-group-sort-by-rank:               Sorting Groups.
* gnus-group-sort-by-score:              Sorting Groups.
* gnus-group-sort-by-unread:             Sorting Groups.
* gnus-group-sort-function:              Sorting Groups.
* gnus-group-sort-groups:                Sorting Groups.
* gnus-group-sort-groups-by-alphabet:    Sorting Groups.
* gnus-group-sort-groups-by-level:       Sorting Groups.
* gnus-group-sort-groups-by-method:      Sorting Groups.
* gnus-group-sort-groups-by-rank:        Sorting Groups.
* gnus-group-sort-groups-by-score:       Sorting Groups.
* gnus-group-sort-groups-by-unread:      Sorting Groups.
* gnus-group-suspend:                    Exiting Gnus.
* gnus-group-transpose-groups:           Subscription Commands.
* gnus-group-uncollapsed-levels:         Group Line Specification.
* gnus-group-universal-argument:         Marking Groups.
* gnus-group-unmark-all-groups:          Marking Groups.
* gnus-group-unmark-group:               Marking Groups.
* gnus-group-unsubscribe-current-group:  Subscription Commands.
* gnus-group-unsubscribe-group:          Subscription Commands.
* gnus-group-update-hook:                Group Highlighting.
* gnus-group-use-permanent-levels:       Group Levels.
* gnus-group-visible-select-group:       Selecting a Group.
* gnus-group-yank-group:                 Subscription Commands.
* gnus-grouplens-override-scoring:       Displaying Predictions.
* gnus-header-button-alist:              Article Buttons.
* gnus-header-face-alist:                Article Highlighting.
* gnus-hidden-properties:                Various Various.
* gnus-ignored-headers:                  Hiding Headers.
* gnus-ignored-newsgroups:               The Active File.
* gnus-inews-article-hook:               Followups To Yourself.
* gnus-info-find-node <1>:               Summary Group Information.
* gnus-info-find-node:                   Group Information.
* gnus-inhibit-startup-message:          Startup Variables.
* gnus-init-file:                        File Commands.
* gnus-insert-pseudo-articles:           Viewing Files.
* gnus-interactive-catchup:              Interactive.
* gnus-interactive-exit:                 Interactive.
* gnus-jog-cache:                        Article Caching.
* gnus-keep-backlog:                     Article Backlog.
* gnus-keep-same-level:                  Group Levels.
* gnus-kill-file-mark:                   Read Articles.
* gnus-kill-file-mode-hook:              Kill Files.
* gnus-kill-file-name:                   Kill Files.
* gnus-kill-files-directory:             Score Variables.
* gnus-kill-killed:                      Score Variables.
* gnus-kill-save-kill-file:              Kill Files.
* gnus-kill-summary-on-exit:             Exiting the Summary Buffer.
* gnus-killed-mark:                      Read Articles.
* gnus-large-newsgroup:                  Selecting a Group.
* gnus-level-default-subscribed:         Group Levels.
* gnus-level-default-unsubscribed:       Group Levels.
* gnus-level-killed:                     Group Levels.
* gnus-level-subscribed:                 Group Levels.
* gnus-level-unsubscribed:               Group Levels.
* gnus-level-zombie:                     Group Levels.
* gnus-list-groups-with-ticked-articles: Listing Groups.
* gnus-load-hook:                        Startup Variables.
* gnus-low-score-mark:                   Read Articles.
* gnus-mail-save-name:                   Saving Articles.
* gnus-mailing-list-groups:              Mail and Post.
* gnus-mark-article-hook:                Choosing Articles.
* gnus-message-archive-group:            Archived Messages.
* gnus-message-archive-method:           Archived Messages.
* gnus-mode-non-string-length:           Mode Lines.
* gnus-mouse-face:                       Highlighting and Menus.
* gnus-move-split-methods:               Mail Group Commands.
* gnus-nntp-server:                      Finding the News.
* gnus-nntpserver-file:                  Finding the News.
* gnus-no-groups-message:                Startup Variables.
* gnus-no-server:                        The Server is Down.
* gnus-nocem-directory:                  NoCeM.
* gnus-nocem-expiry-wait:                NoCeM.
* gnus-nocem-groups:                     NoCeM.
* gnus-nocem-issuers:                    NoCeM.
* gnus-not-empty-thread-mark:            Other Marks.
* gnus-nov-is-evil:                      Exiting the Summary Buffer.
* gnus-novice-user:                      Interactive.
* gnus-numeric-save-name:                Saving Articles.
* gnus-Numeric-save-name:                Saving Articles.
* gnus-options-not-subscribe:            New Groups.
* gnus-options-subscribe:                New Groups.
* gnus-other-frame:                      Starting Up.
* gnus-outgoing-message-group:           Archived Messages.
* gnus-page-delimiter:                   Misc Article.
* gnus-parse-headers-hook:               Various Various.
* gnus-permanently-visible-groups <1>:   Listing Groups.
* gnus-permanently-visible-groups:       Misc Group Stuff.
* gnus-pick-display-summary:             Pick and Read.
* gnus-pick-mode:                        Pick and Read.
* gnus-pick-mode-hook:                   Pick and Read.
* gnus-pick-start-reading:               Pick and Read.
* gnus-picons-buffer:                    Picon Configuration.
* gnus-picons-convert-x-face <1>:        Picon Configuration.
* gnus-picons-convert-x-face:            Picon Requirements.
* gnus-picons-database <1>:              Picon Basics.
* gnus-picons-database:                  Picon Configuration.
* gnus-picons-display-where:             Hard Picons.
* gnus-picons-domain-directories:        Picon Configuration.
* gnus-picons-news-directory:            Picon Configuration.
* gnus-picons-user-directories:          Picon Configuration.
* gnus-picons-x-face-file-name:          Picon Configuration.
* gnus-plain-save-name:                  Saving Articles.
* gnus-Plain-save-name:                  Saving Articles.
* gnus-plain-save-name:                  Saving Articles.
* gnus-post-method:                      Posting Server.
* gnus-process-mark:                     Other Marks.
* gnus-prompt-before-saving:             Saving Articles.
* gnus-read-active-file:                 The Active File.
* gnus-read-mark:                        Read Articles.
* gnus-refer-article-method:             Finding the Parent.
* gnus-replied-mark:                     Other Marks.
* gnus-rmail-save-name:                  Saving Articles.
* gnus-save-all-headers:                 Saving Articles.
* gnus-save-killed-list:                 Startup Files.
* gnus-save-newsrc-file:                 Startup Files.
* gnus-save-newsrc-hook:                 Startup Files.
* gnus-save-quick-newsrc-hook:           Startup Files.
* gnus-save-score:                       Score Variables.
* gnus-save-standard-newsrc-hook:        Startup Files.
* gnus-saved-headers:                    Saving Articles.
* gnus-saved-mark:                       Other Marks.
* gnus-score-after-write-file-function:  Score Variables.
* gnus-score-below-mark:                 Score Variables.
* gnus-score-change-score-file:          Summary Score Commands.
* gnus-score-customize:                  Summary Score Commands.
* gnus-score-edit-current-scores:        Summary Score Commands.
* gnus-score-edit-done:                  Score File Editing.
* gnus-score-edit-file:                  Summary Score Commands.
* gnus-score-edit-insert-date:           Score File Editing.
* gnus-score-exact-adapt-limit:          Adaptive Scoring.
* gnus-score-expiry-days:                Score Variables.
* gnus-score-file-suffix:                Score Variables.
* gnus-score-find-bnews:                 Score Variables.
* gnus-score-find-hierarchical:          Score Variables.
* gnus-score-find-score-files-function:  Score Variables.
* gnus-score-find-single:                Score Variables.
* gnus-score-find-trace:                 Summary Score Commands.
* gnus-score-flush-cache <1>:            Group Score Commands.
* gnus-score-flush-cache:                Summary Score Commands.
* gnus-score-followup-article:           Followups To Yourself.
* gnus-score-followup-thread:            Followups To Yourself.
* gnus-score-interactive-default-score:  Score Variables.
* gnus-score-menu-hook:                  Highlighting and Menus.
* gnus-score-mimic-keymap:               Summary Score Commands.
* gnus-score-mode-hook:                  Score File Editing.
* gnus-score-over-mark:                  Score Variables.
* gnus-score-pretty-print:               Score File Editing.
* gnus-score-search-global-directories:  Global Score Files.
* gnus-score-set-expunge-below:          Summary Score Commands.
* gnus-score-set-mark-below:             Summary Score Commands.
* gnus-score-uncacheable-files:          Score Variables.
* gnus-secondary-select-methods:         Finding the News.
* gnus-secondary-servers:                Finding the News.
* gnus-select-article-hook:              Choosing Articles.
* gnus-select-group-hook:                Selecting a Group.
* gnus-select-method:                    Finding the News.
* gnus-selected-tree-face:               Tree Display.
* gnus-sent-message-ids-file:            Post.
* gnus-sent-message-ids-length:          Post.
* gnus-server-add-server:                Server Commands.
* gnus-server-close-server:              Unavailable Servers.
* gnus-server-copy-server:               Server Commands.
* gnus-server-deny-server:               Unavailable Servers.
* gnus-server-edit-server:               Server Commands.
* gnus-server-exit:                      Server Commands.
* gnus-server-kill-server:               Server Commands.
* gnus-server-line-format:               Server Buffer Format.
* gnus-server-list-servers:              Server Commands.
* gnus-server-menu-hook:                 Highlighting and Menus.
* gnus-server-mode-hook:                 The Server Buffer.
* gnus-server-mode-line-format:          Server Buffer Format.
* gnus-server-open-server:               Unavailable Servers.
* gnus-server-read-server:               Server Commands.
* gnus-server-remove-denials:            Unavailable Servers.
* gnus-server-yank-server:               Server Commands.
* gnus-show-all-headers:                 Hiding Headers.
* gnus-show-mime:                        Using MIME.
* gnus-show-mime-method:                 Using MIME.
* gnus-show-threads:                     Customizing Threading.
* gnus-signature-face:                   Article Highlighting.
* gnus-signature-limit:                  Article Hiding.
* gnus-signature-separator:              Article Highlighting.
* gnus-simplify-ignored-prefixes:        Customizing Threading.
* gnus-simplify-subject-fuzzy-regexp:    Customizing Threading.
* gnus-single-article-buffer:            Misc Article.
* gnus-sorted-header-list:               Hiding Headers.
* gnus-soup-add-article:                 SOUP Commands.
* gnus-soup-directory:                   SOUP Commands.
* gnus-soup-pack-packet:                 SOUP Commands.
* gnus-soup-packer:                      SOUP Commands.
* gnus-soup-packet-directory:            SOUP Commands.
* gnus-soup-packet-regexp:               SOUP Commands.
* gnus-soup-prefix-file:                 SOUP Commands.
* gnus-soup-replies-directory:           SOUP Commands.
* gnus-soup-save-areas:                  SOUP Commands.
* gnus-soup-send-replies:                SOUP Commands.
* gnus-soup-unpacker:                    SOUP Commands.
* gnus-souped-mark:                      Read Articles.
* gnus-sparse-mark:                      Read Articles.
* gnus-split-methods:                    Saving Articles.
* gnus-startup-file:                     Startup Files.
* gnus-startup-hook:                     Startup Variables.
* gnus-strict-mime:                      Using MIME.
* gnus-subscribe-alphabetically:         New Groups.
* gnus-subscribe-hierarchical-interactive: New Groups.
* gnus-subscribe-hierarchically:         New Groups.
* gnus-subscribe-interactively:          New Groups.
* gnus-subscribe-killed:                 New Groups.
* gnus-subscribe-newsgroup-method:       New Groups.
* gnus-subscribe-options-newsgroup-method: New Groups.
* gnus-subscribe-randomly:               New Groups.
* gnus-subscribe-zombies:                New Groups.
* gnus-summary-beginning-of-article:     Paging the Article.
* gnus-summary-best-unread-article:      Choosing Articles.
* gnus-summary-bubble-group:             Group Score.
* gnus-summary-caesar-message:           Article Washing.
* gnus-summary-cancel-article:           Canceling and Superseding.
* gnus-summary-catchup:                  Setting Marks.
* gnus-summary-catchup-all:              Setting Marks.
* gnus-summary-catchup-all-and-exit:     Exiting the Summary Buffer.
* gnus-summary-catchup-and-exit:         Exiting the Summary Buffer.
* gnus-summary-catchup-and-goto-next-group: Exiting the Summary Buffer.
* gnus-summary-catchup-to-here:          Setting Marks.
* gnus-summary-check-current:            Summary Maneuvering.
* gnus-summary-clear-above:              Setting Marks.
* gnus-summary-clear-mark-forward:       Setting Marks.
* gnus-summary-copy-article:             Mail Group Commands.
* gnus-summary-crosspost-article:        Mail Group Commands.
* gnus-summary-current-score:            Summary Score Commands.
* gnus-summary-default-score:            Score Variables.
* gnus-summary-delete-article:           Mail Group Commands.
* gnus-summary-describe-briefly:         Summary Group Information.
* gnus-summary-describe-group:           Summary Group Information.
* gnus-summary-down-thread:              Thread Commands.
* gnus-summary-dummy-line-format:        Customizing Threading.
* gnus-summary-edit-article:             Mail Group Commands.
* gnus-summary-edit-global-kill:         Kill Files.
* gnus-summary-edit-local-kill:          Kill Files.
* gnus-summary-end-of-article:           Paging the Article.
* gnus-summary-enter-digest-group:       Really Various Summary Commands.
* gnus-summary-execute-command:          Searching for Articles.
* gnus-summary-exit:                     Exiting the Summary Buffer.
* gnus-summary-exit-hook:                Exiting the Summary Buffer.
* gnus-summary-exit-no-update:           Exiting the Summary Buffer.
* gnus-summary-expand-window:            Really Various Summary Commands.
* gnus-summary-expire-articles:          Mail Group Commands.
* gnus-summary-expire-articles-now:      Mail Group Commands.
* gnus-summary-fetch-faq:                Summary Group Information.
* gnus-summary-first-unread-article:     Choosing Articles.
* gnus-summary-followup:                 Summary Post Commands.
* gnus-summary-followup-with-original:   Summary Post Commands.
* gnus-summary-gather-exclude-subject:   Customizing Threading.
* gnus-summary-gather-subject-limit:     Customizing Threading.
* gnus-summary-generate-hook:            Various Summary Stuff.
* gnus-summary-goto-article:             Summary Maneuvering.
* gnus-summary-goto-last-article:        Choosing Articles.
* gnus-summary-goto-subject:             Summary Maneuvering.
* gnus-summary-goto-unread <1>:          Setting Marks.
* gnus-summary-goto-unread:              Process/Prefix.
* gnus-summary-hide-all-threads:         Thread Commands.
* gnus-summary-hide-thread:              Thread Commands.
* gnus-summary-highlight:                Summary Highlighting.
* gnus-summary-import-article:           Mail Group Commands.
* gnus-summary-isearch-article:          Paging the Article.
* gnus-summary-kill-below:               Setting Marks.
* gnus-summary-kill-same-subject:        Setting Marks.
* gnus-summary-kill-same-subject-and-select: Setting Marks.
* gnus-summary-kill-thread:              Thread Commands.
* gnus-summary-limit-exclude-childless-dormant: Limiting.
* gnus-summary-limit-exclude-dormant:    Limiting.
* gnus-summary-limit-include-dormant:    Limiting.
* gnus-summary-limit-include-expunged:   Limiting.
* gnus-summary-limit-mark-excluded-as-read: Limiting.
* gnus-summary-limit-to-articles:        Limiting.
* gnus-summary-limit-to-author:          Limiting.
* gnus-summary-limit-to-marks:           Limiting.
* gnus-summary-limit-to-score:           Limiting.
* gnus-summary-limit-to-subject:         Limiting.
* gnus-summary-limit-to-unread:          Limiting.
* gnus-summary-line-format:              Summary Buffer Lines.
* gnus-summary-lower-score:              Summary Score Commands.
* gnus-summary-lower-thread:             Thread Commands.
* gnus-summary-mail-forward:             Summary Mail Commands.
* gnus-summary-mail-other-window:        Summary Mail Commands.
* gnus-summary-make-false-root:          Customizing Threading.
* gnus-summary-mark-above:               Setting Marks.
* gnus-summary-mark-as-dormant:          Setting Marks.
* gnus-summary-mark-as-expirable:        Setting Marks.
* gnus-summary-mark-as-processable <1>:  Setting Process Marks.
* gnus-summary-mark-as-processable:      Pick and Read.
* gnus-summary-mark-as-read-forward:     Setting Marks.
* gnus-summary-mark-below:               Scoring.
* gnus-summary-mark-read-and-unread-as-read: Choosing Articles.
* gnus-summary-mark-region-as-read:      Setting Marks.
* gnus-summary-mark-unread-as-read:      Choosing Articles.
* gnus-summary-menu-hook:                Highlighting and Menus.
* gnus-summary-mode-hook:                Various Summary Stuff.
* gnus-summary-mode-line-format:         Summary Buffer Mode Line.
* gnus-summary-move-article:             Mail Group Commands.
* gnus-summary-next-article:             Choosing Articles.
* gnus-summary-next-group:               Exiting the Summary Buffer.
* gnus-summary-next-page <1>:            Choosing Articles.
* gnus-summary-next-page:                Paging the Article.
* gnus-summary-next-same-subject:        Choosing Articles.
* gnus-summary-next-thread:              Thread Commands.
* gnus-summary-next-unread-article:      Choosing Articles.
* gnus-summary-next-unread-subject:      Summary Maneuvering.
* gnus-summary-pipe-output:              Saving Articles.
* gnus-summary-pop-article:              Choosing Articles.
* gnus-summary-pop-limit:                Limiting.
* gnus-summary-post-forward:             Summary Mail Commands.
* gnus-summary-post-news:                Summary Post Commands.
* gnus-summary-prepare-exit-hook:        Exiting the Summary Buffer.
* gnus-summary-prepare-hook:             Various Summary Stuff.
* gnus-summary-prev-article:             Choosing Articles.
* gnus-summary-prev-group:               Exiting the Summary Buffer.
* gnus-summary-prev-page:                Paging the Article.
* gnus-summary-prev-same-subject:        Choosing Articles.
* gnus-summary-prev-thread:              Thread Commands.
* gnus-summary-prev-unread-article:      Choosing Articles.
* gnus-summary-prev-unread-subject:      Summary Maneuvering.
* gnus-summary-raise-score:              Summary Score Commands.
* gnus-summary-raise-thread:             Thread Commands.
* gnus-summary-refer-article:            Finding the Parent.
* gnus-summary-refer-parent-article:     Finding the Parent.
* gnus-summary-refer-references:         Finding the Parent.
* gnus-summary-remove-bookmark:          Setting Marks.
* gnus-summary-reparent-thread:          Thread Commands.
* gnus-summary-reply:                    Summary Mail Commands.
* gnus-summary-reply-with-original:      Summary Mail Commands.
* gnus-summary-rescan-group:             Exiting the Summary Buffer.
* gnus-summary-rescore:                  Summary Score Commands.
* gnus-summary-reselect-current-group:   Exiting the Summary Buffer.
* gnus-summary-resend-bounced-mail:      Summary Mail Commands.
* gnus-summary-resend-message:           Summary Mail Commands.
* gnus-summary-respool-article:          Mail Group Commands.
* gnus-summary-respool-query:            Mail Group Commands.
* gnus-summary-rethread-current:         Thread Commands.
* gnus-summary-same-subject:             Summary Buffer Format.
* gnus-summary-save-article:             Saving Articles.
* gnus-summary-save-article-body-file:   Saving Articles.
* gnus-summary-save-article-file:        Saving Articles.
* gnus-summary-save-article-folder:      Saving Articles.
* gnus-summary-save-article-mail:        Saving Articles.
* gnus-summary-save-article-rmail:       Saving Articles.
* gnus-summary-save-article-vm:          Saving Articles.
* gnus-summary-save-body-in-file:        Saving Articles.
* gnus-summary-save-in-file:             Saving Articles.
* gnus-summary-save-in-folder:           Saving Articles.
* gnus-summary-save-in-mail:             Saving Articles.
* gnus-summary-save-in-rmail:            Saving Articles.
* gnus-summary-save-in-vm:               Saving Articles.
* gnus-summary-score-entry:              Summary Score Commands.
* gnus-summary-scroll-up:                Paging the Article.
* gnus-summary-search-article-backward:  Searching for Articles.
* gnus-summary-search-article-forward:   Searching for Articles.
* gnus-summary-selected-face:            Summary Highlighting.
* gnus-summary-set-bookmark:             Setting Marks.
* gnus-summary-set-score:                Summary Score Commands.
* gnus-summary-show-all-threads:         Thread Commands.
* gnus-summary-show-article:             Paging the Article.
* gnus-summary-show-thread:              Thread Commands.
* gnus-summary-sort-by-author:           Summary Sorting.
* gnus-summary-sort-by-date:             Summary Sorting.
* gnus-summary-sort-by-number:           Summary Sorting.
* gnus-summary-sort-by-score:            Summary Sorting.
* gnus-summary-sort-by-subject:          Summary Sorting.
* gnus-summary-stop-page-breaking:       Article Washing.
* gnus-summary-supersede-article:        Canceling and Superseding.
* gnus-summary-thread-gathering-function: Customizing Threading.
* gnus-summary-tick-above:               Setting Marks.
* gnus-summary-tick-article-forward:     Setting Marks.
* gnus-summary-toggle-header:            Article Washing.
* gnus-summary-toggle-mime:              Article Washing.
* gnus-summary-toggle-threads:           Thread Commands.
* gnus-summary-toggle-truncation:        Really Various Summary Commands.
* gnus-summary-top-thread:               Thread Commands.
* gnus-summary-universal-argument:       Searching for Articles.
* gnus-summary-unmark-all-processable <1>: Pick and Read.
* gnus-summary-unmark-all-processable:   Setting Process Marks.
* gnus-summary-unmark-as-processable <1>: Setting Process Marks.
* gnus-summary-unmark-as-processable:    Pick and Read.
* gnus-summary-up-thread:                Thread Commands.
* gnus-summary-update-hook:              Summary Highlighting.
* gnus-summary-verbose-header:           Article Washing.
* gnus-summary-wake-up-the-dead:         Exiting the Summary Buffer.
* gnus-summary-zcore-fuzz:               Summary Buffer Lines.
* gnus-supercite-regexp:                 Article Highlighting.
* gnus-supercite-secondary-regexp:       Article Highlighting.
* gnus-suspend-gnus-hook:                Exiting Gnus.
* gnus-thread-hide-killed:               Customizing Threading.
* gnus-thread-hide-subtree:              Customizing Threading.
* gnus-thread-ignore-subject:            Customizing Threading.
* gnus-thread-indent-level:              Customizing Threading.
* gnus-thread-operation-ignore-subject:  Thread Commands.
* gnus-thread-score-function:            Sorting.
* gnus-thread-sort-by-author:            Sorting.
* gnus-thread-sort-by-date:              Sorting.
* gnus-thread-sort-by-number:            Sorting.
* gnus-thread-sort-by-score:             Sorting.
* gnus-thread-sort-by-subject:           Sorting.
* gnus-thread-sort-by-total-score:       Sorting.
* gnus-thread-sort-functions:            Sorting.
* gnus-ticked-mark:                      Unread Articles.
* gnus-topic-copy-group:                 Topic Commands.
* gnus-topic-copy-matching:              Topic Commands.
* gnus-topic-create-topic:               Topic Commands.
* gnus-topic-delete:                     Topic Commands.
* gnus-topic-indent:                     Topic Commands.
* gnus-topic-indent-level:               Topic Variables.
* gnus-topic-kill-group:                 Topic Commands.
* gnus-topic-line-format:                Topic Variables.
* gnus-topic-list-active:                Topic Commands.
* gnus-topic-mark-topic:                 Topic Commands.
* gnus-topic-mode:                       Group Topics.
* gnus-topic-mode-hook:                  Topic Variables.
* gnus-topic-move-group:                 Topic Commands.
* gnus-topic-move-matching:              Topic Commands.
* gnus-topic-remove-group:               Topic Commands.
* gnus-topic-rename:                     Topic Commands.
* gnus-topic-select-group:               Topic Commands.
* gnus-topic-topology:                   Topic Topology.
* gnus-topic-unmark-topic:               Topic Commands.
* gnus-topic-yank-group:                 Topic Commands.
* gnus-total-expirable-newsgroups:       Expiring Mail.
* gnus-tree-brackets:                    Tree Display.
* gnus-tree-line-format:                 Tree Display.
* gnus-tree-minimize-window:             Tree Display.
* gnus-tree-mode-hook:                   Tree Display.
* gnus-tree-mode-line-format:            Tree Display.
* gnus-tree-parent-child-edges:          Tree Display.
* gnus-uncacheable-groups:               Article Caching.
* gnus-unload:                           Exiting Gnus.
* gnus-unread-mark <1>:                  Choosing Articles.
* gnus-unread-mark:                      Unread Articles.
* gnus-update-format:                    Formatting Variables.
* gnus-update-score-entry-dates:         Score Variables.
* gnus-updated-mode-lines:               Mode Lines.
* gnus-use-adaptive-scoring:             Adaptive Scoring.
* gnus-use-cache:                        Article Caching.
* gnus-use-cross-reference:              Exiting the Summary Buffer.
* gnus-use-demon:                        Daemons.
* gnus-use-dribble-file:                 Auto Save.
* gnus-use-full-window:                  Windows Configuration.
* gnus-use-grouplens:                    Using GroupLens.
* gnus-use-long-file-name <1>:           Article Caching.
* gnus-use-long-file-name:               Saving Articles.
* gnus-use-nocem:                        NoCeM.
* gnus-use-scoring:                      Score Variables.
* gnus-use-trees:                        Tree Display.
* gnus-uu-correct-stripped-uucode:       Other Decode Variables.
* gnus-uu-decode-postscript:             PostScript Files.
* gnus-uu-decode-postscript-and-save:    PostScript Files.
* gnus-uu-decode-postscript-and-save-view: PostScript Files.
* gnus-uu-decode-postscript-view:        PostScript Files.
* gnus-uu-decode-unshar:                 Shared Articles.
* gnus-uu-decode-unshar-and-save:        Shared Articles.
* gnus-uu-decode-unshar-and-save-view:   Shared Articles.
* gnus-uu-decode-unshar-view:            Shared Articles.
* gnus-uu-decode-uu:                     Uuencoded Articles.
* gnus-uu-decode-uu-and-save:            Uuencoded Articles.
* gnus-uu-decode-uu-and-save-view:       Uuencoded Articles.
* gnus-uu-decode-uu-view:                Uuencoded Articles.
* gnus-uu-digest-headers:                Mail.
* gnus-uu-digest-mail-forward:           Summary Mail Commands.
* gnus-uu-digest-post-forward:           Summary Mail Commands.
* gnus-uu-do-not-unpack-archives:        Other Decode Variables.
* gnus-uu-grab-move:                     Other Decode Variables.
* gnus-uu-grab-view:                     Other Decode Variables.
* gnus-uu-grabbed-file-functions:        Other Decode Variables.
* gnus-uu-ignore-default-archive-rules:  Other Decode Variables.
* gnus-uu-ignore-default-view-rules:     Other Decode Variables.
* gnus-uu-ignore-files-by-name:          Other Decode Variables.
* gnus-uu-ignore-files-by-type:          Other Decode Variables.
* gnus-uu-kill-carriage-return:          Other Decode Variables.
* gnus-uu-mark-all:                      Setting Process Marks.
* gnus-uu-mark-buffer <1>:               Pick and Read.
* gnus-uu-mark-buffer:                   Setting Process Marks.
* gnus-uu-mark-by-regexp <1>:            Setting Process Marks.
* gnus-uu-mark-by-regexp:                Pick and Read.
* gnus-uu-mark-over:                     Setting Process Marks.
* gnus-uu-mark-region <1>:               Pick and Read.
* gnus-uu-mark-region:                   Setting Process Marks.
* gnus-uu-mark-series:                   Setting Process Marks.
* gnus-uu-mark-sparse:                   Setting Process Marks.
* gnus-uu-mark-thread <1>:               Pick and Read.
* gnus-uu-mark-thread <2>:               Setting Process Marks.
* gnus-uu-mark-thread:                   Thread Commands.
* gnus-uu-notify-files:                  Uuencoded Articles.
* gnus-uu-post-include-before-composing: Uuencoding and Posting.
* gnus-uu-post-length:                   Uuencoding and Posting.
* gnus-uu-post-news:                     Summary Post Commands.
* gnus-uu-post-separate-description:     Uuencoding and Posting.
* gnus-uu-post-threaded:                 Uuencoding and Posting.
* gnus-uu-save-in-digest:                Other Decode Variables.
* gnus-uu-tmp-dir:                       Other Decode Variables.
* gnus-uu-unmark-articles-not-decoded:   Other Decode Variables.
* gnus-uu-unmark-buffer:                 Pick and Read.
* gnus-uu-unmark-by-regexp:              Pick and Read.
* gnus-uu-unmark-region:                 Pick and Read.
* gnus-uu-unmark-thread <1>:             Setting Process Marks.
* gnus-uu-unmark-thread <2>:             Thread Commands.
* gnus-uu-unmark-thread:                 Pick and Read.
* gnus-uu-user-archive-rules:            Rule Variables.
* gnus-uu-user-view-rules:               Rule Variables.
* gnus-uu-user-view-rules-end:           Rule Variables.
* gnus-uu-view-and-save:                 Other Decode Variables.
* gnus-uu-view-with-metamail:            Other Decode Variables.
* gnus-verbose:                          Various Various.
* gnus-verbose-backends:                 Various Various.
* gnus-version:                          Group Information.
* gnus-view-pseudo-asynchronously:       Viewing Files.
* gnus-view-pseudos:                     Viewing Files.
* gnus-view-pseudos-separately:          Viewing Files.
* gnus-visible-headers:                  Hiding Headers.
* gnus-visual:                           Highlighting and Menus.
* gnus-visual-mark-article-hook:         Summary Highlighting.
* gnus-window-min-height:                Windows Configuration.
* gnus-window-min-width:                 Windows Configuration.
* group buffer:                          The Group Buffer.
* group buffer format:                   Group Buffer Format.
* group description:                     Group Information.
* group information:                     Group Information.
* group level:                           Group Levels.
* group listing:                         Listing Groups.
* group movement:                        Group Maneuvering.
* group parameters:                      Group Parameters.
* group score:                           Group Score.
* group score commands:                  Group Score Commands.
* group selection:                       Selecting a Group.
* GroupLens:                             GroupLens.
* grouplens-best-unread-article:         Rating Articles.
* grouplens-newsgroups:                  Using GroupLens.
* grouplens-next-unread-article:         Rating Articles.
* grouplens-prediction-display:          Displaying Predictions.
* grouplens-pseudonym:                   Using GroupLens.
* grouplens-score-thread:                Rating Articles.
* head:                                  Terminology.
* header:                                Terminology.
* headers:                               Terminology.
* help group:                            Document Groups.
* hiding headers:                        Hiding Headers.
* highlight:                             Article Highlighting.
* highlighting <1>:                      Compatibility.
* highlighting:                          Highlighting and Menus.
* highlights:                            Various Various.
* hilit19:                               Compatibility.
* history:                               History.
* ignored groups:                        The Active File.
* illegal characters in file names:      Various Various.
* incoming mail files:                   Mail Backend Variables.
* info:                                  Group Information.
* information on groups:                 Group Information.
* interaction:                           Interactive.
* ispell:                                Mail and Post.
* ispell-message:                        Mail and Post.
* Jem:                                   NoCeM.
* kibozing:                              Kibozed Groups.
* kill files:                            Kill Files.
* killed groups:                         Terminology.
* levels:                                Terminology.
* limiting:                              Limiting.
* links:                                 Splitting Mail.
* LIST overview.fmt:                     Exiting the Summary Buffer.
* local variables:                       Score File Format.
* mail <1>:                              Summary Mail Commands.
* mail <2>:                              Terminology.
* mail:                                  Getting Mail.
* mail folders:                          Mail Folders.
* mail group commands:                   Mail Group Commands.
* mail message:                          Terminology.
* mail NOV spool:                        Mail Spool.
* mail splitting <1>:                    Splitting Mail.
* mail splitting:                        Fancy Mail Splitting.
* mail-extract-address-components:       Summary Buffer Format.
* MAILHOST:                              Mail Backend Variables.
* mailing lists:                         Mail and Post.
* manual:                                Group Information.
* marking groups:                        Marking Groups.
* marks:                                 Marking Articles.
* mbox:                                  Document Groups.
* mbox folders:                          Mail Folders.
* menus:                                 Highlighting and Menus.
* message:                               Terminology.
* metamail:                              Other Decode Variables.
* metamail-buffer:                       Using MIME.
* MH folders:                            Saving Articles.
* mh-e mail spool:                       MH Spool.
* MIME:                                  Using MIME.
* MIME digest:                           Document Groups.
* MMDF mail box:                         Document Groups.
* mode lines <1>:                        Mode Lines.
* mode lines:                            Various Various.
* MODE READER:                           NNTP.
* mouse:                                 Buttons.
* move mail:                             Mail Group Commands.
* movemail:                              Mail Backend Variables.
* moving articles:                       Mail Group Commands.
* Mule:                                  Emacsen.
* native:                                Terminology.
* new features:                          New Features.
* new groups:                            New Groups.
* new messages:                          Scanning New Messages.
* news:                                  Terminology.
* news backends:                         Getting News.
* news spool:                            News Spool.
* nnbabyl:                               Rmail Babyl.
* nnbabyl-active-file:                   Rmail Babyl.
* nnbabyl-get-new-mail <1>:              Rmail Babyl.
* nnbabyl-get-new-mail:                  Not Reading Mail.
* nnbabyl-mbox-file:                     Rmail Babyl.
* nnchoke:                               Backend Interface.
* nndir:                                 Directory Groups.
* nndoc:                                 Document Groups.
* nndoc-article-type:                    Document Groups.
* nndoc-post-type:                       Document Groups.
* nneething:                             Anything Groups.
* nneething-exclude-files:               Anything Groups.
* nneething-map-file:                    Anything Groups.
* nneething-map-file-directory:          Anything Groups.
* nnfolder:                              Mail Folders.
* nnfolder-active-file:                  Mail Folders.
* nnfolder-directory:                    Mail Folders.
* nnfolder-generate-active-file:         Mail Folders.
* nnfolder-get-new-mail <1>:             Mail Folders.
* nnfolder-get-new-mail:                 Not Reading Mail.
* nnfolder-newsgroups-file:              Mail Folders.
* nnheader-file-name-translation-alist:  Various Various.
* nnheader-max-head-length:              Various Various.
* nnkiboze:                              Kibozed Groups.
* nnkiboze-directory:                    Kibozed Groups.
* nnkiboze-generate-groups:              Kibozed Groups.
* nnmail-crash-box:                      Mail Backend Variables.
* nnmail-crosspost:                      Splitting Mail.
* nnmail-crosspost-link-function:        Splitting Mail.
* nnmail-delete-file-function:           Mail Backend Variables.
* nnmail-delete-incoming:                Mail Backend Variables.
* nnmail-expiry-wait:                    Expiring Mail.
* nnmail-expiry-wait-function <1>:       Group Parameters.
* nnmail-expiry-wait-function:           Expiring Mail.
* nnmail-keep-last-article <1>:          Mail and Procmail.
* nnmail-keep-last-article:              Expiring Mail.
* nnmail-message-id-cache-file:          Duplicates.
* nnmail-message-id-cache-length:        Duplicates.
* nnmail-movemail-program:               Mail Backend Variables.
* nnmail-pop-password:                   Mail Backend Variables.
* nnmail-pop-password-required:          Mail Backend Variables.
* nnmail-post-get-new-mail-hook:         Mail Backend Variables.
* nnmail-pre-get-new-mail-hook:          Mail Backend Variables.
* nnmail-prepare-incoming-hook:          Mail Backend Variables.
* nnmail-procmail-directory:             Mail and Procmail.
* nnmail-procmail-suffix <1>:            Mail Backend Variables.
* nnmail-procmail-suffix:                Mail and Procmail.
* nnmail-read-incoming-hook:             Mail Backend Variables.
* nnmail-resplit-incoming:               Mail and Procmail.
* nnmail-split-abbrev-alist:             Fancy Mail Splitting.
* nnmail-split-fancy:                    Fancy Mail Splitting.
* nnmail-split-fancy-syntax-table:       Fancy Mail Splitting.
* nnmail-split-methods:                  Splitting Mail.
* nnmail-spool-file:                     Mail Backend Variables.
* nnmail-tmp-directory:                  Mail Backend Variables.
* nnmail-treat-duplicates:               Duplicates.
* nnmail-use-long-file-names:            Mail Backend Variables.
* nnmail-use-procmail:                   Mail Backend Variables.
* nnmbox:                                Unix Mail Box.
* nnmbox-active-file:                    Unix Mail Box.
* nnmbox-get-new-mail <1>:               Not Reading Mail.
* nnmbox-get-new-mail:                   Unix Mail Box.
* nnmbox-mbox-file:                      Unix Mail Box.
* nnmh:                                  MH Spool.
* nnmh-be-safe:                          MH Spool.
* nnmh-directory:                        MH Spool.
* nnmh-get-new-mail <1>:                 MH Spool.
* nnmh-get-new-mail:                     Not Reading Mail.
* nnml:                                  Mail Spool.
* nnml-active-file:                      Mail Spool.
* nnml-directory:                        Mail Spool.
* nnml-generate-nov-databases:           Mail Spool.
* nnml-get-new-mail <1>:                 Mail Spool.
* nnml-get-new-mail:                     Not Reading Mail.
* nnml-newsgroups-file:                  Mail Spool.
* nnml-nov-file-name:                    Mail Spool.
* nnml-nov-is-evil:                      Mail Spool.
* nnml-prepare-save-mail-hook:           Mail Spool.
* nnsoup:                                SOUP Groups.
* nnsoup-active-file:                    SOUP Groups.
* nnsoup-directory:                      SOUP Groups.
* nnsoup-pack-replies:                   SOUP Commands.
* nnsoup-packer:                         SOUP Groups.
* nnsoup-packet-directory:               SOUP Groups.
* nnsoup-packet-regexp:                  SOUP Groups.
* nnsoup-replies-directory:              SOUP Groups.
* nnsoup-replies-format-type:            SOUP Groups.
* nnsoup-replies-index-type:             SOUP Groups.
* nnsoup-set-variables:                  SOUP Replies.
* nnsoup-tmp-directory:                  SOUP Groups.
* nnsoup-unpacker:                       SOUP Groups.
* nnspool:                               News Spool.
* nnspool-active-file:                   News Spool.
* nnspool-active-times-file:             News Spool.
* nnspool-history-file:                  News Spool.
* nnspool-inews-program:                 News Spool.
* nnspool-inews-switches:                News Spool.
* nnspool-lib-dir:                       News Spool.
* nnspool-newsgroups-file:               News Spool.
* nnspool-nov-directory:                 News Spool.
* nnspool-nov-is-evil:                   News Spool.
* nnspool-sift-nov-with-sed:             News Spool.
* nnspool-spool-directory:               News Spool.
* nntp:                                  NNTP.
* nntp authentification:                 NNTP.
* NNTP server:                           Finding the News.
* nntp-address:                          NNTP.
* nntp-async-number <1>:                 Asynchronous Fetching.
* nntp-async-number:                     NNTP.
* nntp-buggy-select:                     NNTP.
* nntp-command-timeout:                  NNTP.
* nntp-connection-timeout:               NNTP.
* nntp-end-of-line:                      NNTP.
* nntp-maximum-request:                  NNTP.
* nntp-nov-gap:                          NNTP.
* nntp-nov-is-evil:                      NNTP.
* nntp-open-network-stream:              NNTP.
* nntp-open-rlogin:                      NNTP.
* nntp-open-server-function:             NNTP.
* nntp-port-number:                      NNTP.
* nntp-prepare-server-hook:              NNTP.
* nntp-retry-on-break:                   NNTP.
* nntp-rlogin-parameters:                NNTP.
* nntp-rlogin-user-name:                 NNTP.
* nntp-send-authinfo:                    NNTP.
* nntp-send-mode-reader:                 NNTP.
* nntp-server-action-alist:              NNTP.
* nntp-server-hook:                      NNTP.
* nntp-server-opened-hook:               NNTP.
* nntp-warn-about-losing-connection:     NNTP.
* nntp-xover-commands:                   NNTP.
* NNTPSERVER:                            Finding the News.
* nnvirtual:                             Virtual Groups.
* nnvirtual-always-rescan:               Virtual Groups.
* nocem:                                 NoCeM.
* nov <1>:                               Terminology.
* nov:                                   NNTP.
* NOV:                                   Exiting the Summary Buffer.
* offline:                               SOUP.
* overview.fmt:                          Exiting the Summary Buffer.
* parent articles:                       Finding the Parent.
* persistent articles:                   Persistent Articles.
* pick and read:                         Pick and Read.
* POP mail:                              Mail Backend Variables.
* post <1>:                              Composing Messages.
* post:                                  Summary Post Commands.
* PostScript:                            PostScript Files.
* PPP connections:                       NNTP.
* process mark:                          Other Marks.
* process/prefix convention:             Process/Prefix.
* procmail:                              Mail and Procmail.
* pseudo-articles:                       Viewing Files.
* rcvstore:                              Saving Articles.
* reading init file:                     File Commands.
* reading mail:                          Getting Mail.
* reading news:                          Getting News.
* referring articles:                    Finding the Parent.
* reply <1>:                             Terminology.
* reply:                                 Composing Messages.
* reporting bugs <1>:                    Troubleshooting.
* reporting bugs:                        Compatibility.
* restarting:                            Scanning New Messages.
* reverse scoring:                       Reverse Scoring.
* RFC 1036:                              Conformity.
* RFC 1153 digest:                       Document Groups.
* RFC 341 digest:                        Document Groups.
* RFC 822:                               Conformity.
* rmail mbox <1>:                        Document Groups.
* rmail mbox:                            Rmail Babyl.
* rnews batch files:                     Document Groups.
* rule variables:                        Rule Variables.
* saving .newsrc:                        File Commands.
* saving articles:                       Saving Articles.
* scanning new news:                     Scanning New Messages.
* score cache:                           Score Variables.
* score commands:                        Summary Score Commands.
* score file format:                     Score File Format.
* score variables:                       Score Variables.
* scoring:                               Scoring.
* scoring crossposts:                    Scoring Tips.
* scoring tips:                          Scoring Tips.
* secondary:                             Terminology.
* sed:                                   News Spool.
* select method:                         Terminology.
* select methods:                        Select Methods.
* selecting articles:                    Choosing Articles.
* sent messages:                         Archived Messages.
* server:                                Terminology.
* server buffer format:                  Server Buffer Format.
* server commands:                       Server Commands.
* server errors:                         The Server is Down.
* setting marks:                         Setting Marks.
* setting process marks:                 Setting Process Marks.
* shared articles:                       Shared Articles.
* slave:                                 Slave Gnusii.
* slocal:                                Mail and Procmail.
* slow machine:                          Slow Machine.
* Son-of-RFC 1036:                       Conformity.
* sorting groups:                        Sorting Groups.
* SOUP:                                  SOUP.
* sox:                                   Rule Variables.
* spam:                                  NoCeM.
* spamming:                              Exiting the Summary Buffer.
* splitting mail:                        Splitting Mail.
* starting up:                           Starting Up.
* startup files:                         Startup Files.
* subscribing:                           Subscription Commands.
* summary buffer:                        The Summary Buffer.
* summary buffer format:                 Summary Buffer Format.
* summary exit:                          Exiting the Summary Buffer.
* summary movement:                      Summary Maneuvering.
* summary sorting:                       Summary Sorting.
* superseding articles:                  Canceling and Superseding.
* terminology:                           Terminology.
* thread commands:                       Thread Commands.
* threading:                             Threading.
* to-address:                            Group Parameters.
* to-group:                              Group Parameters.
* to-list:                               Group Parameters.
* todo:                                  Newest Features.
* topic commands:                        Topic Commands.
* topic topology:                        Topic Topology.
* topic variables:                       Topic Variables.
* topics:                                Group Topics.
* topology:                              Topic Topology.
* total-expire:                          Group Parameters.
* transient-mark-mode:                   Process/Prefix.
* trees:                                 Tree Display.
* troubleshooting:                       Troubleshooting.
* unix mail box:                         Unix Mail Box.
* Unix mbox:                             Document Groups.
* unloading:                             Exiting Gnus.
* unshar:                                Shared Articles.
* Usenet Seal of Approval:               Conformity.
* uudecode:                              Uuencoded Articles.
* uuencoded articles:                    Uuencoded Articles.
* V R (Summary):                         Summary Score Commands.
* velveeta:                              Exiting the Summary Buffer.
* version:                               Group Information.
* viewing files:                         Viewing Files.
* virtual groups:                        Virtual Groups.
* virtual server:                        Terminology.
* visible group parameter:               Listing Groups.
* visual:                                Highlighting and Menus.
* washing:                               Article Washing.
* window height:                         Windows Configuration.
* window width:                          Windows Configuration.
* windows configuration:                 Windows Configuration.
* x-face:                                Article Washing.
* XEmacs <1>:                            Emacsen.
* XEmacs:                                Emacs/XEmacs Code.
* XOVER:                                 NNTP.
* Xref:                                  Exiting the Summary Buffer.
* zombie groups:                         Terminology.


File: gnus,  Node: Key Index,  Prev: Index,  Up: Top

Key Index
*********

* Menu:

* ! (Summary):                           Setting Marks.
* # (Group):                             Marking Groups.
* # (Summary):                           Setting Process Marks.
* & (Summary):                           Searching for Articles.
* * (Summary):                           Persistent Articles.
* , (Group):                             Group Maneuvering.
* , (GroupLens):                         Rating Articles.
* , (Summary):                           Choosing Articles.
* .  (Summary):                          Choosing Articles.
* . (Group):                             Group Maneuvering.
* / / (Summary):                         Limiting.
* / a (Summary):                         Limiting.
* / C (Summary):                         Limiting.
* / c (Summary):                         Limiting.
* / d (Summary):                         Limiting.
* / D (Summary):                         Limiting.
* / E (Summary):                         Limiting.
* / m (Summary):                         Limiting.
* / n (Summary):                         Limiting.
* / u (Summary):                         Limiting.
* / v (Summary):                         Limiting.
* / w (Summary):                         Limiting.
* < (Summary):                           Paging the Article.
* = (Summary):                           Really Various Summary Commands.
* > (Summary):                           Paging the Article.
* ? (Article):                           Article Keymap.
* ? (Browse):                            Browse Foreign Server.
* ? (Group):                             Group Information.
* ? (Summary):                           Setting Marks.
* ^ (Group):                             Misc Group Stuff.
* ^ (Summary):                           Finding the Parent.
* a (Group):                             Misc Group Stuff.
* a (Server):                            Server Commands.
* a (Summary):                           Summary Post Commands.
* A < (Summary):                         Paging the Article.
* A > (Summary):                         Paging the Article.
* A a (Group):                           Listing Groups.
* A A (Group):                           Listing Groups.
* A d (Group):                           Listing Groups.
* A D (Summary):                         Really Various Summary Commands.
* A g (Summary):                         Paging the Article.
* A k (Group):                           Listing Groups.
* A l (Group):                           Listing Groups.
* A M (Group):                           Listing Groups.
* A m (Group):                           Listing Groups.
* A R (Summary):                         Finding the Parent.
* A s (Group):                           Listing Groups.
* A s (Summary):                         Paging the Article.
* A T (Group):                           Topic Commands.
* A u (Group):                           Listing Groups.
* A z (Group):                           Listing Groups.
* b (Group):                             Group Maintenance.
* B (Group) <1>:                         Finding the News.
* B (Group):                             Browse Foreign Server.
* B (Pick):                              Pick and Read.
* b (Pick):                              Pick and Read.
* B c (Summary):                         Mail Group Commands.
* B C (Summary):                         Mail Group Commands.
* B DEL (Summary):                       Mail Group Commands.
* B e (Summary):                         Mail Group Commands.
* B i (Summary):                         Mail Group Commands.
* B m (Summary):                         Mail Group Commands.
* B M-C-e (Summary):                     Mail Group Commands.
* B q (Summary):                         Mail Group Commands.
* B r (Summary):                         Mail Group Commands.
* B w (Summary):                         Mail Group Commands.
* c (Group):                             Selecting a Group.
* C (Group):                             Selecting a Group.
* c (Server):                            Server Commands.
* C (Server):                            Unavailable Servers.
* c (Summary):                           Exiting the Summary Buffer.
* C (Summary):                           Canceling and Superseding.
* C-c ^ (Article):                       Article Keymap.
* C-c C-c (Article):                     Mail Group Commands.
* C-c C-c (Post):                        Composing Messages.
* C-c C-c (Score):                       Score File Editing.
* C-c C-d (Score):                       Score File Editing.
* C-c C-i (Group):                       Group Information.
* C-c C-m (Article):                     Article Keymap.
* C-c C-p (Score):                       Score File Editing.
* C-c C-s (Group):                       Sorting Groups.
* C-c C-s C-a (Summary):                 Summary Sorting.
* C-c C-s C-d (Summary):                 Summary Sorting.
* C-c C-s C-i (Summary):                 Summary Sorting.
* C-c C-s C-n (Summary):                 Summary Sorting.
* C-c C-s C-s (Summary):                 Summary Sorting.
* C-c C-x (Group):                       Group Maintenance.
* C-c M-C-x (Group):                     Group Maintenance.
* C-c M-g (Group):                       Scanning New Messages.
* C-k (Group) <1>:                       Topic Commands.
* C-k (Group):                           Subscription Commands.
* C-k (Summary):                         Setting Marks.
* C-t (Summary):                         Really Various Summary Commands.
* C-w (Group):                           Subscription Commands.
* C-w (Summary):                         Setting Marks.
* C-x C-t (Group):                       Subscription Commands.
* C-y (Group) <1>:                       Subscription Commands.
* C-y (Group):                           Topic Commands.
* D (Group):                             Group Information.
* D (Server):                            Unavailable Servers.
* d (Summary):                           Setting Marks.
* DEL (Article):                         Article Keymap.
* DEL (Group):                           Group Maneuvering.
* DEL (Summary):                         Paging the Article.
* e (Pick):                              Pick and Read.
* E (Pick):                              Pick and Read.
* e (Server):                            Server Commands.
* e (Summary):                           Mail Group Commands.
* E (Summary):                           Setting Marks.
* F (Group):                             Group Maintenance.
* f (Summary):                           Summary Post Commands.
* F (Summary):                           Summary Post Commands.
* g (Binary):                            Binary Groups.
* g (Group):                             Scanning New Messages.
* g (Summary):                           Paging the Article.
* G a (Group):                           Foreign Groups.
* G b (Summary):                         Choosing Articles.
* G C-n (Summary):                       Choosing Articles.
* G C-p (Summary):                       Choosing Articles.
* G D (Group):                           Foreign Groups.
* G d (Group):                           Foreign Groups.
* G DEL (Group):                         Foreign Groups.
* G E (Group):                           Foreign Groups.
* G e (Group):                           Foreign Groups.
* G f  (Summary):                        Choosing Articles.
* G f (Group):                           Foreign Groups.
* G g (Summary):                         Summary Maneuvering.
* G h (Group):                           Foreign Groups.
* G j (Summary):                         Summary Maneuvering.
* G k (Group) <1>:                       Foreign Groups.
* G k (Group):                           Kibozed Groups.
* G l (Summary):                         Choosing Articles.
* G m (Group):                           Foreign Groups.
* G M-n (Summary):                       Summary Maneuvering.
* G M-p (Summary):                       Summary Maneuvering.
* G n (Summary):                         Choosing Articles.
* G N (Summary):                         Choosing Articles.
* G p (Group):                           Foreign Groups.
* G P (Summary):                         Choosing Articles.
* G p (Summary):                         Choosing Articles.
* G r (Group):                           Foreign Groups.
* G S a (Group):                         Sorting Groups.
* G s b (Group):                         SOUP Commands.
* G S l (Group):                         Sorting Groups.
* G S m (Group):                         Sorting Groups.
* G s p (Group):                         SOUP Commands.
* G s r (Group):                         SOUP Commands.
* G S r (Group):                         Sorting Groups.
* G s s (Group):                         SOUP Commands.
* G S u (Group):                         Sorting Groups.
* G S v (Group):                         Sorting Groups.
* G s w (Group):                         SOUP Commands.
* G V (Group):                           Foreign Groups.
* G v (Group):                           Foreign Groups.
* H d (Summary):                         Summary Group Information.
* H f (Summary):                         Summary Group Information.
* H h (Summary):                         Summary Group Information.
* H i (Summary):                         Summary Group Information.
* I C-i (Summary):                       Summary Score Commands.
* j (Group):                             Group Maneuvering.
* j (Summary):                           Summary Maneuvering.
* k (GroupLens):                         Rating Articles.
* k (Server):                            Server Commands.
* k (Summary):                           Setting Marks.
* l (Browse):                            Browse Foreign Server.
* l (Group):                             Listing Groups.
* L (Group):                             Listing Groups.
* l (Server):                            Server Commands.
* l (Summary):                           Choosing Articles.
* L C-l (Summary):                       Summary Score Commands.
* m (Group):                             Misc Group Stuff.
* m (Summary):                           Summary Mail Commands.
* M ? (Summary):                         Setting Marks.
* M b (Group):                           Marking Groups.
* M b (Summary):                         Setting Marks.
* M B (Summary):                         Setting Marks.
* M C (Summary):                         Setting Marks.
* M c (Summary):                         Setting Marks.
* M C-c (Summary):                       Setting Marks.
* M d (Summary):                         Setting Marks.
* M e (Summary):                         Setting Marks.
* M H (Summary):                         Setting Marks.
* M K (Summary):                         Setting Marks.
* M k (Summary):                         Setting Marks.
* M m (Group):                           Marking Groups.
* M P a (Summary):                       Setting Process Marks.
* M P b (Summary):                       Setting Process Marks.
* M P p (Summary):                       Setting Process Marks.
* M P r (Summary):                       Setting Process Marks.
* M P R (Summary):                       Setting Process Marks.
* M P S (Summary):                       Setting Process Marks.
* M P s (Summary):                       Setting Process Marks.
* M P t (Summary):                       Setting Process Marks.
* M P T (Summary):                       Setting Process Marks.
* M P u (Summary):                       Setting Process Marks.
* M P U (Summary):                       Setting Process Marks.
* M P v (Summary):                       Setting Process Marks.
* M r (Group):                           Marking Groups.
* M S (Summary):                         Limiting.
* M t (Summary):                         Setting Marks.
* M u (Group):                           Marking Groups.
* M U (Group):                           Marking Groups.
* M V c (Summary):                       Setting Marks.
* M V k (Summary):                       Setting Marks.
* M V m (Summary):                       Setting Marks.
* M V u (Summary):                       Setting Marks.
* M w (Group):                           Marking Groups.
* M-# (Group):                           Marking Groups.
* M-# (Summary):                         Setting Process Marks.
* M-& (Summary):                         Searching for Articles.
* M-* (Summary):                         Persistent Articles.
* M-^ (Summary):                         Finding the Parent.
* M-C-k (Summary):                       Thread Commands.
* M-C-l (Summary):                       Thread Commands.
* M-d (Group):                           Group Information.
* M-f (Group):                           Group Information.
* M-g (Group):                           Scanning New Messages.
* M-g (Summary):                         Exiting the Summary Buffer.
* M-k (Group):                           Kill Files.
* M-K (Group):                           Kill Files.
* M-k (Summary):                         Kill Files.
* M-K (Summary):                         Kill Files.
* M-n (Group):                           Group Maneuvering.
* M-n (Summary):                         Summary Maneuvering.
* M-p (Group):                           Group Maneuvering.
* M-p (Summary):                         Summary Maneuvering.
* M-r (Summary):                         Searching for Articles.
* M-RET (Group):                         Selecting a Group.
* M-s (Summary):                         Searching for Articles.
* M-TAB (Article):                       Article Keymap.
* M-u (Summary):                         Setting Marks.
* M-x gnus:                              Starting Up.
* M-x gnus-binary-mode:                  Binary Groups.
* M-x gnus-bug <1>:                      Compatibility.
* M-x gnus-bug:                          Troubleshooting.
* M-x gnus-other-frame:                  Starting Up.
* M-x gnus-pick-mode:                    Pick and Read.
* M-x gnus-update-format:                Formatting Variables.
* M-x nnfolder-generate-active-file:     Mail Folders.
* M-x nnkiboze-generate-groups:          Kibozed Groups.
* n (Browse):                            Browse Foreign Server.
* n (Group):                             Group Maneuvering.
* N (Group):                             Group Maneuvering.
* n (GroupLens):                         Rating Articles.
* N (Summary):                           Choosing Articles.
* n (Summary):                           Choosing Articles.
* O (Server):                            Unavailable Servers.
* o (Summary):                           Saving Articles.
* O b (Summary):                         Saving Articles.
* O f (Summary):                         Saving Articles.
* O h (Summary):                         Saving Articles.
* O m (Summary):                         Saving Articles.
* O o (Summary):                         Saving Articles.
* O p (Summary):                         Saving Articles.
* O r (Summary):                         Saving Articles.
* O s (Summary):                         SOUP Commands.
* O v (Summary):                         Saving Articles.
* p (Browse):                            Browse Foreign Server.
* P (Group):                             Group Maneuvering.
* p (Group):                             Group Maneuvering.
* P (Summary):                           Choosing Articles.
* p (Summary):                           Choosing Articles.
* q (Browse):                            Browse Foreign Server.
* Q (Group):                             Exiting Gnus.
* q (Group):                             Exiting Gnus.
* q (Server):                            Server Commands.
* q (Summary):                           Exiting the Summary Buffer.
* Q (Summary):                           Exiting the Summary Buffer.
* r (Group):                             File Commands.
* R (Group):                             Scanning New Messages.
* r (GroupLens):                         Rating Articles.
* r (Pick):                              Pick and Read.
* R (Pick):                              Pick and Read.
* R (Server):                            Unavailable Servers.
* R (Summary):                           Summary Mail Commands.
* r (Summary):                           Summary Mail Commands.
* RET (Browse):                          Browse Foreign Server.
* RET (Group) <1>:                       Selecting a Group.
* RET (Group):                           Topic Commands.
* RET (Pick):                            Pick and Read.
* RET (Summary):                         Paging the Article.
* s (Article):                           Article Keymap.
* s (Group):                             File Commands.
* S (Summary):                           Canceling and Superseding.
* S C-k (Group):                         Subscription Commands.
* S D b (Summary):                       Summary Mail Commands.
* S D r (Summary):                       Summary Mail Commands.
* S f (Summary):                         Summary Post Commands.
* S F (Summary):                         Summary Post Commands.
* S k (Group):                           Subscription Commands.
* S l (Group):                           Group Levels.
* S m (Summary):                         Summary Mail Commands.
* S o m (Summary):                       Summary Mail Commands.
* S O m (Summary):                       Summary Mail Commands.
* S o p (Summary):                       Summary Mail Commands.
* S O p (Summary):                       Summary Mail Commands.
* S p (Summary):                         Summary Post Commands.
* S R (Summary):                         Summary Mail Commands.
* S r (Summary):                         Summary Mail Commands.
* S s (Group):                           Subscription Commands.
* S t (Group):                           Subscription Commands.
* S u (Summary):                         Summary Post Commands.
* S w (Group):                           Subscription Commands.
* S y (Group):                           Subscription Commands.
* S z (Group):                           Subscription Commands.
* SPACE (Article):                       Article Keymap.
* SPACE (Browse):                        Browse Foreign Server.
* SPACE (Group):                         Selecting a Group.
* SPACE (Pick):                          Pick and Read.
* SPACE (Server):                        Server Commands.
* SPACE (Summary) <1>:                   Choosing Articles.
* SPACE (Summary):                       Paging the Article.
* T # (Group):                           Topic Commands.
* T # (Summary):                         Thread Commands.
* t (Group):                             Group Topics.
* t (Pick):                              Pick and Read.
* T (Pick):                              Pick and Read.
* T ^ (Summary):                         Thread Commands.
* T c (Group):                           Topic Commands.
* T C (Group):                           Topic Commands.
* T D (Group):                           Topic Commands.
* T d (Summary):                         Thread Commands.
* T DEL (Group):                         Topic Commands.
* T H (Summary):                         Thread Commands.
* T h (Summary):                         Thread Commands.
* T i (Summary):                         Thread Commands.
* T k (Summary):                         Thread Commands.
* T l (Summary):                         Thread Commands.
* T m (Group):                           Topic Commands.
* T M (Group):                           Topic Commands.
* T M-# (Group):                         Topic Commands.
* T M-# (Summary):                       Thread Commands.
* T n (Group):                           Topic Commands.
* T n (Summary):                         Thread Commands.
* T o (Summary):                         Thread Commands.
* T p (Summary):                         Thread Commands.
* T r (Group):                           Topic Commands.
* T S (Summary):                         Thread Commands.
* T s (Summary):                         Thread Commands.
* T t (Summary):                         Thread Commands.
* T T (Summary):                         Thread Commands.
* T TAB (Group):                         Topic Commands.
* T u (Summary):                         Thread Commands.
* TAB (Article):                         Article Keymap.
* u (Browse):                            Browse Foreign Server.
* u (Group):                             Subscription Commands.
* U (Group):                             Subscription Commands.
* u (Pick):                              Pick and Read.
* U (Pick):                              Pick and Read.
* V (Group):                             Group Information.
* V a (Summary):                         Summary Score Commands.
* V C (Summary):                         Summary Score Commands.
* V c (Summary):                         Summary Score Commands.
* V e (Summary):                         Summary Score Commands.
* V E (Summary):                         Summary Score Commands.
* V F (Summary):                         Summary Score Commands.
* V f (Summary):                         Summary Score Commands.
* V m (Summary):                         Summary Score Commands.
* V s (Summary):                         Summary Score Commands.
* V S (Summary):                         Summary Score Commands.
* V t (Summary):                         Summary Score Commands.
* W B (Summary):                         Article Washing.
* W b (Summary):                         Article Washing.
* W c (Summary):                         Article Washing.
* W f (Group):                           Group Score Commands.
* W f (Summary):                         Article Washing.
* W H a (Summary):                       Article Highlighting.
* W H c (Summary):                       Article Highlighting.
* W H h (Summary):                       Article Highlighting.
* W H s (Summary):                       Article Highlighting.
* W l (Summary):                         Article Washing.
* W L (Summary):                         Article Washing.
* W m (Summary):                         Article Washing.
* W o (Summary):                         Article Washing.
* W q (Summary):                         Article Washing.
* W r (Summary):                         Article Washing.
* W t (Summary):                         Article Washing.
* W T e (Summary):                       Article Date.
* W T l (Summary):                       Article Date.
* W T o (Summary):                       Article Date.
* W T u (Summary):                       Article Date.
* W v (Summary):                         Article Washing.
* W w (Summary):                         Article Washing.
* W W a (Summary):                       Article Hiding.
* W W b (Summary):                       Article Hiding.
* W W C (Summary):                       Article Hiding.
* W W c (Summary):                       Article Hiding.
* W W h (Summary):                       Article Hiding.
* W W p (Summary):                       Article Hiding.
* W W s (Summary):                       Article Hiding.
* x (Summary):                           Limiting.
* X p (Summary):                         PostScript Files.
* X P (Summary):                         PostScript Files.
* X s (Summary):                         Shared Articles.
* X S (Summary):                         Shared Articles.
* X u (Summary):                         Uuencoded Articles.
* X U (Summary):                         Uuencoded Articles.
* X v p (Summary):                       PostScript Files.
* X v P (Summary):                       PostScript Files.
* X v S (Summary):                       Shared Articles.
* X v s (Summary):                       Shared Articles.
* X v u (Summary):                       Uuencoded Articles.
* X v U (Summary):                       Uuencoded Articles.
* y (Server):                            Server Commands.
* z (Group):                             Exiting Gnus.
* Z C (Summary):                         Exiting the Summary Buffer.
* Z c (Summary):                         Exiting the Summary Buffer.
* Z E (Summary):                         Exiting the Summary Buffer.
* Z G (Summary):                         Exiting the Summary Buffer.
* Z n (Summary):                         Exiting the Summary Buffer.
* Z N (Summary):                         Exiting the Summary Buffer.
* Z P (Summary):                         Exiting the Summary Buffer.
* Z R (Summary):                         Exiting the Summary Buffer.
* Z Z (Summary):                         Exiting the Summary Buffer.


