\input texinfo @c -*-texinfo-*-
@setfilename gnus
-@settitle Red Gnus 0.41 Manual
+@settitle Red Gnus 0.51 Manual
@synindex fn cp
@synindex vr cp
@synindex pg cp
\marginpar[\hspace{2.5cm}\gnushead]{\gnushead}
}
-\newcommand{\gnuscleardoublepage}{\ifodd\count0\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
+\newcommand{\gnuscleardoublepage}{\ifodd\count0\mbox{}\clearpage\thispagestyle{empty}\mbox{}\clearpage\else\clearpage\fi}
\newcommand{\gnuspagechapter}[1]{
{\mbox{}}
@tex
@titlepage
-@title Red Gnus 0.41 Manual
+@title Red Gnus 0.51 Manual
@author by Lars Magne Ingebrigtsen
@page
@code{gnus-no-server} command to start Gnus. That might come in handy
if you're in a hurry as well. This command will not attempt to contact
your primary server---instead, it will just activate all groups on level
-@code{1} and @code{2}. (You should preferably keep no native groups on
-those two levels.)
+1 and 2. (You should preferably keep no native groups on those two
+levels.)
@node Slave Gnusae
To work around that problem some, we here at the Think-Tank at the Gnus
Towers have come up with a new concept: @dfn{Masters} and
-@dfn{servants}. (We have applied for a patent on this concept, and have
+@dfn{slaves}. (We have applied for a patent on this concept, and have
taken out a copyright on those words. If you wish to use those words in
conjunction with each other, you have to send $1 per usage instance to
me. Usage of the patent (@dfn{Master/Slave Relationships In Computer
@item gnus-subscribe-zombies
@vindex gnus-subscribe-zombies
-Make all new groups zombies. You can browse the zombies later (with
-@kbd{A z}) and either kill them all off properly, or subscribe to them.
-This is the default.
+Make all new groups zombies. This is the default. You can browse the
+zombies later (with @kbd{A z}) and either kill them all off properly
+(with @kbd{S z}), or subscribe to them (with @kbd{u}).
@item gnus-subscribe-randomly
@vindex gnus-subscribe-randomly
Note that if you subscribe to lots and lots of groups, setting this
variable to @code{nil} will probably make Gnus slower, not faster. At
present, having this variable @code{nil} will slow Gnus down
-considerably, unless you read news over a @code{2400} baud modem.
+considerably, unless you read news over a 2400 baud modem.
This variable can also have the value @code{some}. Gnus will then
attempt to read active info only on the subscribed groups. On some
Quite simple, huh?
-You can see that there are @code{25} unread articles in
+You can see that there are 25 unread articles in
@samp{news.announce.newusers}. There are no unread articles, but some
ticked articles, in @samp{alt.fan.andrea-dworkin} (see that little
asterisk at the beginning of the line?)
@item t
Estimated total number of articles. (This is really @var{max-number}
-minus @var{min-number} plus @code{1}.)
+minus @var{min-number} plus 1.)
@item y
Number of unread, unticked, non-dormant articles.
@vindex gnus-group-uncollapsed-levels
Short (collapsed) group name. The @code{gnus-group-uncollapsed-levels}
variable says how many levels to leave at the end of the group name.
-The default is @code{1}---this will mean that group names like
+The default is 1---this will mean that group names like
@samp{gnu.emacs.gnus} will be shortened to @samp{g.emacs.gnus}.
+@item m
+@vindex gnus-new-mail-mark
+@cindex %
+@samp{%} (@code{gnus-new-mail-mark}) if there has arrived new mail to
+the group lately.
+
+@item d
+A string that says when you last read the group (@pxref{Group
+Timestamp}).
+
@item u
User defined specifier. The next character in the format string should
be a letter. @sc{gnus} will call the function
minimum amount of fuzz (@code{gnus-group-quick-select-group}). No
scoring/killing will be performed, there will be no highlights and no
expunging. This might be useful if you're in a real hurry and have to
-enter some humongous group. If you give a @code{0} prefix to this command
+enter some humongous group. If you give a 0 prefix to this command
(i.e., @kbd{0 M-RET}), Gnus won't even generate the summary buffer.
This might be useful if you want to toggle threading before entering the
group.
@vindex gnus-large-newsgroup
The @code{gnus-large-newsgroup} variable says what Gnus should consider
-to be a big group. This is @code{200} by default. If the group has
-more (unread and/or ticked) articles than this, Gnus will query the user
+to be a big group. This is 200 by default. If the group has more
+(unread and/or ticked) articles than this, Gnus will query the user
before entering the group. The user can then specify how many articles
should be fetched from the server. If the user specifies a negative
number (@code{-n}), the @code{n} oldest articles will be fetched. If it
These groups can't be yanked back after killing, so this command should
be used with some caution. The only time where this command comes in
really handy is when you have a @file{.newsrc} with lots of unsubscribed
-groups that you want to get rid off. @kbd{S C-k} on level @code{7} will
+groups that you want to get rid off. @kbd{S C-k} on level 7 will
kill off all unsubscribed groups that do not have message numbers in the
@file{.newsrc} file.
@cindex level
All groups have a level of @dfn{subscribedness}. For instance, if a
-group is on level @code{2}, it is more subscribed than a group on level @code{5}. You
+group is on level 2, it is more subscribed than a group on level 5. You
can ask Gnus to just list groups on a given level or lower
(@pxref{Listing Groups}), or to just check for new articles in groups on
a given level or lower (@pxref{Scanning New Messages}).
@vindex gnus-level-zombie
@vindex gnus-level-unsubscribed
@vindex gnus-level-subscribed
-Gnus considers groups on between levels @code{1} and
-@code{gnus-level-subscribed} (inclusive) (default @code{5}) to be subscribed,
+Gnus considers groups on between levels 1 and
+@code{gnus-level-subscribed} (inclusive) (default 5) to be subscribed,
@code{gnus-level-subscribed} (exclusive) and
-@code{gnus-level-unsubscribed} (inclusive) (default @code{7}) to be
+@code{gnus-level-unsubscribed} (inclusive) (default 7) to be
unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
-(default @code{8}) and @code{gnus-level-killed} to be killed (default @code{9}),
+(default 8) and @code{gnus-level-killed} to be killed (default 9),
completely dead. Gnus treats subscribed and unsubscribed groups exactly
the same, but zombie and killed groups have no information on what
articles you have read, etc, stored. This distinction between dead and
for reasons of efficiency.
It is recommended that you keep all your mail groups (if any) on quite
-low levels (e.g. @code{1} or @code{2}).
+low levels (e.g. 1 or 2).
If you want to play with the level variables, you should show some care.
Set them once, and don't touch them ever again. Better yet, don't touch
@vindex gnus-level-default-unsubscribed
@vindex gnus-level-default-subscribed
Two closely related variables are @code{gnus-level-default-subscribed}
-(default @code{3}) and @code{gnus-level-default-unsubscribed} (default @code{6}),
+(default 3) and @code{gnus-level-default-unsubscribed} (default 6),
which are the levels that new groups will be put on if they are
(un)subscribed. These two variables should, of course, be inside the
relevant legal ranges.
Gnus will normally just activate groups that are on level
@code{gnus-activate-level} or less. If you don't want to activate
unsubscribed groups, for instance, you might set this variable to
-@code{5}. The default is @code{6}.
+5. The default is 6.
@node Group Score
group. You can then sort the group buffer based on this score.
Alternatively, you can sort on score and then level. (Taken together,
the level and the score is called the @dfn{rank} of the group. A group
-that is on level @code{4} and has a score of @code{1} has a higher rank than a group
-on level @code{5} that has a score of @code{300}. (The level is the most significant
+that is on level 4 and has a score of 1 has a higher rank than a group
+on level 5 that has a score of 300. (The level is the most significant
part and the score is the least significant part.))
@findex gnus-summary-bubble-group
groups---mail groups mostly. This command might very well be quite slow
on some backends.
+@item G c
+@kindex G c (Group)
+@cindex customizing
+@findex gnus-group-customize
+Customize the group parameters (@code{gnus-group-customize}).
+
@item G e
@kindex G e (Group)
@findex gnus-group-edit-group-method
List absolutely all groups that are in the active file(s) of the
server(s) you are connected to (@code{gnus-group-list-active}). This
might very well take quite a while. It might actually be a better idea
-to do a @kbd{A m} to list all matching, and just give @samp{.} as the
+to do a @kbd{A M} to list all matching, and just give @samp{.} as the
thing to match on. Also note that this command may list group that
don't exist (yet)---these will be listed as if they are killed groups.
Take the output with some grains of salt.
Note:
@quotation
-Miss Lisa Cannifax, while sitting in English class, feels her feet go
+Miss Lisa Cannifax, while sitting in English class, felt her feet go
numbly heavy and herself fall into a hazy trance as the boy sitting
behind her drew repeated lines with his pencil across the back of her
plastic chair.
@vindex gnus-topic-indent-level
Each sub-topic (and the groups in the sub-topics) will be indented with
@code{gnus-topic-indent-level} times the topic level number of spaces.
-The default is @code{2}.
+The default is 2.
@vindex gnus-topic-mode-hook
@code{gnus-topic-mode-hook} is called in topic minor mode buffers.
@item C-k
@kindex C-k (Topic)
@findex gnus-topic-kill-group
-Kill a group or topic (@code{gnus-topic-kill-group}).
+Kill a group or topic (@code{gnus-topic-kill-group}). All groups in the
+topic will be removed along with the topic.
@item C-y
@kindex C-y (Topic)
@findex gnus-topic-yank-group
-Yank the previously killed group or topic (@code{gnus-topic-yank-group}).
-Note that all topics will be yanked before all groups.
+Yank the previously killed group or topic
+(@code{gnus-topic-yank-group}). Note that all topics will be yanked
+before all groups.
@item T r
@kindex T r (Topic)
13: comp.sources.unix
@end example
-So, here we have one top-level topic, two topics under that, and one
-sub-topic under one of the sub-topics. (There is always just one (@code{1})
-top-level topic). This topology can be expressed as follows:
+So, here we have one top-level topic (@samp{Gnus}), two topics under
+that, and one sub-topic under one of the sub-topics. (There is always
+just one (1) top-level topic). This topology can be expressed as
+follows:
@lisp
(("Gnus" visible)
@menu
* Scanning New Messages:: Asking Gnus to see whether new messages have arrived.
* Group Information:: Information and help on groups and Gnus.
+* Group Timestamp:: Making Gnus keep track of when you last read a group.
* File Commands:: Reading and writing the Gnus files.
@end menu
@end table
+@node Group Timestamp
+@subsection Group Timestamp
+@cindex timestamps
+@cindex group timestamps
+
+It can be convenient to let Gnus keep track of when you last read a
+group. To set the ball rolling, you should add
+@code{gnus-group-set-timestamp} to @code{gnus-select-group-hook}:
+
+@lisp
+(add-hook 'gnus-select-group-hook 'gnus-group-set-timestamp)
+@end lisp
+
+After doing this, each time you enter a group, it'll be recorded.
+
+This information can be displayed in various ways---the easiest is to
+use the @samp{%d} spec in the group line format:
+
+@lisp
+(setq gnus-group-line-format
+ "%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
+@end lisp
+
+This will result in lines looking like:
+
+@example
+* 0: mail.ding 19961002T012943
+ 0: custom 19961002T012713
+@end example
+
+As you can see, the date is displayed in compact ISO 8601 format. This
+may be a bit too much, so to just display the date, you could say
+something like:
+
+@lisp
+(setq gnus-group-line-format
+ "%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
+@end lisp
+
+
@node File Commands
@subsection File Commands
@cindex file commands
A line for each article is displayed in the summary buffer. You can
move around, read articles, post articles and reply to articles.
+The most common way to a summary buffer is to select a group from the
+group buffer (@pxref{Selecting a Group}).
+
+You can have as many summary buffers open as you wish.
+
@menu
* Summary Buffer Format:: Deciding how the summary buffer is to look.
* Summary Maneuvering:: Moving around the summary buffer.
The name (from the @code{From} header).
@item a
The name (from the @code{From} header). This differs from the @code{n}
-spec in that it uses @code{gnus-extract-address-components}, which is
-slower, but may be more thorough.
+spec in that it uses the function designated by the
+@code{gnus-extract-address-components} variable, which is slower, but
+may be more thorough.
@item A
The address (from the @code{From} header). This works the same way as
the @code{a} spec.
ship a mail to a different account of yours. (If you're both
@code{root} and @code{postmaster} and get a mail for @code{postmaster}
to the @code{root} account, you may want to resend it to
-@code{postmaster}. Ordnung muss sein!
+@code{postmaster}. Ordnung muß sein!
@item S O m
@kindex S O m (Summary)
@cindex post
@cindex composing news
-Commands for posting an article:
+Commands for posting a news article:
@table @kbd
@item S p
long thesis on cats' urinary tracts, and have to go home for dinner
before you've finished reading the thesis. You can then set a bookmark
in the article, and Gnus will jump to this bookmark the next time it
-encounters the article.
+encounters the article. @xref{Setting Marks}
@item
@vindex gnus-replied-mark
subjects of the loose threads before gathering them into one big
super-thread. This might be too strict a requirement, what with the
presence of stupid newsreaders that chop off long subjects lines. If
-you think so, set this variable to, say, @code{20} to require that only the
-first @code{20} characters of the subjects have to match. If you set this
+you think so, set this variable to, say, 20 to require that only the
+first 20 characters of the subjects have to match. If you set this
variable to a really low number, you'll find that Gnus will gather
everything in sight into one thread, which isn't very helpful.
@item gnus-simplify-ignored-prefixes
@vindex gnus-simplify-ignored-prefixes
If you set @code{gnus-summary-gather-subject-limit} to something as low
-as @code{10}, you might consider setting this variable to something sensible:
+as 10, you might consider setting this variable to something sensible:
@c Written by Michael Ernst <mernst@cs.rice.edu>
@lisp
@item gnus-thread-indent-level
@vindex gnus-thread-indent-level
This is a number that says how much each sub-thread should be indented.
-The default is @code{4}.
+The default is 4.
@end table
First, some caveats. There are some pitfalls to using asynchronous
article fetching, especially the way Gnus does it.
-Let's say you are reading article @code{1}, which is short, and article @code{2} is
+Let's say you are reading article 1, which is short, and article 2 is
quite long, and you are not interested in reading that. Gnus does not
-know this, so it goes ahead and fetches article @code{2}. You decide to read
-article @code{3}, but since Gnus is in the process of fetching article @code{2}, the
+know this, so it goes ahead and fetches article 2. You decide to read
+article 3, but since Gnus is in the process of fetching article 2, the
connection is blocked.
To avoid these situations, Gnus will open two (count 'em two)
@vindex gnus-use-article-prefetch
You can control how many articles that are to be pre-fetched by setting
-@code{gnus-use-article-prefetch}. This is @code{30} by default, which means
+@code{gnus-use-article-prefetch}. This is 30 by default, which means
that when you read an article in the group, the backend will pre-fetch
-the next @code{30} articles. If this variable is @code{t}, the backend will
+the next 30 articles. If this variable is @code{t}, the backend will
pre-fetch all the articles that it can without bound. If it is
@code{nil}, no pre-fetching will be made.
data structure as the only parameter.
If, for instance, you wish to pre-fetch only unread articles that are
-shorter than @code{100} lines, you could say something like:
+shorter than 100 lines, you could say something like:
@lisp
(defun my-async-short-unread-p (data)
So where does the massive article-fetching and storing come into the
picture? The @code{gnus-jog-cache} command will go through all
subscribed newsgroups, request all unread articles, and store them in
-the cache. You should only ever, ever ever ever, use this command if @code{1})
+the cache. You should only ever, ever ever ever, use this command if 1)
your connection to the @sc{nntp} server is really, really, really slow
-and @code{2}) you have a really, really, really huge disk. Seriously.
+and 2) you have a really, really, really huge disk. Seriously.
@vindex gnus-uncacheable-groups
It is likely that you do not want caching on some groups. For instance,
@item button-par
Gnus has to know which parts of the match is to be highlighted. This is
a number that says what sub-expression of the regexp that is to be
-highlighted. If you want it all highlighted, you use @code{0} here.
+highlighted. If you want it all highlighted, you use 0 here.
@item use-p
This form will be @code{eval}ed, and if the result is non-@code{nil},
@item B M-C-e
@kindex B M-C-e (Summary)
@findex gnus-summary-expire-articles-now
-Expunge all the expirable articles in the group
+Delete all the expirable articles in the group
(@code{gnus-summary-expire-articles-now}). This means that @strong{all}
articles that are eligible for expiry in the current group will
disappear forever into that big @file{/dev/null} in the sky.
millions, of functions you can put in this hook. For an overview of
functions @pxref{Article Highlighting}, @pxref{Article Hiding},
@pxref{Article Washing}, @pxref{Article Buttons} and @pxref{Article
-Date}.
+Date}. Note that the order of functions in this hook might affect
+things, so you may have to fiddle a bit to get the desired results.
You can, of course, write your own functions. The functions are called
from the article buffer, and you can do anything you like, pretty much.
These select methods specifications can sometimes become quite
complicated---say, for instance, that you want to read from the
-@sc{nntp} server @samp{news.funet.fi} on port number @code{13}, which
+@sc{nntp} server @samp{news.funet.fi} on port number 13, which
hangs if queried for @sc{nov} headers and has a buggy select. Ahem.
Anyways, if you had to specify that for each group that used this
server, that would be too much work, so Gnus offers a way of naming
@var{(variable form)} pairs.
To go back to the first example---imagine that you want to read from
-port @code{15} from that machine. This is what the select method should
+port 15 from that machine. This is what the select method should
look like then:
@lisp
@code{t} and be prompted for the password, or set
@code{nnmail-pop-password} to the password itself.
+Your Emacs has to have been configured with @samp{--with-pop} before
+compilation. This is the default, but some installations have it
+switched off.
+
When you use a mail backend, Gnus will slurp all your mail from your
inbox and plonk it down in your home directory. Gnus doesn't move any
mail if you're not using a mail backend---you have to do a lot of magic
articles that are marked as expirable have an @samp{E} in the first
column in the summary buffer.
+Note that making a group auto-expirable don't mean that all read
+articles are expired---only the articles that are marked as expirable
+will be expired. Also note the using the @kbd{d} command won't make
+groups expirable---only semi-automatic marking of articles as read will
+mark the articles as expirable in auto-expirable groups.
+
Let's say you subscribe to a couple of mailing lists, and you want the
articles you have read to disappear after a while:
Another way to have auto-expiry happen is to have the element
@code{auto-expire} in the group parameters of the group.
+If you use adaptive scoring (@pxref{Adaptive Scoring}) and
+auto-expiring, you'll have problems. Auto-expiring and adaptive scoring
+doesn't really mix very well.
+
@vindex nnmail-expiry-wait
The @code{nnmail-expiry-wait} variable supplies the default time an
expirable article has to live. The default is seven days.
@emph{man}! Or a @emph{woman}! Whatever you feel more comfortable
with! So there!
+Most people make most of their mail groups total-expirable, though.
+
@node Washing Mail
@subsection Washing Mail
and mail from servers to home machines and back again. It can be a bit
fiddly.
+First some terminology:
+
+@table @dfn
+
+@item server
+This is the machine that is connected to the outside world and where you
+get news and/or mail from.
+
+@item home machine
+This is the machine that you want to do the actual reading and responding
+on. It is typically not connected to the rest of the world in any way.
+
+@item packet
+Something that contains messages and/or commands. There are two kinds
+of packets:
+
+@table @dfn
+@item message packets
+These are packets made at the server, and typically contains lots of
+messages for you to read. These are called @file{SoupoutX.tgz} by
+default, where @var{X} is a number.
+
+@item response packets
+These are packets made at the home machine, and typically contains
+replies that you've written. These are called @file{SoupinX.tgz} by
+default, where @var{X} is a number.
+
+@end table
+
+@end table
+
+
@enumerate
@item
You log in on the server and create a @sc{soup} packet. You can either
-use a dedicated @sc{soup} thingie, or you can use Gnus to create the
-packet with the @kbd{O s} command.
+use a dedicated @sc{soup} thingie (like the @code{awk} program), or you
+can use Gnus to create the packet with its @sc{soup} commands (@kbd{O
+s} and/or @kbd{G s b}; and then @kbd{G s p}) (@pxref{SOUP Commands}).
@item
You transfer the packet home. Rail, boat, car or modem will do fine.
You put the packet in your home directory.
@item
-You fire up Gnus using the @code{nnsoup} backend as the native server.
+You fire up Gnus on your home machine using the @code{nnsoup} backend as
+the native or secondary server.
@item
You read articles and mail and answer and followup to the things you
-want.
+want (@pxref{SOUP Replies}).
@item
You do the @kbd{G s r} command to pack these replies into a @sc{soup}
@node SOUP Commands
@subsubsection SOUP Commands
+These are commands for creating and manipulating @sc{soup} packets.
+
@table @kbd
@item G s b
@kindex G s b (Group)
@item G s w
@kindex G s w (Group)
@findex gnus-soup-save-areas
-Save all data files (@code{gnus-soup-save-areas}).
+Save all @sc{soup} data files (@code{gnus-soup-save-areas}).
@item G s s
@kindex G s s (Group)
@findex gnus-soup-add-article
This summary-mode command adds the current article to a @sc{soup} packet
(@code{gnus-soup-add-article}). It understands the process/prefix
-convention.
+convention (@pxref{Process/Prefix}).
@end table
header uses.
@item Followup
-This match key will add a score entry on all articles that followup to
-some author. Uses the same match types as the @code{From} header uses.
+This match key is somewhat special, in that it will match the
+@code{From} header, and affect the score of not only the matching
+articles, but also all followups to the matching articles. This allows
+you e.g. increase the score of followups to your own articles, or
+decrease the score of followups to the articles of some known
+trouble-maker. Uses the same match types as the @code{From} header
+uses.
@item Thread
-This match key will add a score entry on all articles that are part of
-a thread. Uses the same match types as the @code{References} header
-uses.
+This match key works along the same lines as the @code{Followup} match
+key. If you say that you want to score on a (sub-)thread that is
+started by an article with a @code{Message-ID} @var{X}, then you add a
+@samp{thread} match. This will add a new @samp{thread} match for each
+article that has @var{X} in its @code{References} header. (These new
+@samp{thread} matches will use the @code{Message-ID}s of these matching
+articles.) This will ensure that you can raise/lower the score of an
+entire thread, even though some articles in the thread may not have
+complete @code{References} headers. Note that using this may lead to
+undeterministic scores of the articles in the thread.
@end table
@end enumerate
this one was.
@item exclude-files
-The clue of this entry should be any number of files. This files will
+The clue of this entry should be any number of files. These files will
not be loaded, even though they would normally be so, for some reason or
other.
That means that that subject will get a score of ten times -1, which
should be, unless I'm much mistaken, -10.
+If you have auto-expirable (mail) groups (@pxref{Expiring Mail}), all
+the read articles will be marked with the @samp{E} mark. This'll
+probably make adaptive scoring slightly impossible, so auto-expiring and
+adaptive scoring doesn't really mix very well.
+
The headers you can score on are @code{from}, @code{subject},
@code{message-id}, @code{references}, @code{xref}, @code{lines},
@code{chars} and @code{date}. In addition, you can score on
@vindex gnus-demon-timestep
(When I say ``minute'' here, I really mean @code{gnus-demon-timestep}
-seconds. This is @code{60} by default. If you change that variable,
+seconds. This is 60 by default. If you change that variable,
all the timings in the handlers will be affected.)
@vindex gnus-use-demon
@item jem@@xpat.com;
@cindex Jem
-Jem---Korean despammer who is getting very busy these days.
+John Milburn---despammer located in Korea who is getting very busy these
+days.
@item red@@redpoll.mrfs.oh.us (Richard E. Depew)
Richard E. Depew---lone American despammer. He mostly cancels binary
@item nnheader-max-head-length
@vindex nnheader-max-head-length
When the backends read straight heads of articles, they all try to read
-as little as possible. This variable (default @code{4096}) specifies
+as little as possible. This variable (default 4096) specifies
the absolute max length the backends will try to read before giving up
on finding a separator line between the head and the body. If this
variable is @code{nil}, there is no upper read bound. If it is
Magnus Hammerin,
Raja R. Harinath,
Marc Horowitz,
-Ishikawa Ichiro,
+Ishikawa Ichiro, @c Ishikawa
Francois Felix Ingrand,
Lee Iverson,
Fred Johansen,
Timo Metzemakers,
Richard Mlynarik,
Lantz Moore,
-MORIOKA Tomohiko,
+Morioka Tomohiko, @c Morioka
Hrvoje Niksic,
Andy Norman,
Ken Olstad,
-Masaharu Onishi,
-Hideki Ono,
+Masaharu Onishi, @c Onishi
+Hideki Ono, @c Ono
Ulrich Pfeifer,
Colin Rafferty,
Bart Robinson,
Christoph Wedler,
Joe Wells,
and
-Katsumi Yamaoka.
+Katsumi Yamaoka. @c Yamaoka
Apologies to everybody that I've forgotten, of which there are many, I'm
sure.
@lisp
(add-hook 'gnus-article-display-hook
- 'gnus-article-hide-boring-headers)
+ 'gnus-article-hide-boring-headers t)
@end lisp
@item
And much, much, much more. There is more to come than has already been
implemented. (But that's always true, isn't it?)
-@file{<URL:http://www.ifi.uio.no/~larsi/sgnus/todo>} is where the actual
+@file{<URL:http://www.ifi.uio.no/~larsi/rgnus/todo>} is where the actual
up-to-the-second todo list is located, so if you're really curious, you
could point your Web browser over that-a-way.
211 56 1000 1059 ifi.discussion
@end example
-The first number is the status, which should be @code{211}. Next is the
+The first number is the status, which should be 211. Next is the
total number of articles in the group, the lowest article number, the
highest article number, and finally the group name. Note that the total
number of articles may be less than one might think while just
projects / gnus / blobdiff