\input texinfo @c -*-texinfo-*-
@setfilename gnus
-@settitle Gnus 5.6.1 Manual
+@settitle Pterodactyl Gnus 0.77 Manual
@synindex fn cp
@synindex vr cp
@synindex pg cp
@c @direntry
-@c * Gnus: (gnus). The news reader Gnus.
+@c * Gnus: (gnus). The newsreader Gnus.
@c @end direntry
@iftex
@finalout
\newcommand{\gnustilde}{\symbol{"7E}}
\newcommand{\gnusless}{{$<$}}
\newcommand{\gnusgreater}{{$>$}}
+\newcommand{\gnusbraceleft}{{$>$}}
+\newcommand{\gnusbraceright}{{$>$}}
\newcommand{\gnushead}{\raisebox{-1cm}{\epsfig{figure=ps/gnus-head.eps,height=1cm}}}
\newcommand{\gnusinteresting}{
}
{
\ifodd\count0
-\mbox{} \hfill
+\mbox{} \hfill
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
\else
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
}
{
\ifodd\count0
-\mbox{} \hfill
+\mbox{} \hfill
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
\else
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
}
{
\ifodd\count0
-\mbox{} \hfill
+\mbox{} \hfill
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
\else
\raisebox{-0.5cm}{\epsfig{figure=ps/gnus-big-logo.eps,height=1cm}}
\thispagestyle{empty}
-Copyright \copyright{} 1995,96,97 Free Software Foundation, Inc.
+Copyright \copyright{} 1995,96,97,98,99 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
This file documents Gnus, the GNU Emacs newsreader.
-Copyright (C) 1995,96 Free Software Foundation, Inc.
+Copyright (C) 1995,96,97,98,99 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
@tex
@titlepage
-@title Gnus 5.6.1 Manual
+@title Pterodactyl Gnus 0.77 Manual
@author by Lars Magne Ingebrigtsen
@page
@vskip 0pt plus 1filll
-Copyright @copyright{} 1995,96,97 Free Software Foundation, Inc.
+Copyright @copyright{} 1995,96,97,98,99 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
spool or your mbox file. All at the same time, if you want to push your
luck.
-This manual corresponds to Gnus 5.6.1.
+This manual corresponds to Pterodactyl Gnus 0.77.
@end ifinfo
@end iflatex
Gnus is the advanced, self-documenting, customizable, extensible
-unreal-time newsreader for GNU Emacs.
+unreal-time newsreader for GNU Emacs.
Oops. That sounds oddly familiar, so let's start over again to avoid
being accused of plagiarism:
@findex gnus
If your system administrator has set things up properly, starting Gnus
and reading news is extremely easy---you just type @kbd{M-x gnus} in
-your Emacs.
+your Emacs.
@findex gnus-other-frame
@kindex M-x gnus-other-frame
@code{gnus-nntp-server} to @code{nil}, which is what it is by default.
@vindex gnus-secondary-servers
+@vindex gnus-nntp-server
You can also make Gnus prompt you interactively for the name of an
@sc{nntp} server. If you give a non-numerical prefix to @code{gnus}
(i.e., @kbd{C-u M-x gnus}), Gnus will let you choose between the servers
in the @code{gnus-secondary-servers} list (if any). You can also just
-type in the name of any server you feel like visiting.
+type in the name of any server you feel like visiting. (Note that this
+will set @code{gnus-nntp-server}, which means that if you then @kbd{M-x
+gnus} later in the same Emacs session, Gnus will contact the same
+server.)
@findex gnus-group-browse-foreign-server
@kindex B (Group)
here as @dfn{whatever Lars thinks you should read}.)
You'll also be subscribed to the Gnus documentation group, which should
-help you with most common problems.
+help you with most common problems.
If @code{gnus-default-subscribed-newsgroups} is @code{t}, Gnus will just
use the normal functions for handling new groups, and not do anything
groups altogether, so you may set @code{gnus-save-killed-list} to
@code{nil}, which will save time both at startup, at exit, and all over.
Saves disk space, too. Why isn't this the default, then?
-Unfortunately, not all servers support this command.
+Unfortunately, not all servers support this command.
I bet I know what you're thinking now: How do I find out whether my
server supports @code{ask-server}? No? Good, because I don't have a
mouthful.) If this variable is non-@code{nil}, Gnus will ask you in a
hierarchical fashion whether to subscribe to new groups or not. Gnus
will ask you for each sub-hierarchy whether you want to descend the
-hierarchy or not.
+hierarchy or not.
One common mistake is to set the variable a few paragraphs above
(@code{gnus-subscribe-newsgroup-method}) to
Sometimes it is necessary to move from one @sc{nntp} server to another.
This happens very rarely, but perhaps you change jobs, or one server is
-very flaky and you want to use another.
+very flaky and you want to use another.
Changing the server is pretty easy, right? You just change
-@code{gnus-select-method} to point to the new server?
+@code{gnus-select-method} to point to the new server?
@emph{Wrong!}
@sc{nntp} servers, and the only way Gnus keeps track of what articles
you have read is by keeping track of article numbers. So when you
change @code{gnus-select-method}, your @file{.newsrc} file becomes
-worthless.
+worthless.
Gnus provides a few functions to attempt to translate a @file{.newsrc}
file from one server to another. They all have one thing in
gnus-group-clear-data-on-native-groups} command to clear out all data
that you have on your native groups. Use with caution.
+After changing servers, you @strong{must} move the cache hierarchy away,
+since the cached articles will have wrong article numbers, which will
+affect which articles Gnus thinks are read.
+
@node Startup Files
@section Startup Files
@vindex gnus-save-newsrc-file
You can turn off writing the @file{.newsrc} file by setting
@code{gnus-save-newsrc-file} to @code{nil}, which means you can delete
-the file and save some space, as well as making exit from Gnus faster.
+the file and save some space, as well as exiting from Gnus faster.
However, this will make it impossible to use other newsreaders than
Gnus. But hey, who would want to, right?
@code{gnus-save-standard-newsrc-hook} is called just before saving the
@file{.newsrc} file. The latter two are commonly used to turn version
control on or off. Version control is on by default when saving the
-startup files. If you want to turn backup creation off, say something like:
+startup files. If you want to turn backup creation off, say something like:
@lisp
(defun turn-off-backup ()
normally the user's home directory.) The dribble file will get the same
file permissions as the @code{.newsrc} file.
+@vindex gnus-always-read-dribble-file
+If @code{gnus-always-read-dribble-file} is non-@code{nil}, Gnus will
+read the dribble file on startup without querying the user.
+
@node The Active File
@section The Active File
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 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
@node Group Buffer Format
@section Group Buffer Format
-@menu
+@menu
* Group Line Specification:: Deciding how the group buffer is to look.
* Group Modeline Specification:: The group buffer modeline.
* Group Highlighting:: Having nice colors in the group buffer.
@code{gnus-group-line-format} variable. This variable works along the
lines of a @code{format} specification, which is pretty much the same as
a @code{printf} specifications, for those of you who use (feh!) C.
-@xref{Formatting Variables}.
+@xref{Formatting Variables}.
@samp{%M%S%5y: %(%g%)\n} is the value that produced those lines above.
@table @samp
-@item M
+@item M
An asterisk if the group only has marked articles.
@item S
Whether the group is subscribed.
-@item L
+@item L
Level of subscribedness.
@item N
used.
@item P
-Indentation based on the level of the topic (@pxref{Group Topics}).
+Indentation based on the level of the topic (@pxref{Group Topics}).
@item c
@vindex gnus-group-uncollapsed-levels
@item d
A string that says when you last read the group (@pxref{Group
-Timestamp}).
+Timestamp}).
@item u
User defined specifier. The next character in the format string should
@vindex gnus-group-mode-line-format
The mode line can be changed by setting
-@code{gnus-group-mode-line-format} (@pxref{Formatting Variables}). It
+@code{gnus-group-mode-line-format} (@pxref{Mode Line Formatting}). It
doesn't understand that many format specifiers:
@table @samp
background is dark:
@lisp
-(face-spec-set 'my-group-face-1 '((t (:foreground "Red" :bold t))))
-(face-spec-set 'my-group-face-2 '((t (:foreground "SeaGreen" :bold t))))
-(face-spec-set 'my-group-face-3 '((t (:foreground "SpringGreen" :bold t))))
-(face-spec-set 'my-group-face-4 '((t (:foreground "SteelBlue" :bold t))))
-(face-spec-set 'my-group-face-5 '((t (:foreground "SkyBlue" :bold t))))
+(face-spec-set 'my-group-face-1
+ '((t (:foreground "Red" :bold t))))
+(face-spec-set 'my-group-face-2
+ '((t (:foreground "SeaGreen" :bold t))))
+(face-spec-set 'my-group-face-3
+ '((t (:foreground "SpringGreen" :bold t))))
+(face-spec-set 'my-group-face-4
+ '((t (:foreground "SteelBlue" :bold t))))
+(face-spec-set 'my-group-face-5
+ '((t (:foreground "SkyBlue" :bold t))))
(setq gnus-group-highlight
'(((> unread 200) . my-group-face-1)
- ((and (< level 3) (zerop unread)) . my-group-face-2)
- ((< level 3) . my-group-face-3)
- ((zerop unread) . my-group-face-4)
-(setq gnus-group-highlight
- `(((> unread 200) .
- ,(custom-face-lookup "Red" nil nil t nil nil))
- ((and (< level 3) (zerop unread)) .
- ,(custom-face-lookup "SeaGreen" nil nil t nil nil))
- ((< level 3) .
- ,(custom-face-lookup "SpringGreen" nil nil t nil nil))
- ((zerop unread) .
- ,(custom-face-lookup "SteelBlue" nil nil t nil nil))
- (t .
- ,(custom-face-lookup "SkyBlue" nil nil t nil nil))))
- (t . my-group-face-5)))
+ ((and (< level 3) (zerop unread)) . my-group-face-2)
+ ((< level 3) . my-group-face-3)
+ ((zerop unread) . my-group-face-4)
+ (t . my-group-face-5)))
@end lisp
Also @pxref{Faces and Fonts}.
The level of the group.
@item score
The score of the group.
-@item ticked
+@item ticked
The number of ticked articles in the group.
@item total
The total number of articles in the group. Or rather, MAX-NUMBER minus
@cindex group movement
All movement commands understand the numeric prefix and will behave as
-expected, hopefully.
+expected, hopefully.
@table @kbd
@findex gnus-group-prev-group
Go to the previous group (@code{gnus-group-prev-group}).
-@item M-p
-@kindex M-p (Group)
+@item M-n
+@kindex M-n (Group)
@findex gnus-group-next-unread-group-same-level
Go to the next unread group on the same (or lower) level
-(@code{gnus-group-next-unread-group-same-level}).
+(@code{gnus-group-next-unread-group-same-level}).
-@item M-n
-@kindex M-n (Group)
+@item M-p
+@kindex M-p (Group)
@findex gnus-group-prev-unread-group-same-level
Go to the previous unread group on the same (or lower) level
-(@code{gnus-group-prev-unread-group-same-level}).
+(@code{gnus-group-prev-unread-group-same-level}).
@end table
Three commands for jumping to groups:
@kindex , (Group)
@findex gnus-group-best-unread-group
Jump to the unread group with the lowest level
-(@code{gnus-group-best-unread-group}).
+(@code{gnus-group-best-unread-group}).
@item .
@kindex . (Group)
@findex gnus-group-first-unread-group
Jump to the first group with unread articles
-(@code{gnus-group-first-unread-group}).
+(@code{gnus-group-first-unread-group}).
@end table
@vindex gnus-group-goto-unread
(@code{gnus-group-select-group}). Takes the same arguments as
@code{gnus-group-read-group}---the only difference is that this command
does not display the first unread article automatically upon group
-entry.
+entry.
@item M-RET
@kindex M-RET (Group)
full summary buffer.
@item t
-Select the first unread article when entering the group.
+Select the first unread article when entering the group.
@item best
-Select the most high-scored article in the group when entering the
-group.
+Select the highest scored article in the group when entering the
+group.
+
+@end table
+
+This variable can also be a function. In that case, that function will
+be called to place point on a subject line, and/or select some article.
+Useful functions include:
+
+@table @code
+@item gnus-summary-first-unread-subject
+Place point on the subject line of the first unread article, but
+don't select the article.
+
+@item gnus-summary-first-unread-article
+Select the first unread article.
+
+@item gnus-summary-best-unread-article
+Select the highest-scored unread article.
@end table
-
+
+
If you want to prevent automatic selection in some group (say, in a
binary group with Huge articles) you can set this variable to @code{nil}
in @code{gnus-select-group-hook}, which is called when a group is
@findex gnus-group-unsubscribe-current-group
@c @icon{gnus-group-unsubscribe}
Toggle subscription to the current group
-(@code{gnus-group-unsubscribe-current-group}).
+(@code{gnus-group-unsubscribe-current-group}).
@item S s
@itemx U
@kindex S w (Group)
@kindex C-w (Group)
@findex gnus-group-kill-region
-Kill all groups in the region (@code{gnus-group-kill-region}).
+Kill all groups in the region (@code{gnus-group-kill-region}).
@item S z
@kindex S z (Group)
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 7 will
kill off all unsubscribed groups that do not have message numbers in the
-@file{.newsrc} file.
+@file{.newsrc} file.
@end table
@kindex C (Group)
@findex gnus-group-catchup-current-all
Mark all articles in this group, even the ticked ones, as read
-(@code{gnus-group-catchup-current-all}).
+(@code{gnus-group-catchup-current-all}).
@item M-c
@kindex M-c (Group)
If you have switched from one @sc{nntp} server to another, all your marks
and read ranges have become worthless. You can use this command to
clear out all data that you have on your native groups. Use with
-caution.
+caution.
@end table
(@pxref{Listing Groups}), or to just check for new articles in groups on
a given level or lower (@pxref{Scanning New Messages}).
-Remember: The higher the level of the group, the less important it is.
+Remember: The higher the level of the group, the less important it is.
@table @kbd
If @code{gnus-group-list-inactive-groups} is non-@code{nil}, non-active
groups will be listed along with the unread groups. This variable is
@code{t} by default. If it is @code{nil}, inactive groups won't be
-listed.
+listed.
@vindex gnus-group-use-permanent-levels
If @code{gnus-group-use-permanent-levels} is non-@code{nil}, once you
You would normally keep important groups on high levels, but that scheme
is somewhat restrictive. Don't you wish you could have Gnus sort the
group buffer according to how often you read groups, perhaps? Within
-reason?
+reason?
This is what @dfn{group score} is for. You can assign a score to each
group. You can then sort the group buffer based on this score.
@itemx M m
@kindex M m (Group)
@findex gnus-group-mark-group
-Set the mark on the current group (@code{gnus-group-mark-group}).
+Set the mark on the current group (@code{gnus-group-mark-group}).
@item M-#
@kindex M-# (Group)
@kindex M u (Group)
@findex gnus-group-unmark-group
Remove the mark from the current group
-(@code{gnus-group-unmark-group}).
+(@code{gnus-group-unmark-group}).
@item M U
@kindex M U (Group)
@findex gnus-group-unmark-all-groups
-Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
+Remove the mark from all groups (@code{gnus-group-unmark-all-groups}).
@item M w
@kindex M w (Group)
@findex gnus-group-mark-region
-Mark all groups between point and mark (@code{gnus-group-mark-region}).
+Mark all groups between point and mark (@code{gnus-group-mark-region}).
@item M b
@kindex M b (Group)
@findex gnus-group-mark-buffer
-Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
+Mark all groups in the buffer (@code{gnus-group-mark-buffer}).
@item M r
@kindex M r (Group)
@findex gnus-group-mark-regexp
Mark all groups that match some regular expression
-(@code{gnus-group-mark-regexp}).
+(@code{gnus-group-mark-regexp}).
@end table
Also @pxref{Process/Prefix}.
@kindex G p (Group)
@findex gnus-group-edit-group-parameters
Enter a buffer where you can edit the group parameters
-(@code{gnus-group-edit-group-parameters}).
+(@code{gnus-group-edit-group-parameters}).
@item G E
@kindex G E (Group)
Make a directory group (@pxref{Directory Groups}). You will be prompted
for a directory name (@code{gnus-group-make-directory-group}).
-@item G h
+@item G h
@kindex G h (Group)
@cindex help group
@findex gnus-group-make-help-group
@cindex nneething
Read an arbitrary directory as if it were a newsgroup with the
@code{nneething} backend (@code{gnus-group-enter-directory}).
-@xref{Anything Groups}.
+@xref{Anything Groups}.
@item G f
@kindex G f (Group)
this command without a prefix, Gnus will guess at the file type.
@xref{Document Groups}.
+@item G u
+@kindex G u (Group)
+@vindex gnus-useful-groups
+@findex gnus-group-make-useful-group
+Create one of the groups mentioned in @code{gnus-useful-groups}
+(@code{gnus-group-make-useful-group}).
+
@item G w
@kindex G w (Group)
@findex gnus-group-make-web-group
include @code{dejanews}, @code{altavista} and @code{reference}.
@xref{Web Searches}.
+If you use the @code{dejanews} search engine, you can limit the search
+to a particular group by using a match string like
+@samp{~g alt.sysadmin.recovery shaving}.
+
@item G DEL
@kindex G DEL (Group)
@findex gnus-group-delete-group
@end table
@xref{Select Methods} for more information on the various select
-methods.
+methods.
@vindex gnus-activate-foreign-newsgroups
If @code{gnus-activate-foreign-newsgroups} is a positive number,
Gnus will check all foreign groups with this level or lower at startup.
This might take quite a while, especially if you subscribe to lots of
-groups from different @sc{nntp} servers.
+groups from different @sc{nntp} servers. Also @pxref{Group Levels};
+@code{gnus-activate-level} also affects activation of foreign
+newsgroups.
@node Group Parameters
@section Group Parameters
@cindex group parameters
-The group parameters store information local to a particular group:
+The group parameters store information local to a particular group.
+Here's an example group parameter list:
+
+@example
+((to-address . "ding@@gnus.org")
+ (auto-expire . t))
+@end example
+
+We see that each element consists of a "dotted pair"---the thing before
+the dot is the key, while the thing after the dot is the value. All the
+parameters have this form @emph{except} local variable specs, which are
+not dotted pairs, but proper lists.
+
+The following group parameters can be used:
@table @code
@item to-address
@cindex to-address
-If the group parameter list contains an element that looks like
-@code{(to-address . "some@@where.com")}, that address will be used by
-the backend when doing followups and posts. This is primarily useful in
-mail groups that represent closed mailing lists---mailing lists where
-it's expected that everybody that writes to the mailing list is
-subscribed to it. Since using this parameter ensures that the mail only
-goes to the mailing list itself, it means that members won't receive two
-copies of your followups.
+Address used by when doing followups and new posts.
+
+@example
+(to-address . "some@@where.com")
+@end example
+
+This is primarily useful in mail groups that represent closed mailing
+lists---mailing lists where it's expected that everybody that writes to
+the mailing list is subscribed to it. Since using this parameter
+ensures that the mail only goes to the mailing list itself, it means
+that members won't receive two copies of your followups.
Using @code{to-address} will actually work whether the group is foreign
or not. Let's say there's a group on the server that is called
@samp{fa.4ad-l}. This is a real newsgroup, but the server has gotten
the articles from a mail-to-news gateway. Posting directly to this
group is therefore impossible---you have to send mail to the mailing
-list address instead.
+list address instead.
@item to-list
@cindex to-list
-If the group parameter list has an element that looks like
-@code{(to-list . "some@@where.com")}, that address will be used when
-doing a @kbd{a} in that group. It is totally ignored when doing a
-followup---except that if it is present in a news group, you'll get mail
-group semantics when doing @kbd{f}.
+Address used when doing a @kbd{a} in that group.
+
+@example
+(to-list . "some@@where.com")
+@end example
+
+It is totally ignored
+when doing a followup---except that if it is present in a news group,
+you'll get mail group semantics when doing @kbd{f}.
If you do an @kbd{a} command in a mail group and you have neither a
-@code{to-list} group parameter nor a @code{to-address} group paramater,
+@code{to-list} group parameter nor a @code{to-address} group parameter,
then a @code{to-list} group parameter will be added automatically upon
sending the message if @code{gnus-add-to-list} is set to @code{t}.
@vindex gnus-add-to-list
@item to-group
@cindex to-group
Elements like @code{(to-group . "some.group.name")} means that all
-posts in that group will be sent to @code{some.group.name}.
+posts in that group will be sent to @code{some.group.name}.
@item newsgroup
@cindex newsgroup
-If this symbol is present in the group parameter list, Gnus will treat
-all responses as if they were responses to news articles. This can be
-useful if you have a mail group that's really a mirror of a news group.
+If you have @code{(newsgroup . t)} in the group parameter list, Gnus
+will treat all responses as if they were responses to news articles.
+This can be useful if you have a mail group that's really a mirror of a
+news group.
@item gcc-self
@cindex gcc-self
-If this symbol is present in the group parameter list and set to
-@code{t}, newly composed messages will be @code{Gcc}'d to the current
-group. If it is present and set to @code{none}, no @code{Gcc:} header
-will be generated, if it is present and a string, this string will be
-inserted literally as a @code{gcc} header (this symbol takes precedence
-over any default @code{Gcc} rules as described later). @xref{Archived
-Messages}
+If @code{(gcc-self . t)} is present in the group parameter list, newly
+composed messages will be @code{Gcc}'d to the current group. If
+@code{(gcc-self . none)} is present, no @code{Gcc:} header will be
+generated, if @code{(gcc-self . "string")} is present, this string will
+be inserted literally as a @code{gcc} header. This parameter takes
+precedence over any default @code{Gcc} rules as described later
+(@pxref{Archived Messages}).
@item auto-expire
@cindex auto-expire
@item score-file
@cindex score file group parameter
Elements that look like @code{(score-file . "file")} will make
-@file{file} into the current adaptive score file for the group in
-question. All adaptive score entries will be put into this file.
+@file{file} into the current score file for the group in question. All
+interactive score entries will be put into this file.
@item adapt-file
@cindex adapt file group parameter
Elements that look like @code{(comment . "This is a comment")}
are arbitrary comments on the group. They are currently ignored by
Gnus, but provide a place for you to store information on particular
-groups.
+groups.
+
+@item charset
+Elements that look like @code{(charset . iso-8859-1)} will make
+@code{iso-8859-1} the default charset; that is, the charset that will be
+used for all articles that do not specify a charset.
@item @var{(variable form)}
You can use the group parameters to set variables local to the group you
group. @code{dummy-variable} will be set to the result of the
@code{(ding)} form, but who cares?
+@item posting-style
+You can store additional posting style information for this group only
+here (@pxref{Posting Styles}). The format is that of an entry in the
+@code{gnus-posting-styles} alist, except that there's no regexp matching
+the group name (of course). Style elements in this group parameter will
+take precedence over the ones found in @code{gnus-posting-styles}.
+
+For instance, if you want a funky name and signature in this group only,
+instead of hacking @code{gnus-posting-styles}, you could put something
+like this in the group parameters:
+
+@example
+(posting-style
+ (name "Funky Name")
+ (signature "Funky Signature"))
+@end example
+
@end table
Use the @kbd{G p} command to edit group parameters of a group. You
might also be interested in reading about topic parameters (@pxref{Topic
Parameters}).
-Here's an example group parameter list:
-
-@example
-((to-address . "ding@@gnus.org")
- (auto-expire . t))
-@end example
-
@node Listing Groups
@section Listing Groups
@kindex A m (Group)
@findex gnus-group-list-matching
List all unread, subscribed groups with names that match a regexp
-(@code{gnus-group-list-matching}).
+(@code{gnus-group-list-matching}).
@item A M
@kindex A M (Group)
The @kbd{C-c C-s} (@code{gnus-group-sort-groups}) command sorts the
group buffer according to the function(s) given by the
@code{gnus-group-sort-function} variable. Available sorting functions
-include:
+include:
@table @code
@kindex G S a (Group)
@findex gnus-group-sort-groups-by-alphabet
Sort the group buffer alphabetically by group name
-(@code{gnus-group-sort-groups-by-alphabet}).
+(@code{gnus-group-sort-groups-by-alphabet}).
@item G S u
@kindex G S u (Group)
@kindex G S l (Group)
@findex gnus-group-sort-groups-by-level
Sort the group buffer by group level
-(@code{gnus-group-sort-groups-by-level}).
+(@code{gnus-group-sort-groups-by-level}).
@item G S v
@kindex G S v (Group)
@kindex G S m (Group)
@findex gnus-group-sort-groups-by-method
Sort the group buffer alphabetically by backend name
-(@code{gnus-group-sort-groups-by-method}).
+(@code{gnus-group-sort-groups-by-method}).
@end table
-When given a prefix, all these commands will sort in reverse order.
+All the commands below obeys the process/prefix convention
+(@pxref{Process/Prefix}).
+
+When given a symbolic prefix (@pxref{Symbolic Prefixes}), all these
+commands will sort in reverse order.
You can also sort a subset of the groups:
@item G P a
@kindex G P a (Group)
@findex gnus-group-sort-selected-groups-by-alphabet
-Sort the process/prefixed groups in the group buffer alphabetically by
-group name (@code{gnus-group-sort-selected-groups-by-alphabet}).
+Sort the groups alphabetically by group name
+(@code{gnus-group-sort-selected-groups-by-alphabet}).
@item G P u
@kindex G P u (Group)
@findex gnus-group-sort-selected-groups-by-unread
-Sort the process/prefixed groups in the group buffer by the number of
-unread articles (@code{gnus-group-sort-selected-groups-by-unread}).
+Sort the groups by the number of unread articles
+(@code{gnus-group-sort-selected-groups-by-unread}).
@item G P l
@kindex G P l (Group)
@findex gnus-group-sort-selected-groups-by-level
-Sort the process/prefixed groups in the group buffer by group level
+Sort the groups by group level
(@code{gnus-group-sort-selected-groups-by-level}).
@item G P v
@kindex G P v (Group)
@findex gnus-group-sort-selected-groups-by-score
-Sort the process/prefixed groups in the group buffer by group score
+Sort the groups by group score
(@code{gnus-group-sort-selected-groups-by-score}). @xref{Group Score}.
@item G P r
@kindex G P r (Group)
@findex gnus-group-sort-selected-groups-by-rank
-Sort the process/prefixed groups in the group buffer by group rank
+Sort the groups by group rank
(@code{gnus-group-sort-selected-groups-by-rank}). @xref{Group Score}.
@item G P m
@kindex G P m (Group)
@findex gnus-group-sort-selected-groups-by-method
-Sort the process/prefixed groups in the group buffer alphabetically by
-backend name (@code{gnus-group-sort-selected-groups-by-method}).
+Sort the groups alphabetically by backend name
+(@code{gnus-group-sort-selected-groups-by-method}).
@end table
@kindex F (Group)
@findex gnus-group-find-new-groups
Find new groups and process them (@code{gnus-group-find-new-groups}).
-If given a prefix, use the @code{ask-server} method to query the server
-for new groups.
+With 1 @kbd{C-u}, use the @code{ask-server} method to query the server
+for new groups. With 2 @kbd{C-u}'s, use most complete method possible
+to query the server for new groups, and subscribe the new groups as
+zombies.
@item C-c C-x
@kindex C-c C-x (Group)
@kindex SPACE (Browse)
@findex gnus-browse-read-group
Enter the current group and display the first article
-(@code{gnus-browse-read-group}).
+(@code{gnus-browse-read-group}).
@item RET
@kindex RET (Browse)
@findex gnus-browse-select-group
-Enter the current group (@code{gnus-browse-select-group}).
+Enter the current group (@code{gnus-browse-select-group}).
@item u
@kindex u (Browse)
@findex gnus-browse-unsubscribe-current-group
Unsubscribe to the current group, or, as will be the case here,
-subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
+subscribe to it (@code{gnus-browse-unsubscribe-current-group}).
@item l
@itemx q
(add-hook 'gnus-group-mode-hook 'gnus-topic-mode)
@end lisp
-@menu
+@menu
* Topic Variables:: How to customize the topics the Lisp Way.
* Topic Commands:: Interactive E-Z commands.
* Topic Sorting:: Sorting each topic individually.
Number of groups in the topic.
@item a
Number of unread articles in the topic.
-@item A
-Number of unread articles in the topic and all its subtopics.
+@item A
+Number of unread articles in the topic and all its subtopics.
@end table
@vindex gnus-topic-indent-level
The default is 2.
@vindex gnus-topic-mode-hook
-@code{gnus-topic-mode-hook} is called in topic minor mode buffers.
+@code{gnus-topic-mode-hook} is called in topic minor mode buffers.
@vindex gnus-topic-display-empty-topics
The @code{gnus-topic-display-empty-topics} says whether to display even
@item T n
@kindex T n (Topic)
@findex gnus-topic-create-topic
-Prompt for a new topic name and create it
-(@code{gnus-topic-create-topic}).
+Prompt for a new topic name and create it
+(@code{gnus-topic-create-topic}).
@item T m
@kindex T m (Topic)
@kindex T D (Topic)
@findex gnus-topic-remove-group
Remove a group from the current topic (@code{gnus-topic-remove-group}).
+This command is mainly useful if you have the same group in several
+topics and wish to remove it from one of the topics. You may also
+remove a group from all topics, but in that case, Gnus will add it to
+the root topic the next time you start Gnus. In fact, all new groups
+(which, naturally, don't belong to any topic) will show up in the root
+topic.
+
This command uses the process/prefix convention
(@pxref{Process/Prefix}).
@kindex T M (Topic)
@findex gnus-topic-move-matching
Move all groups that match some regular expression to a topic
-(@code{gnus-topic-move-matching}).
+(@code{gnus-topic-move-matching}).
@item T C
@kindex T C (Topic)
@findex gnus-topic-copy-matching
Copy all groups that match some regular expression to a topic
-(@code{gnus-topic-copy-matching}).
+(@code{gnus-topic-copy-matching}).
-@item T h
-@kindex T h (Topic)
+@item T H
+@kindex T H (Topic)
@findex gnus-topic-toggle-display-empty-topics
Toggle hiding empty topics
-(@code{gnus-topic-toggle-display-empty-topics}).
+(@code{gnus-topic-toggle-display-empty-topics}).
@item T #
@kindex T # (Topic)
@findex gnus-topic-mark-topic
Mark all groups in the current topic with the process mark
-(@code{gnus-topic-mark-topic}).
+(@code{gnus-topic-mark-topic}).
@item T M-#
@kindex T M-# (Topic)
@findex gnus-topic-unmark-topic
Remove the process mark from all groups in the current topic
-(@code{gnus-topic-unmark-topic}).
+(@code{gnus-topic-unmark-topic}).
+
+@item T TAB
+@itemx TAB
+@kindex T TAB (Topic)
+@kindex TAB (Topic)
+@findex gnus-topic-indent
+``Indent'' the current topic so that it becomes a sub-topic of the
+previous topic (@code{gnus-topic-indent}). If given a prefix,
+``un-indent'' the topic instead.
+
+@item M-TAB
+@kindex M-TAB (Topic)
+@findex gnus-topic-unindent
+``Un-indent'' the current topic so that it becomes a sub-topic of the
+parent of its current parent (@code{gnus-topic-unindent}).
@item RET
@kindex RET (Topic)
toggling command on topics. In addition, if you give a numerical
prefix, group on that level (and lower) will be displayed.
-@item T TAB
-@kindex T TAB (Topic)
-@findex gnus-topic-indent
-``Indent'' the current topic so that it becomes a sub-topic of the
-previous topic (@code{gnus-topic-indent}). If given a prefix,
-``un-indent'' the topic instead.
+@item C-c C-x
+@kindex C-c C-x (Topic)
+@findex gnus-topic-expire-articles
+Run all expirable articles in the current group or topic through the expiry
+process (if any) (@code{gnus-topic-expire-articles}).
@item C-k
@kindex C-k (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.
+before all groups.
@item T r
@kindex T r (Topic)
@findex gnus-topic-rename
-Rename a topic (@code{gnus-topic-rename}).
+Rename a topic (@code{gnus-topic-rename}).
@item T DEL
@kindex T DEL (Topic)
@findex gnus-topic-delete
-Delete an empty topic (@code{gnus-topic-delete}).
+Delete an empty topic (@code{gnus-topic-delete}).
@item A T
@kindex A T (Topic)
@cindex topic sorting
You can sort the groups in each topic individually with the following
-commands:
+commands:
@table @kbd
@kindex T S a (Topic)
@findex gnus-topic-sort-groups-by-alphabet
Sort the current topic alphabetically by group name
-(@code{gnus-topic-sort-groups-by-alphabet}).
+(@code{gnus-topic-sort-groups-by-alphabet}).
@item T S u
@kindex T S u (Topic)
@kindex T S l (Topic)
@findex gnus-topic-sort-groups-by-level
Sort the current topic by group level
-(@code{gnus-topic-sort-groups-by-level}).
+(@code{gnus-topic-sort-groups-by-level}).
@item T S v
@kindex T S v (Topic)
@kindex T S m (Topic)
@findex gnus-topic-sort-groups-by-method
Sort the current topic alphabetically by backend name
-(@code{gnus-topic-sort-groups-by-method}).
+(@code{gnus-topic-sort-groups-by-method}).
@end table
-@xref{Sorting Groups} for more information about group sorting.
+@xref{Sorting Groups} for more information about group sorting.
@node Topic Topology
@lisp
(("Gnus" visible)
- (("Emacs -- I wuw it!" visible)
+ (("Emacs -- I wuw it!" visible)
(("Naughty Emacs" visible)))
(("Misc" visible)))
@end lisp
for the display above. That variable is saved in the @file{.newsrc.eld}
file, and shouldn't be messed with manually---unless you really want
to. Since this variable is read from the @file{.newsrc.eld} file,
-setting it in any other startup files will have no effect.
+setting it in any other startup files will have no effect.
This topology shows what topics are sub-topics of what topics (right),
and which topics are visible. Two settings are currently
All groups in a topic will inherit group parameters from the parent (and
ancestor) topic parameters. All valid group parameters are valid topic
-parameters (@pxref{Group Parameters}).
+parameters (@pxref{Group Parameters}).
Group parameters (of course) override topic parameters, and topic
parameters in sub-topics override topic parameters in super-topics. You
. "emacs.SCORE")}; the @samp{Relief} topic has the topic parameter
@code{(score-file . "relief.SCORE")}; and the @samp{Misc} topic has the
topic parameter @code{(score-file . "emacs.SCORE")}. In addition,
-@samp{alt.religion.emacs} has the group parameter @code{(score-file
+@* @samp{alt.religion.emacs} has the group parameter @code{(score-file
. "religion.SCORE")}.
Now, when you enter @samp{alt.sex.emacs} in the @samp{Relief} topic, you
@item gnus-group-mode-hook
@vindex gnus-group-mode-hook
is called after the group buffer has been
-created.
+created.
@item gnus-group-prepare-hook
@vindex gnus-group-prepare-hook
@cindex activating groups
@item C-c M-g
@kindex C-c M-g (Group)
-Activate absolutely all groups (@code{gnus-activate-all-groups}).
+Activate absolutely all groups (@code{gnus-activate-all-groups}).
@item R
@kindex R (Group)
@end table
@vindex gnus-get-new-news-hook
-@code{gnus-get-new-news-hook} is run just before checking for new news.
+@code{gnus-get-new-news-hook} is run just before checking for new news.
@vindex gnus-after-getting-new-news-hook
@code{gnus-after-getting-new-news-hook} is run after checking for new
use the @samp{%d} spec in the group line format:
@lisp
-(setq gnus-group-line-format
+(setq gnus-group-line-format
"%M\%S\%p\%P\%5y: %(%-40,40g%) %d\n")
@end lisp
something like:
@lisp
-(setq gnus-group-line-format
+(setq gnus-group-line-format
"%M\%S\%p\%P\%5y: %(%-40,40g%) %6,6~(cut 2)d\n")
@end lisp
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}).
+group buffer (@pxref{Selecting a Group}).
You can have as many summary buffers open as you wish.
* Saving Articles:: Ways of customizing article saving.
* Decoding Articles:: Gnus can treat series of (uu)encoded articles.
* Article Treatment:: The article buffer can be mangled at will.
+* MIME Commands:: Doing MIMEy things with the articles.
+* Charsets:: Character set issues.
* Article Commands:: Doing various things with the article buffer.
* Summary Sorting:: Sorting the summary buffer in various ways.
* Finding the Parent:: No child support? Get the parent.
@menu
* Summary Buffer Lines:: You can specify how summary lines should look.
+* To From Newsgroups:: How to not display your own name.
* Summary Buffer Mode Line:: You can say how the mode line should look.
* Summary Highlighting:: Making the summary buffer all pretty and nice.
@end menu
fast, and too simplistic solution; and
@code{mail-extract-address-components}, which works very nicely, but is
slower. The default function will return the wrong answer in 5% of the
-cases. If this is unacceptable to you, use the other function instead.
+cases. If this is unacceptable to you, use the other function instead:
+
+@lisp
+(setq gnus-extract-address-components
+ 'mail-extract-address-components)
+@end lisp
@vindex gnus-summary-same-subject
@code{gnus-summary-same-subject} is a string indicating that the current
The following format specification characters are understood:
@table @samp
-@item N
+@item N
Article number.
@item S
Subject string.
Full @code{From} header.
@item n
The name (from the @code{From} header).
+@item f
+The name, code @code{To} header or the @code{Newsgroups} header
+(@pxref{To From Newsgroups}).
@item a
The name (from the @code{From} header). This differs from the @code{n}
spec in that it uses the function designated by the
Twenty minus thread level spaces.
@item U
Unread.
+
@item R
-Replied.
+This misleadingly named specifier is the @dfn{secondary mark}. This
+mark will say whether the article has been replied to, has been cached,
+or has been saved.
+
@item i
Score as a number (@pxref{Scoring}).
@item z
@vindex gnus-summary-zcore-fuzz
Zcore, @samp{+} if above the default level and @samp{-} if below the
default level. If the difference between
-@code{gnus-summary-default-level} and the score is less than
+@code{gnus-summary-default-score} and the score is less than
@code{gnus-summary-zcore-fuzz}, this spec will not be used.
@item V
Total thread score.
This restriction may disappear in later versions of Gnus.
+@node To From Newsgroups
+@subsection To From Newsgroups
+@cindex To
+@cindex Newsgroups
+
+In some groups (particularly in archive groups), the @code{From} header
+isn't very interesting, since all the articles there are written by
+you. To display the information in the @code{To} or @code{Newsgroups}
+headers instead, you need to decide three things: What information to
+gather; where to display it; and when to display it.
+
+@enumerate
+@item
+@vindex gnus-extra-headers
+The reading of extra header information is controlled by the
+@code{gnus-extra-headers}. This is a list of header symbols. For
+instance:
+
+@lisp
+(setq gnus-extra-headers
+ '(To Newsgroups X-Newsreader))
+@end lisp
+
+This will result in Gnus trying to obtain these three headers, and
+storing it in header structures for later easy retrieval.
+
+@item
+@findex gnus-extra-header
+The value of these extra headers can be accessed via the
+@code{gnus-extra-header} function. Here's a format line spec that will
+access the @code{X-Newsreader} header:
+
+@example
+"%~(form (gnus-extra-header 'X-Newsreader))@@"
+@end example
+
+@item
+@vindex gnus-ignored-from-addresses
+The @code{gnus-ignored-from-addresses} variable says when the @samp{%f}
+summary line spec returns the @code{To}, @code{Newsreader} or
+@code{From} header. If this regexp matches the contents of the
+@code{From} header, the value of the @code{To} or @code{Newsreader}
+headers are used instead.
+
+@end enumerate
+
+@vindex nnmail-extra-headers
+A related variable is @code{nnmail-extra-headers}, which controls when
+to include extra headers when generating overview (@sc{nov}) files. If
+you have old overview files, you should regenerate them after changing
+this variable.
+
+@vindex gnus-summary-line-format
+You also have to instruct Gnus to display the data by changing the
+@code{%n} spec to the @code{%f} spec in the
+@code{gnus-summary-line-format} variable.
+
+In summary, you'd typically do something like the following:
+
+@lisp
+(setq gnus-extra-headers
+ '(To Newsgroups))
+(setq nnmail-extra-headers gnus-extra-headers)
+(setq gnus-summary-line-format
+ "%U%R%z%I%(%[%4L: %-20,20f%]%) %s\n")
+(setq gnus-ignored-from-addresses
+ "Your Name Here")
+@end lisp
+
+Now, this is mostly useful for mail groups, where you have control over
+the @sc{nov} files that are created. However, if you can persuade your
+nntp admin to add:
+
+@example
+Newsgroups:full
+@end example
+
+to the end of her @file{overview.fmt} file, then you can use that just
+as you would the extra headers from the mail groups.
+
+
@node Summary Buffer Mode Line
@subsection Summary Buffer Mode Line
@vindex gnus-summary-mode-line-format
-You can also change the format of the summary mode bar. Set
-@code{gnus-summary-mode-line-format} to whatever you like. The default
-is @samp{Gnus: %%b [%A] %Z}.
+You can also change the format of the summary mode bar (@pxref{Mode Line
+Formatting}). Set @code{gnus-summary-mode-line-format} to whatever you
+like. The default is @samp{Gnus: %%b [%A] %Z}.
Here are the elements you can play with:
Unprefixed group name.
@item A
Current article number.
+@item z
+Current article score.
@item V
Gnus version.
@item U
and no unselected ones.
@item g
Shortish group name. For instance, @samp{rec.arts.anime} will be
-shortened to @samp{r.a.anime}.
+shortened to @samp{r.a.anime}.
@item S
Subject of the current article.
@item u
@item t
Number of ticked articles (@pxref{Unread Articles}).
@item r
-Number of articles that have been marked as read in this session.
+Number of articles that have been marked as read in this session.
@item E
Number of articles expunged by the score files.
@end table
@cindex summary movement
All the straight movement commands understand the numeric prefix and
-behave pretty much as you'd expect.
+behave pretty much as you'd expect.
None of these commands select articles.
@kindex G M-n (Summary)
@findex gnus-summary-next-unread-subject
Go to the next summary line of an unread article
-(@code{gnus-summary-next-unread-subject}).
+(@code{gnus-summary-next-unread-subject}).
@item G M-p
@itemx M-p
@kindex G M-p (Summary)
@findex gnus-summary-prev-unread-subject
Go to the previous summary line of an unread article
-(@code{gnus-summary-prev-unread-subject}).
+(@code{gnus-summary-prev-unread-subject}).
@item G j
@itemx j
If non-@code{nil}, all the movement commands will try to go to the next
article with the same subject as the current. (@dfn{Same} here might
mean @dfn{roughly equal}. See @code{gnus-summary-gather-subject-limit}
-for details (@pxref{Customizing Threading}).) This variable is not
-particularly useful if you use a threaded display.
+for details (@pxref{Customizing Threading}).) If there are no more
+articles with the same subject, go to the first unread article.
+
+This variable is not particularly useful if you use a threaded display.
@item gnus-summary-check-current
@vindex gnus-summary-check-current
buffer, which might make it more inconvenient to read extremely long
threads.
+This variable can also be a number. In that case, center the window at
+the given number of lines from the top.
+
@end table
@kindex G C-n (Summary)
@findex gnus-summary-next-same-subject
Go to the next article with the same subject
-(@code{gnus-summary-next-same-subject}).
+(@code{gnus-summary-next-same-subject}).
@item G C-p
@kindex G C-p (Summary)
@findex gnus-summary-prev-same-subject
Go to the previous article with the same subject
-(@code{gnus-summary-prev-same-subject}).
+(@code{gnus-summary-prev-same-subject}).
@item G f
@itemx .
@kindex , (Summary)
@findex gnus-summary-best-unread-article
Go to the article with the highest score
-(@code{gnus-summary-best-unread-article}).
+(@code{gnus-summary-best-unread-article}).
@item G l
@itemx l
@item DEL
@kindex DEL (Summary)
@findex gnus-summary-prev-page
-Scroll the current article back one page (@code{gnus-summary-prev-page}).
+Scroll the current article back one page (@code{gnus-summary-prev-page}).
@item RET
@kindex RET (Summary)
Scroll the current article one line forward
(@code{gnus-summary-scroll-up}).
+@item M-RET
+@kindex M-RET (Summary)
+@findex gnus-summary-scroll-down
+Scroll the current article one line backward
+(@code{gnus-summary-scroll-down}).
+
@item A g
@itemx g
@kindex A g (Summary)
@findex gnus-summary-end-of-article
Scroll to the end of the article (@code{gnus-summary-end-of-article}).
-@item A s
+@item A s
@itemx s
@kindex A s (Summary)
@kindex s (Summary)
@c @icon{gnus-summary-mail-reply}
@c @icon{gnus-summary-reply}
Mail a reply to the author of the current article
-(@code{gnus-summary-reply}).
+(@code{gnus-summary-reply}).
@item S R
@itemx R
@kindex S W (Summary)
@findex gnus-summary-wide-reply-with-original
Mail a wide reply to the current article and include the original
-message (@code{gnus-summary-reply-with-original}). This command uses
+message (@code{gnus-summary-wide-reply-with-original}). This command uses
the process/prefix convention.
@item S o m
@code{Resent-To}, @code{Resent-From} and so on will be added. This
means that you actually send a mail to someone that has a @code{To}
header that (probably) points to yourself. This will confuse people.
-So, natcherly you'll only do that if you're really eVIl.
+So, natcherly you'll only do that if you're really eVIl.
This command is mainly used if you have several accounts and want to
ship a mail to a different account of yours. (If you're both
@code{postmaster}. Ordnung muß sein!
This command understands the process/prefix convention
-(@pxref{Process/Prefix}).
+(@pxref{Process/Prefix}).
@item S O m
@kindex S O m (Summary)
@cindex crossposting
@cindex excessive crossposting
Send a complaint about excessive crossposting to the author of the
-current article (@code{gnus-summary-mail-crosspost-complaint}).
+current article (@code{gnus-summary-mail-crosspost-complaint}).
@findex gnus-crosspost-complaint
-This command is provided as a way to fight back agains the current
+This command is provided as a way to fight back against the current
crossposting pandemic that's sweeping Usenet. It will compose a reply
using the @code{gnus-crosspost-complaint} variable as a preamble. This
command understands the process/prefix convention
@end table
+Also @pxref{(message)Header Commands} for more information.
+
@node Summary Post Commands
@subsection Summary Post Commands
Post a followup to the current article via news, even if you got the
message through mail (@code{gnus-summary-followup-to-mail}).
-@item S n
-@kindex S n (Summary)
-@findex gnus-summary-followup-to-mail
+@item S N
+@kindex S N (Summary)
+@findex gnus-summary-followup-to-mail-with-original
Post a followup to the current article via news, even if you got the
message through mail and include the original message
(@code{gnus-summary-followup-to-mail-with-original}). This command uses
@findex gnus-uu-post-news
@c @icon{gnus-uu-post-news}
Uuencode a file, split it into parts, and post it as a series
-(@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
+(@code{gnus-uu-post-news}). (@pxref{Uuencoding and Posting}).
@end table
+Also @pxref{(message)Header Commands} for more information.
+
@node Canceling and Superseding
@section Canceling Articles
live on here and there, while most sites will delete the article in
question.
-Gnus will use the ``current'' select method when cancelling. If you
+Gnus will use the ``current'' select method when canceling. If you
want to use the standard posting method, use the @samp{a} symbolic
prefix (@pxref{Symbolic Prefixes}).
@cindex article ticking
@cindex marks
-There are several marks you can set on an article.
+There are several marks you can set on an article.
You have marks that decide the @dfn{readedness} (whoo, neato-keano
neologism ohoy!) of the article. Alphabetic marks generally mean
reading it, or replying to it, until sometime later, you'd typically
tick it. However, articles can be expired, so if you want to keep an
article forever, you'll have to make it persistent (@pxref{Persistent
-Articles}).
+Articles}).
@item ?
@vindex gnus-dormant-mark
-Marked as dormant (@code{gnus-dormant-mark}).
+Marked as dormant (@code{gnus-dormant-mark}).
@dfn{Dormant articles} will only appear in the summary buffer if there
are followups to it. If you want to see them even if they don't have
@item SPACE
@vindex gnus-unread-mark
-Markes as unread (@code{gnus-unread-mark}).
+Marked as unread (@code{gnus-unread-mark}).
@dfn{Unread articles} are articles that haven't been read at all yet.
@end table
@itemize @bullet
-@item
+@item
You can set a bookmark in the current article. Say you are reading a
long thesis on cats' urinary tracts, and have to go home for dinner
before you've finished reading the thesis. You can then set a bookmark
in the article, and Gnus will jump to this bookmark the next time it
-encounters the article. @xref{Setting Marks}
+encounters the article. @xref{Setting Marks}.
@item
@vindex gnus-replied-mark
answered) will be marked with an @samp{A} in the second column
(@code{gnus-replied-mark}).
-@item
+@item
@vindex gnus-cached-mark
Articles stored in the article cache will be marked with an @samp{*} in
-the second column (@code{gnus-cached-mark}). @xref{Article Caching}
+the second column (@code{gnus-cached-mark}). @xref{Article Caching}.
-@item
+@item
@vindex gnus-saved-mark
Articles ``saved'' (in some manner or other; not necessarily
religiously) are marked with an @samp{S} in the second column
(@code{gnus-saved-mark}).
-@item
+@item
@vindex gnus-not-empty-thread-mark
@vindex gnus-empty-thread-mark
If the @samp{%e} spec is used, the presence of threads or not will be
marked with @code{gnus-not-empty-thread-mark} and
@code{gnus-empty-thread-mark} in the third column, respectively.
-@item
+@item
@vindex gnus-process-mark
Finally we have the @dfn{process mark} (@code{gnus-process-mark}). A
variety of commands react to the presence of the process mark. For
@kindex M t (Summary)
@findex gnus-summary-tick-article-forward
Tick the current article (@code{gnus-summary-tick-article-forward}).
-@xref{Article Caching}
+@xref{Article Caching}.
@item M ?
@itemx ?
@kindex M ? (Summary)
@findex gnus-summary-mark-as-dormant
Mark the current article as dormant
-(@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}
+(@code{gnus-summary-mark-as-dormant}). @xref{Article Caching}.
@item M d
@itemx d
@kindex C-k (Summary)
@findex gnus-summary-kill-same-subject
Mark all articles that have the same subject as the current one as read
-(@code{gnus-summary-kill-same-subject}).
+(@code{gnus-summary-kill-same-subject}).
@item M C
@kindex M C (Summary)
@kindex M H (Summary)
@findex gnus-summary-catchup-to-here
Catchup the current group to point
-(@code{gnus-summary-catchup-to-here}).
+(@code{gnus-summary-catchup-to-here}).
@item C-w
@kindex C-w (Summary)
@findex gnus-summary-mark-region-as-read
Mark all articles between point and mark as read
-(@code{gnus-summary-mark-region-as-read}).
+(@code{gnus-summary-mark-region-as-read}).
@item M V k
@kindex M V k (Summary)
@kindex M P p (Summary)
@findex gnus-summary-mark-as-processable
Mark the current article with the process mark
-(@code{gnus-summary-mark-as-processable}).
+(@code{gnus-summary-mark-as-processable}).
@findex gnus-summary-unmark-as-processable
-@item M P u
+@item M P u
@itemx M-#
@kindex M P u (Summary)
@kindex M-# (Summary)
@kindex M P U (Summary)
@findex gnus-summary-unmark-all-processable
Remove the process mark from all articles
-(@code{gnus-summary-unmark-all-processable}).
+(@code{gnus-summary-unmark-all-processable}).
@item M P i
@kindex M P i (Summary)
@findex gnus-uu-invert-processable
Invert the list of process marked articles
-(@code{gnus-uu-invert-processable}).
+(@code{gnus-uu-invert-processable}).
@item M P R
@kindex M P R (Summary)
@findex gnus-uu-mark-by-regexp
-Mark articles by a regular expression (@code{gnus-uu-mark-by-regexp}).
+Mark articles that have a @code{Subject} header that matches a regular
+expression (@code{gnus-uu-mark-by-regexp}).
@item M P r
@kindex M P r (Summary)
@kindex M P b (Summary)
@findex gnus-uu-mark-buffer
Mark all articles in the buffer in the order they appear
-(@code{gnus-uu-mark-buffer}).
+(@code{gnus-uu-mark-buffer}).
@item M P k
@kindex M P k (Summary)
It can be convenient to limit the summary buffer to just show some
subset of the articles currently in the group. The effect most limit
commands have is to remove a few (or many) articles from the summary
-buffer.
+buffer.
All limiting commands work on subsets of the articles already fetched
from the servers. None of these commands query the server for
@kindex / / (Summary)
@findex gnus-summary-limit-to-subject
Limit the summary buffer to articles that match some subject
-(@code{gnus-summary-limit-to-subject}).
+(@code{gnus-summary-limit-to-subject}).
@item / a
@kindex / a (Summary)
@item / m
@kindex / m (Summary)
@findex gnus-summary-limit-to-marks
-Ask for a mark and then limit to all articles that have not been marked
+Ask for a mark and then limit to all articles that have been marked
with that mark (@code{gnus-summary-limit-to-marks}).
@item / t
@kindex M S (Summary)
@kindex / E (Summary)
@findex gnus-summary-limit-include-expunged
-Display all expunged articles
-(@code{gnus-summary-limit-include-expunged}).
+Include all expunged articles in the limit
+(@code{gnus-summary-limit-include-expunged}).
@item / D
@kindex / D (Summary)
@findex gnus-summary-limit-include-dormant
-Display all dormant articles (@code{gnus-summary-limit-include-dormant}).
+Include all dormant articles in the limit
+(@code{gnus-summary-limit-include-dormant}).
+
+@item / *
+@kindex / * (Summary)
+@findex gnus-summary-limit-include-cached
+Include all cached articles in the limit
+(@code{gnus-summary-limit-include-cached}).
@item / d
@kindex / d (Summary)
@findex gnus-summary-limit-exclude-dormant
-Hide all dormant articles (@code{gnus-summary-limit-exclude-dormant}).
+Exclude all dormant articles from the limit
+(@code{gnus-summary-limit-exclude-dormant}).
+
+@item / M
+@kindex / M (Summary)
+@findex gnus-summary-limit-exclude-marks
+Exclude all marked articles (@code{gnus-summary-limit-exclude-marks}).
@item / T
@kindex / T (Summary)
@findex gnus-summary-limit-include-thread
-Include all the articles in the current thread.
+Include all the articles in the current thread in the limit.
@item / c
@kindex / c (Summary)
@findex gnus-summary-limit-exclude-childless-dormant
-Hide all dormant articles that have no children
-(@code{gnus-summary-limit-exclude-childless-dormant}).
+Exclude all dormant articles that have no children from the limit
+(@code{gnus-summary-limit-exclude-childless-dormant}).
@item / C
@kindex / C (Summary)
Threading is done by looking at the @code{References} headers of the
articles. In a perfect world, this would be enough to build pretty
trees, but unfortunately, the @code{References} header is often broken
-or simply missing. Weird news propagration excarcerbates the problem,
+or simply missing. Weird news propagation excarcerbates the problem,
so one has to employ other heuristics to get pleasing results. A
plethora of approaches exists, as detailed in horrible detail in
-@pxref{Customizing Threading}.
+@pxref{Customizing Threading}.
First, a quick overview of the concepts:
@item loose threads
Threads often lose their roots due to article expiry, or due to the root
already having been read in a previous session, and not displayed in the
-summary buffer. We then typicall have many sub-threads that really
+summary buffer. We then typically have many sub-threads that really
belong to one thread, but are without connecting roots. These are
called loose threads.
@cindex fuzzy article gathering
If you set this variable to the special value @code{fuzzy}, Gnus will
use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
-Matching}).
+Matching}).
@item gnus-simplify-subject-fuzzy-regexp
@vindex gnus-simplify-subject-fuzzy-regexp
@c Written by Michael Ernst <mernst@cs.rice.edu>
@lisp
(setq gnus-simplify-ignored-prefixes
- (concat
+ (concat
"\\`\\[?\\("
- (mapconcat
+ (mapconcat
'identity
'("looking"
"wanted" "followup" "summary\\( of\\)?"
- "help" "query" "problem" "question"
+ "help" "query" "problem" "question"
"answer" "reference" "announce"
"How can I" "How to" "Comparison of"
;; ...
@end lisp
All words that match this regexp will be removed before comparing two
-subjects.
+subjects.
@item gnus-simplify-subject-functions
@vindex gnus-simplify-subject-functions
@samp{} and @samp{(none)}. To make the situation slightly better,
you can use the regexp @code{gnus-summary-gather-exclude-subject} to say
what subjects should be excluded from the gathering process.@*
-The default is @samp{^ *$\\|^(none)$}.
+The default is @samp{^ *$\\|^(none)$}.
@item gnus-summary-thread-gathering-function
@vindex gnus-summary-thread-gathering-function
This variable can also be set to @code{invisible}. This won't have any
visible effects, but is useful if you use the @kbd{A T} command a lot
-(@pxref{Finding the Parent}).
+(@pxref{Finding the Parent}).
@item gnus-build-sparse-threads
@vindex gnus-build-sparse-threads
@item gnus-parse-headers-hook
@vindex gnus-parse-headers-hook
-Hook run before parsing any headers. The default value is
-@code{(gnus-decode-rfc1522)}, which means that QPized headers will be
-slightly decoded in a hackish way. This is likely to change in the
-future when Gnus becomes @sc{MIME}ified.
+Hook run before parsing any headers.
@item gnus-alter-header-function
@vindex gnus-alter-header-function
@kindex M-C-l (Summary)
@findex gnus-summary-lower-thread
Lower the score of the current (sub-)thread
-(@code{gnus-summary-lower-thread}).
+(@code{gnus-summary-lower-thread}).
@item T i
@kindex T i (Summary)
Go to the top of the thread (@code{gnus-summary-top-thread}).
@end table
-@vindex gnus-thread-operation-ignore-subject
+@vindex gnus-thread-operation-ignore-subject
If you ignore subject while threading, you'll naturally end up with
threads that have several different subjects in them. If you then issue
a command like `T k' (@code{gnus-summary-kill-thread}) you might not
@findex gnus-thread-sort-by-number
@vindex gnus-thread-sort-functions
If you are using a threaded summary display, you can sort the threads by
-setting @code{gnus-thread-sort-functions}, which is a list of functions.
+setting @code{gnus-thread-sort-functions}, which can be either a single
+function, a list of functions, or a list containing functions and
+@code{(not some-function)} elements.
+
By default, sorting is done on article numbers. Ready-made sorting
predicate functions include @code{gnus-thread-sort-by-number},
@code{gnus-thread-sort-by-author}, @code{gnus-thread-sort-by-subject},
Each function takes two threads and returns non-@code{nil} if the first
thread should be sorted before the other. Note that sorting really is
-normally done by looking only at the roots of each thread. If you use
-more than one function, the primary sort key should be the last function
-in the list. You should probably always include
+normally done by looking only at the roots of each thread.
+
+If you use more than one function, the primary sort key should be the
+last function in the list. You should probably always include
@code{gnus-thread-sort-by-number} in the list of sorting
functions---preferably first. This will ensure that threads that are
equal with respect to the other sort criteria will be displayed in
ascending article order.
-If you would like to sort by score, then by subject, and finally by
-number, you could do something like:
+If you would like to sort by reverse score, then by subject, and finally
+by number, you could do something like:
@lisp
-(setq gnus-thread-sort-functions
+(setq gnus-thread-sort-functions
'(gnus-thread-sort-by-number
gnus-thread-sort-by-subject
- gnus-thread-sort-by-total-score))
+ (reverse gnus-thread-sort-by-total-score)))
@end lisp
The threads that have highest score will be displayed first in the
say something like:
@lisp
-(setq gnus-article-sort-functions
+(setq gnus-article-sort-functions
'(gnus-article-sort-by-number
gnus-article-sort-by-subject))
@end lisp
while you are reading the previous one? Why not, indeed.
First, some caveats. There are some pitfalls to using asynchronous
-article fetching, especially the way Gnus does it.
+article fetching, especially the way Gnus does it.
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
The default value is @code{(read exit)}.
-@vindex gnus-use-header-prefetch
-If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
-from the next group.
+@c @vindex gnus-use-header-prefetch
+@c If @code{gnus-use-header-prefetch} is non-@code{nil}, prefetch articles
+@c from the next group.
@node Article Caching
not then be downloaded by this command.
@vindex gnus-uncacheable-groups
-It is likely that you do not want caching on some groups. For instance,
+@vindex gnus-cacheable-groups
+It is likely that you do not want caching on all groups. For instance,
if your @code{nnml} mail is located under your home directory, it makes no
sense to cache it somewhere else under your home directory. Unless you
-feel that it's neat to use twice as much space. To limit the caching,
-you could set the @code{gnus-uncacheable-groups} regexp to
-@samp{^nnml}, for instance. This variable is @code{nil} by
-default.
+feel that it's neat to use twice as much space.
+
+To limit the caching, you could set @code{gnus-cacheable-groups} to a
+regexp of groups to cache, @samp{^nntp} for instance, or set the
+@code{gnus-uncacheable-groups} regexp to @samp{^nnml}, for instance.
+Both variables are @code{nil} by default. If a group matches both
+variables, the group is not cached.
@findex gnus-cache-generate-nov-databases
@findex gnus-cache-generate-active
@item *
@kindex * (Summary)
@findex gnus-cache-enter-article
-Make the current article persistent (@code{gnus-cache-enter-article}).
+Make the current article persistent (@code{gnus-cache-enter-article}).
@item M-*
@kindex M-* (Summary)
@findex gnus-cache-remove-article
Remove the current article from the persistent articles
(@code{gnus-cache-remove-article}). This will normally delete the
-article.
+article.
@end table
-Both these commands understand the process/prefix convention.
+Both these commands understand the process/prefix convention.
To avoid having all ticked articles (and stuff) entered into the cache,
you should set @code{gnus-use-cache} to @code{passive} if you're just
variable is non-@code{nil} and is not a number, Gnus will store
@emph{all} read articles, which means that your Emacs will grow without
bound before exploding and taking your machine down with you. I put
-that in there just to keep y'all on your toes.
+that in there just to keep y'all on your toes.
This variable is @code{nil} by default.
@findex gnus-summary-save-article
@c @icon{gnus-summary-save-article}
Save the current article using the default article saver
-(@code{gnus-summary-save-article}).
+(@code{gnus-summary-save-article}).
@item O m
@kindex O m (Summary)
@findex gnus-summary-save-article-mail
Save the current article in mail format
-(@code{gnus-summary-save-article-mail}).
+(@code{gnus-summary-save-article-mail}).
@item O r
@kindex O r (Summary)
@findex gnus-summary-save-article-rmail
Save the current article in rmail format
-(@code{gnus-summary-save-article-rmail}).
+(@code{gnus-summary-save-article-rmail}).
@item O f
@kindex O f (Summary)
@findex gnus-summary-save-article-file
@c @icon{gnus-summary-save-article-file}
Save the current article in plain file format
-(@code{gnus-summary-save-article-file}).
+(@code{gnus-summary-save-article-file}).
@item O F
@kindex O F (Summary)
@findex gnus-summary-write-article-file
Write the current article in plain file format, overwriting any previous
-file contents (@code{gnus-summary-write-article-file}).
+file contents (@code{gnus-summary-write-article-file}).
@item O b
@kindex O b (Summary)
@findex gnus-summary-save-article-body-file
Save the current article body in plain file format
-(@code{gnus-summary-save-article-body-file}).
+(@code{gnus-summary-save-article-body-file}).
@item O h
@kindex O h (Summary)
@findex gnus-summary-save-article-folder
Save the current article in mh folder format
-(@code{gnus-summary-save-article-folder}).
+(@code{gnus-summary-save-article-folder}).
@item O v
@kindex O v (Summary)
have Gnus do all your thinking for you, you can even set this variable
to @code{nil}, which means that you will never be prompted for files to
save articles in. Gnus will simply save all the articles in the default
-files.
+files.
@vindex gnus-default-article-saver
You can customize the @code{gnus-default-article-saver} variable to make
-Gnus do what you want it to. You can use any of the four ready-made
+Gnus do what you want it to. You can use any of the six ready-made
functions below, or you can create your own.
@table @code
All of these functions, except for the last one, will save the article
in the @code{gnus-article-save-directory}, which is initialized from the
@code{SAVEDIR} environment variable. This is @file{~/News/} by
-default.
+default.
As you can see above, the functions use different functions to find a
suitable name of a file to save the article in. Below is a list of
This variable is @code{((gnus-article-archive-name))} by default, which
means that Gnus will look at the articles it saves for an
@code{Archive-name} line and use that as a suggestion for the file
-name.
+name.
Here's an example function to clean up file names somewhat. If you have
lots of mail groups called things like
@code{nil}, all the preceding functions will replace all periods
(@samp{.}) in the group names with slashes (@samp{/})---which means that
the functions will generate hierarchies of directories instead of having
-all the files in the toplevel directory
+all the files in the top level directory
(@file{~/News/alt/andrea-dworkin} instead of
@file{~/News/alt.andrea-dworkin}.) This variable is @code{t} by default
on most systems. However, for historical reasons, this is @code{nil} on
Then just save with @kbd{o}. You'd then read this hierarchy with
ephemeral @code{nneething} groups---@kbd{G D} in the group buffer, and
-the toplevel directory as the argument (@file{~/News/}). Then just walk
+the top level directory as the argument (@file{~/News/}). Then just walk
around to the groups/directories with @code{nneething}.
Sometime users post articles (or series of articles) that have been
encoded in some way or other. Gnus can decode them for you.
-@menu
+@menu
* Uuencoded Articles:: Uudecode articles.
* Shell Archives:: Unshar articles.
* PostScript Files:: Split PostScript.
For example: If you choose a subject called @samp{cat.gif (2/3)}, Gnus
will find all the articles that match the regexp @samp{^cat.gif
-([0-9]+/[0-9]+).*$}.
+([0-9]+/[0-9]+).*$}.
Subjects that are non-standard, like @samp{cat.gif (2/3) Part 6 of a
series}, will not be properly recognized by any of the automatic viewing
@kindex X v S (Summary)
@findex gnus-uu-decode-unshar-and-save-view
Unshars, views and saves the current series
-(@code{gnus-uu-decode-unshar-and-save-view}).
+(@code{gnus-uu-decode-unshar-and-save-view}).
@end table
@kindex X v P (Summary)
@findex gnus-uu-decode-postscript-and-save-view
View and save the current PostScript series
-(@code{gnus-uu-decode-postscript-and-save-view}).
+(@code{gnus-uu-decode-postscript-and-save-view}).
@end table
Adjective, not verb.
-@menu
+@menu
* Rule Variables:: Variables that say how a file is to be viewed.
* Other Decode Variables:: Other decode variables.
* Uuencoding and Posting:: Variables for customizing uuencoding.
Gnus uses @dfn{rule variables} to decide how to view a file. All these
variables are of the form
-
+
@lisp
(list '(regexp1 command2)
'(regexp2 command2)
say something like:
@lisp
(setq gnus-uu-user-view-rules
- (list '(\"\\\\.au$\" \"sox %s -t .aiff > /dev/audio\")))
+ (list '("\\\\.au$" "sox %s -t .aiff > /dev/audio")))
@end lisp
@item gnus-uu-user-view-rules-end
immediately. If this variable is @code{not-confirm}, the user won't even
be asked for a confirmation before viewing is done.
-@vindex gnus-view-pseudos-separately
+@vindex gnus-view-pseudos-separately
If @code{gnus-view-pseudos-separately} is non-@code{nil}, one
pseudo-article will be created for each file to be viewed. If
@code{nil}, all files that use the same viewing command will be given as
@menu
* Article Highlighting:: You want to make the article look like fruit salad.
-* Article Fontisizing:: Making emphasized text look niced.
+* Article Fontisizing:: Making emphasized text look nice.
* Article Hiding:: You also want to make certain info go away.
* Article Washing:: Lots of way-neat functions to make life better.
* Article Buttons:: Click on URLs, Message-IDs, addresses and the like.
@node Article Highlighting
@subsection Article Highlighting
-@cindex highlight
+@cindex highlighting
Not only do you want your article buffer to look like fruit salad, but
you want it to look like technicolor fruit salad.
@item W H a
@kindex W H a (Summary)
@findex gnus-article-highlight
-Highlight the current article (@code{gnus-article-highlight}).
+@findex gnus-article-maybe-highlight
+Do much highlighting of the current article
+(@code{gnus-article-highlight}). This function highlights header, cited
+text, the signature, and adds buttons to the body and the head.
@item W H h
@kindex W H h (Summary)
@item W H c
@kindex W H c (Summary)
@findex gnus-article-highlight-citation
-Highlight cited text (@code{gnus-article-highlight-citation}).
+Highlight cited text (@code{gnus-article-highlight-citation}).
Some variables to customize the citation highlights:
@item gnus-cite-parse-max-size
If the article size if bigger than this variable (which is 25000 by
-default), no citation highlighting will be performed.
+default), no citation highlighting will be performed.
@item gnus-cite-prefix-regexp
@vindex gnus-cite-prefix-regexp
-Regexp matching the longest possible citation prefix on a line.
+Regexp matching the longest possible citation prefix on a line.
@item gnus-cite-max-prefix
@vindex gnus-cite-max-prefix
@item gnus-supercite-regexp
@vindex gnus-supercite-regexp
-Regexp matching normal Supercite attribution lines.
+Regexp matching normal Supercite attribution lines.
@item gnus-supercite-secondary-regexp
@vindex gnus-supercite-secondary-regexp
@end table
+@xref{Customizing Articles} for how to highlight articles automatically.
+
@node Article Fontisizing
@subsection Article Fontisizing
running the article through the @kbd{W e}
(@code{gnus-article-emphasize}) command.
-@vindex gnus-article-emphasis
+@vindex gnus-emphasis-alist
How the emphasis is computed is controlled by the
-@code{gnus-article-emphasis} variable. This is an alist where the first
+@code{gnus-emphasis-alist} variable. This is an alist where the first
element is a regular expression to be matched. The second is a number
that says what regular expression grouping is used to find the entire
emphasized word. The third is a number that says what regexp grouping
@code{gnus-emphasis-underline}, @code{gnus-emphasis-bold-italic},
@code{gnus-emphasis-underline-italic},
@code{gnus-emphasis-underline-bold}, and
-@code{gnus-emphasis-underline-bold-italic}.
+@code{gnus-emphasis-underline-bold-italic}.
If you want to change these faces, you can either use @kbd{M-x
customize}, or you can use @code{copy-face}. For instance, if you want
(copy-face 'red 'gnus-emphasis-italic)
@end lisp
+@xref{Customizing Articles} for how to fontize articles automatically.
+
@node Article Hiding
@subsection Article Hiding
@cindex article hiding
Or rather, hiding certain things in each article. There usually is much
-too much cruft in most articles.
+too much cruft in most articles.
@table @kbd
@item W W a
@kindex W W a (Summary)
@findex gnus-article-hide
-Do maximum hiding on the summary buffer (@kbd{gnus-article-hide}).
+Do quite a lot of hiding on the article buffer
+(@kbd{gnus-article-hide}). In particular, this function will hide
+headers, PGP, cited text and the signature.
@item W W h
@kindex W W h (Summary)
@findex gnus-article-hide-headers
Hide headers (@code{gnus-article-hide-headers}). @xref{Hiding
-Headers}.
+Headers}.
@item W W b
@kindex W W b (Summary)
@kindex W W s (Summary)
@findex gnus-article-hide-signature
Hide signature (@code{gnus-article-hide-signature}). @xref{Article
-Signature}.
+Signature}.
@item W W p
@kindex W W p (Summary)
@vindex gnus-article-hide-pgp-hook
Hide @sc{pgp} signatures (@code{gnus-article-hide-pgp}). The
@code{gnus-article-hide-pgp-hook} hook will be run after a @sc{pgp}
-signature has been hidden.
+signature has been hidden. For example, to automatically verify
+articles that have signatures in them do:
+@lisp
+;;; Hide pgp cruft if any.
+
+(setq gnus-treat-strip-pgp t)
+
+;;; After hiding pgp, verify the message;
+;;; only happens if pgp signature is found.
+
+(add-hook 'gnus-article-hide-pgp-hook
+ (lambda ()
+ (save-excursion
+ (set-buffer gnus-original-article-buffer)
+ (mc-verify))))
+@end lisp
@item W W P
@kindex W W P (Summary)
Hide @sc{pem} (privacy enhanced messages) cruft
(@code{gnus-article-hide-pem}).
+@item W W B
+@kindex W W B (Summary)
+@findex gnus-article-strip-banner
+Strip the banner specified by the @code{banner} group parameter
+(@code{gnus-article-strip-banner}). This is mainly used to hide those
+annoying banners and/or signatures that some mailing lists and moderated
+groups adds to all the messages. The way to use this function is to add
+the @code{banner} group parameter (@pxref{Group Parameters}) to the
+group you want banners stripped from. The parameter either be a string,
+which will be interpreted as a regulax expression matching text to be
+removed, or the symbol @code{signature}, meaning that the (last)
+signature should be removed.
+
@item W W c
@kindex W W c (Summary)
@findex gnus-article-hide-citation
@table @code
-@item gnus-cite-hide-percentage
-@vindex gnus-cite-hide-percentage
-If the cited text is of a bigger percentage than this variable (default
-50), hide the cited text.
-
-@item gnus-cite-hide-absolute
-@vindex gnus-cite-hide-absolute
-The cited text must have at least this length (default 10) before it
-is hidden.
-
-@item gnus-cited-text-button-line-format
-@vindex gnus-cited-text-button-line-format
+@item gnus-cited-opened-text-button-line-format
+@itemx gnus-cited-closed-text-button-line-format
+@vindex gnus-cited-closed-text-button-line-format
+@vindex gnus-cited-opened-text-button-line-format
Gnus adds buttons to show where the cited text has been hidden, and to
allow toggle hiding the text. The format of the variable is specified
-by this format-like variable (@pxref{Formatting Variables}). These
+by these format-like variable (@pxref{Formatting Variables}). These
specs are valid:
@table @samp
@item b
-Start point of the hidden text.
+Starting point of the hidden text.
@item e
-End point of the hidden text.
+Ending point of the hidden text.
@item l
-Length of the hidden text.
+Number of characters in the hidden region.
+@item n
+Number of lines of hidden text.
@end table
@item gnus-cited-lines-visible
@vindex gnus-cited-lines-visible
-The number of lines at the beginning of the cited text to leave shown.
+The number of lines at the beginning of the cited text to leave shown.
+
+@end table
+
+@item W W C-c
+@kindex W W C-c (Summary)
+@findex gnus-article-hide-citation-maybe
+Hide citation (@code{gnus-article-hide-citation-maybe}) depending on the
+following two variables:
+
+@table @code
+@item gnus-cite-hide-percentage
+@vindex gnus-cite-hide-percentage
+If the cited text is of a bigger percentage than this variable (default
+50), hide the cited text.
+
+@item gnus-cite-hide-absolute
+@vindex gnus-cite-hide-absolute
+The cited text must have at least this length (default 10) before it
+is hidden.
@end table
@item W W C
Hide cited text in articles that aren't roots
(@code{gnus-article-hide-citation-in-followups}). This isn't very
useful as an interactive command, but might be a handy function to stick
-in @code{gnus-article-display-hook} (@pxref{Customizing Articles}).
+have happen automatically (@pxref{Customizing Articles}).
@end table
Also @pxref{Article Highlighting} for further variables for
citation customization.
+@xref{Customizing Articles} for how to hide article elements
+automatically.
+
@node Article Washing
@subsection Article Washing
@kindex W l (Summary)
@findex gnus-summary-stop-page-breaking
Remove page breaks from the current article
-(@code{gnus-summary-stop-page-breaking}).
+(@code{gnus-summary-stop-page-breaking}). @xref{Misc Article} for page
+delimiters.
@item W r
@kindex W r (Summary)
@findex gnus-summary-caesar-message
@c @icon{gnus-summary-caesar-message}
Do a Caesar rotate (rot13) on the article buffer
-(@code{gnus-summary-caesar-message}).
+(@code{gnus-summary-caesar-message}).
Unreadable articles that tell you to read them with Caesar rotate or rot13.
(Typically offensive jokes and such.)
It's commonly called ``rot13'' because each letter is rotated 13
positions in the alphabet, e. g. @samp{B} (letter #2) -> @samp{O} (letter
#15). It is sometimes referred to as ``Caesar rotate'' because Caesar
-is rumoured to have employed this form of, uh, somewhat weak encryption.
+is rumored to have employed this form of, uh, somewhat weak encryption.
@item W t
@kindex W t (Summary)
@findex gnus-summary-toggle-header
Toggle whether to display all headers in the article buffer
-(@code{gnus-summary-toggle-header}).
+(@code{gnus-summary-toggle-header}).
@item W v
@kindex W v (Summary)
Toggle whether to display all headers in the article buffer permanently
(@code{gnus-summary-verbose-header}).
-@item W m
-@kindex W m (Summary)
-@findex gnus-summary-toggle-mime
-Toggle whether to run the article through @sc{mime} before displaying
-(@code{gnus-summary-toggle-mime}).
-
@item W o
@kindex W o (Summary)
@findex gnus-article-treat-overstrike
@item W d
@kindex W d (Summary)
@findex gnus-article-treat-dumbquotes
-Treat M******** sm*rtq**t*s (@code{gnus-article-treat-dumbquotes}).
+@vindex gnus-article-dumbquotes-map
+@cindex Smartquotes
+@cindex M******** sm*rtq**t*s
+@cindex Latin 1
+Treat M******** sm*rtq**t*s according to
+@code{gnus-article-dumbquotes-map}
+(@code{gnus-article-treat-dumbquotes}). Note that this function guesses
+whether a character is a sm*rtq**t* or not, so it should only be used
+interactively.
@item W w
@kindex W w (Summary)
@findex gnus-article-fill-cited-article
-Do word wrap (@code{gnus-article-fill-cited-article}). If you use this
-function in @code{gnus-article-display-hook}, it should be run fairly
-late and certainly after any highlighting.
+Do word wrap (@code{gnus-article-fill-cited-article}).
You can give the command a numerical prefix to specify the width to use
when filling.
+@item W q
+@kindex W q (Summary)
+@findex gnus-article-fill-long-lines
+Fill long lines (@code{gnus-article-fill-long-lines}).
+
+@item W C
+@kindex W C (Summary)
+@findex gnus-article-capitalize-sentencse
+Capitalize the first word in each sentence
+(@code{gnus-article-capitalize-sentences}).
+
@item W c
@kindex W c (Summary)
@findex gnus-article-remove-cr
-Remove CR (i. e., @samp{^M}s on the end of the lines)
+Translate CRLF pairs (i. e., @samp{^M}s on the end of the lines) into LF
+(this takes care of DOS line endings), and then translate any remaining
+CRs into LF (this takes care of Mac line endings)
(@code{gnus-article-remove-cr}).
@item W q
Quoted-Printable is one common @sc{mime} encoding employed when sending
non-ASCII (i. e., 8-bit) articles. It typically makes strings like
@samp{déjà vu} look like @samp{d=E9j=E0 vu}, which doesn't look very
-readable to me.
+readable to me. Note that the this is usually done automatically by
+Gnus if the message in question has a @code{Content-Transfer-Encoding}
+header that says that this encoding has been done.
@item W f
@kindex W f (Summary)
@kindex W b (Summary)
@findex gnus-article-add-buttons
Add clickable buttons to the article (@code{gnus-article-add-buttons}).
-@xref{Article Buttons}
+@xref{Article Buttons}.
@item W B
@kindex W B (Summary)
@findex gnus-article-add-buttons-to-head
Add clickable buttons to the article headers
-(@code{gnus-article-add-buttons-to-head}).
+(@code{gnus-article-add-buttons-to-head}).
@item W E l
@kindex W E l (Summary)
Remove all white space from the beginning of all lines of the article
body (@code{gnus-article-strip-leading-space}).
+@item W E e
+@kindex W E e (Summary)
+@findex gnus-article-strip-trailing-space
+Remove all white space from the end of all lines of the article
+body (@code{gnus-article-strip-trailing-space}).
+
@end table
+@xref{Customizing Articles} for how to wash articles automatically.
+
@node Article Buttons
@subsection Article Buttons
@item regexp
All text that match this regular expression will be considered an
external reference. Here's a typical regexp that matches embedded URLs:
-@samp{<URL:\\([^\n\r>]*\\)>}.
+@samp{<URL:\\([^\n\r>]*\\)>}.
@item button-par
Gnus has to know which parts of the matches is to be highlighted. This
@item data-par
As with @var{button-par}, this is a sub-expression number, but this one
-says which part of the match is to be sent as data to @var{function}.
+says which part of the match is to be sent as data to @var{function}.
@end table
@end table
+@xref{Customizing Articles} for how to buttonize articles automatically.
+
@node Article Date
@subsection Article Date
@kindex W T u (Summary)
@findex gnus-article-date-ut
Display the date in UT (aka. GMT, aka ZULU)
-(@code{gnus-article-date-ut}).
+(@code{gnus-article-date-ut}).
@item W T i
@kindex W T i (Summary)
@end table
+@xref{Customizing Articles} for how to display the date in your
+preferred format automatically.
+
@node Article Signature
@subsection Article Signature
(setq gnus-signature-separator
'("^-- $" ; The standard
"^-- *$" ; A common mangling
- "^-------*$" ; Many people just use a looong
+ "^-------*$" ; Many people just use a looong
; line of dashes. Shame!
"^ *--------*$" ; Double-shame!
"^________*$" ; Underscores are also popular
@vindex gnus-signature-limit
@code{gnus-signature-limit} provides a limit to what is considered a
-signature.
+signature.
@enumerate
-@item
+@item
If it is an integer, no signature may be longer (in characters) than
that integer.
-@item
+@item
If it is a floating point number, no signature may be longer (in lines)
than that number.
-@item
+@item
If it is a function, the function will be called without any parameters,
and if it returns @code{nil}, there is no signature in the buffer.
@item
signature after all.
+@node MIME Commands
+@section MIME Commands
+@cindex MIME decoding
+
+@table @kbd
+@item M-t
+@kindex M-t (Summary)
+@findex gnus-summary-display-buttonized
+Toggle the buttonized display of the article buffer
+(@code{gnus-summary-toggle-display-buttonized}).
+
+@item W M w
+@kindex W M w (Summary)
+Decode RFC2047-encoded words in the article headers
+(@code{gnus-article-decode-mime-words}).
+
+@item W M c
+@kindex W M c (Summary)
+Decode encoded article bodies as well as charsets
+(@code{gnus-article-decode-charset}).
+
+This command looks in the @code{Content-Type} header to determine the
+charset. If there is no such header in the article, you can give it a
+prefix, which will prompt for the charset to decode as. In regional
+groups where people post using some common encoding (but do not include
+MIME headers), you can set the @code{charset} group/topic parameter to
+the required charset (@pxref{Group Parameters}).
+
+@item W M v
+@kindex W M v (Summary)
+View all the @sc{mime} parts in the current article
+(@code{gnus-mime-view-all-parts}).
+
+@end table
+
+Relevant variables:
+
+@table @code
+@item gnus-ignored-mime-types
+@vindex gnus-ignored-mime-types
+This is a list of regexps. @sc{mime} types that match a regexp from
+this list will be completely ignored by Gnus. The default value is
+@code{nil}.
+
+To have all Vcards be ignored, you'd say something like this:
+
+@lisp
+(setq gnus-ignored-mime-types
+ '("text/x-vcard"))
+@end lisp
+
+@item gnus-unbuttonized-mime-types
+@vindex gnus-unbuttonized-mime-types
+This is a list of regexps. @sc{mime} types that match a regexp from
+this list won't have @sc{mime} buttons inserted unless they aren't
+displayed. The default value is @code{(".*/.*")}.
+
+@item gnus-article-mime-part-function
+@vindex gnus-article-mime-part-function
+For each @sc{mime} part, this function will be called with the @sc{mime}
+handle as the parameter. The function is meant to be used to allow
+users to gather information from the article (e. g., add Vcard info to
+the bbdb database) or to do actions based on parts (e. g., automatically
+save all jpegs into some directory).
+
+Here's an example function the does the latter:
+
+@lisp
+(defun my-save-all-jpeg-parts (handle)
+ (when (equal (car (mm-handle-type handle)) "image/jpeg")
+ (with-temp-buffer
+ (insert (mm-get-part handle))
+ (write-region (point-min) (point-max)
+ (read-file-name "Save jpeg to: ")))))
+(setq gnus-article-mime-part-function
+ 'my-save-all-jpeg-parts)
+@end lisp
+
+@end table
+
+
+@node Charsets
+@section Charsets
+@cindex charsets
+
+People use different charsets, and we have @sc{mime} to let us know what
+charsets they use. Or rather, we wish we had. Many people use
+newsreaders and mailers that do not understand or use @sc{mime}, and
+just send out messages without saying what character sets they use. To
+help a bit with this, some local news hierarchies have policies that say
+what character set is the default. For instance, the @samp{fj}
+hierarchy uses @code{iso-2022-jp-2}.
+
+@vindex gnus-group-charset-alist
+This knowledge is encoded in the @code{gnus-group-charset-alist}
+variable, which is an alist of regexps (to match group names) and
+default charsets to be used when reading these groups.
+
+In addition, some people do use soi-disant @sc{mime}-aware agents that
+aren't. These blitely mark messages as being in @code{iso-8859-1} even
+if they really are in @code{koi-8}. To help here, the
+@code{gnus-newsgroup-ignored-charsets} variable can be used. The
+charsets that are listed here will be ignored. The variable can be set
+on a group-by-group basis using the group parameters (@pxref{Group
+Parameters}). The default value is @code{(unknown-8bit)}, which is
+something some agents insist on having in there.
+
+
@node Article Commands
@section Article Commands
@cindex printing
@kindex A P (Summary)
@vindex gnus-ps-print-hook
-@findex gnus-summary-print-article
+@findex gnus-summary-print-article
Generate and print a PostScript image of the article buffer
(@code{gnus-summary-print-article}). @code{gnus-ps-print-hook} will be
run just before printing the buffer.
ancestor. So if you say @kbd{3 ^}, Gnus will fetch the parent, the
grandparent and the grandgrandparent of the current article. If you say
@kbd{-3 ^}, Gnus will only fetch the grandgrandparent of the current
-article.
+article.
@item A R (Summary)
@findex gnus-summary-refer-references
@table @kbd
@item .
@kindex . (Pick)
-@findex gnus-summary-mark-as-processable
-Pick the article on the current line
-(@code{gnus-summary-mark-as-processable}). If given a numerical prefix,
-go to that article and pick it. (The line number is normally displayed
+@findex gnus-pick-article-or-thread
+Pick the article or thread on the current line
+(@code{gnus-pick-article-or-thread}). If the variable
+@code{gnus-thread-hide-subtree} is true, then this key selects the
+entire thread when used at the first article of the thread. Otherwise,
+it selects just the article. If given a numerical prefix, go to that
+thread or article and pick it. (The line number is normally displayed
at the beginning of the summary pick lines.)
@item SPACE
@item u
@kindex u (Pick)
-@findex gnus-summary-unmark-as-processable
-Unpick the article (@code{gnus-summary-unmark-as-processable}).
-
-@item U
-@kindex U (Pick)
-@findex gnus-summary-unmark-all-processable
-Unpick all articles (@code{gnus-summary-unmark-all-processable}).
-
-@item t
-@kindex t (Pick)
-@findex gnus-uu-mark-thread
-Pick the thread (@code{gnus-uu-mark-thread}).
-
-@item T
-@kindex T (Pick)
-@findex gnus-uu-unmark-thread
-Unpick the thread (@code{gnus-uu-unmark-thread}).
-
-@item r
-@kindex r (Pick)
-@findex gnus-uu-mark-region
-Pick the region (@code{gnus-uu-mark-region}).
-
-@item R
-@kindex R (Pick)
-@findex gnus-uu-unmark-region
-Unpick the region (@code{gnus-uu-unmark-region}).
-
-@item e
-@kindex e (Pick)
-@findex gnus-uu-mark-by-regexp
-Pick articles that match a regexp (@code{gnus-uu-mark-by-regexp}).
-
-@item E
-@kindex E (Pick)
-@findex gnus-uu-unmark-by-regexp
-Unpick articles that match a regexp (@code{gnus-uu-unmark-by-regexp}).
-
-@item b
-@kindex b (Pick)
-@findex gnus-uu-mark-buffer
-Pick the buffer (@code{gnus-uu-mark-buffer}).
-
-@item B
-@kindex B (Pick)
-@findex gnus-uu-unmark-buffer
-Unpick the buffer (@code{gnus-uu-unmark-buffer}).
+@findex gnus-pick-unmark-article-or-thread.
+Unpick the thread or article
+(@code{gnus-pick-unmark-article-or-thread}). If the variable
+@code{gnus-thread-hide-subtree} is true, then this key unpicks the
+thread if used at the first article of the thread. Otherwise it unpicks
+just the article. You can give this key a numerical prefix to unpick
+the thread or article at that line.
@item RET
@kindex RET (Pick)
@end table
+All the normal summary mode commands are still available in the
+pick-mode, with the exception of @kbd{u}. However @kbd{!} is available
+which is mapped to the same function
+@code{gnus-summary-tick-article-forward}.
+
If this sounds like a good idea to you, you could say:
@lisp
displayed. The pick mode line format is controlled by the
@code{gnus-summary-pick-line-format} variable (@pxref{Formatting
Variables}). It accepts the same format specs that
-@code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
+@code{gnus-summary-line-format} does (@pxref{Summary Buffer Lines}).
@node Binary Groups
@kbd{X u}, @kbd{n}, @kbd{RET} all the time. @kbd{M-x gnus-binary-mode}
is a minor mode for summary buffers that makes all ordinary Gnus article
selection functions uudecode series of articles and display the result
-instead of just displaying the articles the normal way.
+instead of just displaying the articles the normal way.
@kindex g (Binary)
@findex gnus-binary-show-article
If you don't like the normal Gnus summary display, you might try setting
@code{gnus-use-trees} to @code{t}. This will create (by default) an
additional @dfn{tree buffer}. You can execute all summary mode commands
-in the tree buffer.
+in the tree buffer.
There are a few variables to customize the tree display, of course:
@item gnus-tree-mode-line-format
@vindex gnus-tree-mode-line-format
-A format string for the mode bar in the tree mode buffers. The default
-is @samp{Gnus: %%b %S %Z}. For a list of valid specs, @pxref{Summary
-Buffer Mode Line}.
+A format string for the mode bar in the tree mode buffers (@pxref{Mode
+Line Formatting}). The default is @samp{Gnus: %%b %S %Z}. For a list
+of valid specs, @pxref{Summary Buffer Mode Line}.
@item gnus-selected-tree-face
@vindex gnus-selected-tree-face
The number of the article.
@item [
The opening bracket.
-@item ]
+@item ]
The closing bracket.
@item s
The subject.
@item gnus-tree-parent-child-edges
@vindex gnus-tree-parent-child-edges
This is a list that contains the characters used for connecting parent
-nodes to their children. The default is @code{(?- ?\\ ?|)}.
+nodes to their children. The default is @code{(?- ?\\ ?|)}.
@end table
@cindex move mail
@findex gnus-summary-move-article
Move the article from one mail group to another
-(@code{gnus-summary-move-article}).
+(@code{gnus-summary-move-article}).
@item B c
@kindex B c (Summary)
@item B r
@kindex B r (Summary)
@findex gnus-summary-respool-article
-Respool the mail article (@code{gnus-summary-move-article}).
+Respool the mail article (@code{gnus-summary-respool-article}).
@code{gnus-summary-respool-default-method} will be used as the default
select method when respooling. This variable is @code{nil} by default,
which means that the current group select method will be used instead.
@findex gnus-summary-respool-query
If you want to re-spool an article, you might be curious as to what group
the article will end up in before you do the re-spooling. This command
-will tell you (@code{gnus-summary-respool-query}).
+will tell you (@code{gnus-summary-respool-query}).
+
+@item B t
+@kindex B t (Summary)
+@findex gnus-summary-respool-trace
+Similarly, this command will display all fancy splitting patterns used
+when repooling, if any (@code{gnus-summary-respool-trace}).
@item B p
@kindex B p (Summary)
it to, for instance, highlight lines or modify the look of the buffer in
some other ungodly manner. I don't care.
+@vindex gnus-summary-prepared-hook
+@item gnus-summary-prepared-hook
+A hook called as the very last thing after the summary buffer has been
+generated.
+
@vindex gnus-summary-ignore-duplicates
@item gnus-summary-ignore-duplicates
When Gnus discovers two articles that have the same @code{Message-ID},
@kindex M-s (Summary)
@findex gnus-summary-search-article-forward
Search through all subsequent articles for a regexp
-(@code{gnus-summary-search-article-forward}).
+(@code{gnus-summary-search-article-forward}).
@item M-r
@kindex M-r (Summary)
@findex gnus-summary-search-article-backward
Search through all previous articles for a regexp
-(@code{gnus-summary-search-article-backward}).
+(@code{gnus-summary-search-article-backward}).
@item &
@kindex & (Summary)
@findex gnus-summary-prepare
Regenerate the current summary buffer (@code{gnus-summary-prepare}).
-@item Y c
+@item Y c
@kindex Y c (Summary)
@findex gnus-summary-insert-cached-articles
Pull all cached articles (for the current group) into the summary buffer
@code{nndoc} groups for each document, and then opening an
@code{nnvirtual} group on top of these @code{nndoc} groups. This
command understands the process/prefix convention
-(@pxref{Process/Prefix}).
+(@pxref{Process/Prefix}).
@item C-t
@kindex C-t (Summary)
@kindex = (Summary)
@findex gnus-summary-expand-window
Expand the summary buffer window (@code{gnus-summary-expand-window}).
-If given a prefix, force an @code{article} window configuration.
+If given a prefix, force an @code{article} window configuration.
@item M-C-e
@kindex M-C-e (Summary)
Edit the group parameters (@pxref{Group Parameters}) of the current
group (@code{gnus-summary-edit-parameters}).
+@item M-C-g
+@kindex M-C-g (Summary)
+@findex gnus-summary-customize-parameters
+Customize the group parameters (@pxref{Group Parameters}) of the current
+group (@code{gnus-summary-customize-parameters}).
+
@end table
@cindex exiting groups
Exiting from the summary buffer will normally update all info on the
-group and return you to the group buffer.
+group and return you to the group buffer.
@table @kbd
@kindex Z n (Summary)
@findex gnus-summary-catchup-and-goto-next-group
Mark all articles as read and go to the next group
-(@code{gnus-summary-catchup-and-goto-next-group}).
+(@code{gnus-summary-catchup-and-goto-next-group}).
@item Z R
@kindex Z R (Summary)
@kindex Z N (Summary)
@findex gnus-summary-next-group
Exit the group and go to the next group
-(@code{gnus-summary-next-group}).
+(@code{gnus-summary-next-group}).
@item Z P
@kindex Z P (Summary)
@findex gnus-summary-prev-group
Exit the group and go to the previous group
-(@code{gnus-summary-prev-group}).
+(@code{gnus-summary-prev-group}).
@item Z s
@kindex Z s (Summary)
@vindex gnus-exit-group-hook
@code{gnus-exit-group-hook} is called when you exit the current
-group.
+group.
@findex gnus-summary-wake-up-the-dead
@findex gnus-dead-summary-mode
called @code{gnus-dead-summary-mode}. Now, if you switch back to this
buffer, you'll find that all keys are mapped to a function called
@code{gnus-summary-wake-up-the-dead}. So tapping any keys in a dead
-summary buffer will result in a live, normal summary buffer.
+summary buffer will result in a live, normal summary buffer.
-There will never be more than one dead summary buffer at any one time.
+There will never be more than one dead summary buffer at any one time.
@vindex gnus-use-cross-reference
The data on the current group will be updated (which articles you have
several groups (not cross-posting) is called @dfn{spamming}, and you are
by law required to send nasty-grams to anyone who perpetrates such a
heinous crime. You may want to try NoCeM handling to filter out spam
-(@pxref{NoCeM}).
+(@pxref{NoCeM}).
Remember: Cross-posting is kinda ok, but posting the same article
separately to several groups is not. Massive cross-posting (aka.
article more than once by utilizing the crossposting mechanism
(@pxref{Crosspost Handling}). However, that simple and efficient
approach may not work satisfactory for some users for various
-reasons.
+reasons.
@enumerate
-@item
+@item
The @sc{nntp} server may fail to generate the @code{Xref} header. This
is evil and not very common.
-@item
+@item
The @sc{nntp} server may fail to include the @code{Xref} header in the
@file{.overview} data bases. This is evil and all too common, alas.
@item gnus-duplicate-list-length
@vindex gnus-duplicate-list-length
This variable says how many @code{Message-ID}s to keep in the duplicate
-suppression list. The default is 10000.
+suppression list. The default is 10000.
@item gnus-duplicate-file
@vindex gnus-duplicate-file
variable, will be displayed in random order after all the headers listed in this variable.
@findex gnus-article-hide-boring-headers
-@vindex gnus-article-display-hook
@vindex gnus-boring-article-headers
-You can hide further boring headers by entering
-@code{gnus-article-hide-boring-headers} into
-@code{gnus-article-display-hook}. What this function does depends on
-the @code{gnus-boring-article-headers} variable. It's a list, but this
-list doesn't actually contain header names. Instead is lists various
-@dfn{boring conditions} that Gnus can check and remove from sight.
+You can hide further boring headers by setting
+@code{gnus-treat-hide-boring-header} to @code{head}. What this function
+does depends on the @code{gnus-boring-article-headers} variable. It's a
+list, but this list doesn't actually contain header names. Instead is
+lists various @dfn{boring conditions} that Gnus can check and remove
+from sight.
These conditions are:
@table @code
@item empty
Remove all empty headers.
-@item newsgroups
-Remove the @code{Newsgroups} header if it only contains the current group
-name.
@item followup-to
Remove the @code{Followup-To} header if it is identical to the
@code{Newsgroups} header.
@item reply-to
Remove the @code{Reply-To} header if it lists the same address as the
@code{From} header.
+@item newsgroups
+Remove the @code{Newsgroups} header if it only contains the current group
+name.
@item date
Remove the @code{Date} header if the article is less than three days
old.
Remove all @code{To} headers if there are more than one.
@end table
-To include the four first elements, you could say something like;
+To include the four three elements, you could say something like;
@lisp
-(setq gnus-boring-article-headers
- '(empty newsgroups followup-to reply-to))
+(setq gnus-boring-article-headers
+ '(empty followup-to reply-to))
@end lisp
This is also the default value for this variable.
of the characters, and it also makes it possible to embed pictures and
other naughty stuff in innocent-looking articles.
-@vindex gnus-show-mime
-@vindex gnus-show-mime-method
-@vindex gnus-strict-mime
-@findex metamail-buffer
-Gnus handles @sc{mime} by pushing the articles through
-@code{gnus-show-mime-method}, which is @code{metamail-buffer} by
-default. This function calls the external @code{metamail} program to
-actually do the work. One common problem with this program is that is
-thinks that it can't display 8-bit things in the Emacs buffer. To tell
-it the truth, put something like the following in your
-@file{.bash_profile} file. (You do use @code{bash}, don't you?)
+@vindex gnus-display-mime-function
+@findex gnus-display-mime
+Gnus pushes @sc{mime} articles through @code{gnus-display-mime-function}
+to display the @sc{mime} parts. This is @code{gnus-display-mime} by
+default, which creates a bundle of clickable buttons that can be used to
+display, save and manipulate the @sc{mime} objects.
-@example
-export MM_CHARSET="iso-8859-1"
-@end example
+The following commands are available when you have placed point over a
+@sc{mime} button:
-For more information on @code{metamail}, see its manual page.
+@table @kbd
+@findex gnus-article-press-button
+@item RET (Article)
+@itemx BUTTON-2 (Article)
+Toggle displaying of the @sc{mime} object
+(@code{gnus-article-press-button}).
+
+@findex gnus-mime-view-part
+@item M-RET (Article)
+@itemx v (Article)
+Prompt for a method, and then view the @sc{mime} object using this
+method (@code{gnus-mime-view-part}).
+
+@findex gnus-mime-save-part
+@item o (Article)
+Prompt for a file name, and then save the @sc{mime} object
+(@code{gnus-mime-save-part}).
+
+@findex gnus-mime-copy-part
+@item c (Article)
+Copy the @sc{mime} object to a fresh buffer and display this buffer
+(@code{gnus-mime-copy-part}).
+
+@findex gnus-mime-pipe-part
+@item | (Article)
+Output the @sc{mime} object to a process (@code{gnus-mime-pipe-part}).
+@end table
-Set @code{gnus-show-mime} to @code{t} if you want to use
-@sc{mime} all the time. However, if @code{gnus-strict-mime} is
-non-@code{nil}, the @sc{mime} method will only be used if there are
-@sc{mime} headers in the article. If you have @code{gnus-show-mime}
-set, then you'll see some unfortunate display glitches in the article
-buffer. These can't be avoided.
+Gnus will display some @sc{mime} objects automatically. The way Gnus
+determines which parts to do this with is described in the Emacs MIME
+manual.
-It might be best to just use the toggling functions from the summary
-buffer to avoid getting nasty surprises. (For instance, you enter the
+It might be best to just use the toggling functions from the article
+buffer to avoid getting nasty surprises. (For instance, you enter the
group @samp{alt.sing-a-long} and, before you know it, @sc{mime} has
decoded the sound file in the article and some horrible sing-a-long song
-comes screaming out your speakers, and you can't find the volume
-button, because there isn't one, and people are starting to look at you,
-and you try to stop the program, but you can't, and you can't find the
-program to control the volume, and everybody else in the room suddenly
-decides to look at you disdainfully, and you'll feel rather stupid.)
+comes screaming out your speakers, and you can't find the volume button,
+because there isn't one, and people are starting to look at you, and you
+try to stop the program, but you can't, and you can't find the program
+to control the volume, and everybody else in the room suddenly decides
+to look at you disdainfully, and you'll feel rather stupid.)
Any similarity to real events and people is purely coincidental. Ahem.
@section Customizing Articles
@cindex article customization
-@vindex gnus-article-display-hook
-The @code{gnus-article-display-hook} is called after the article has
-been inserted into the article buffer. It is meant to handle all
-treatment of the article before it is displayed.
+A slew of functions for customizing how the articles are to look like
+exist. You can call these functions interactively, or you can have them
+called automatically when you select the articles.
-@findex gnus-article-maybe-highlight
-By default this hook just contains @code{gnus-article-hide-headers},
-@code{gnus-article-treat-overstrike}, and
-@code{gnus-article-maybe-highlight}, but there are thousands, nay
-millions, of functions you can put in this hook. For an overview of
-functions @pxref{Article Highlighting}, @pxref{Article Hiding},
-@pxref{Article Washing}, @pxref{Article Buttons} and @pxref{Article
-Date}. Note that the order of functions in this hook might affect
-things, so you may have to fiddle a bit to get the desired results.
-
-You can, of course, write your own functions. The functions are called
-from the article buffer, and you can do anything you like, pretty much.
-There is no information that you have to keep in the buffer---you can
-change everything. However, you shouldn't delete any headers. Instead
-make them invisible if you want to make them go away.
+To have them called automatically, you should set the corresponding
+``treatment'' variable. For instance, to have headers hidden, you'd set
+@code{gnus-treat-hide-headers}. Below is a list of variables that can
+be set, but first we discuss the values these variables can have.
+
+@enumerate
+@item
+@code{nil}: Don't do this treatment.
+
+@item
+@code{t}: Do this treatment on all body parts.
+
+@item
+@code{head}: Do the treatment on the headers.
+
+@item
+@code{last}: Do this treatment on the last part.
+
+@item
+An integer: Do this treatment on all body parts that have a length less
+than this number.
+
+@item
+A list:
+
+The list is evaluated recursively. The first element of the list is a
+predicate. The following predicates are recognized: @code{or},
+@code{and}, @code{not} and @code{typep}. Here's an example:
+
+@lisp
+(or last
+ (typep "text/x-vcard"))
+@end lisp
+
+@end enumerate
+
+You may have noticed that the word @dfn{part} is used here. This refers
+to the fact that some messages are @sc{mime} multipart articles that may
+be divided into several parts. Articles that are not multiparts are
+considered to contain just a single part.
+
+@vindex gnus-article-treat-types
+Are the treatments applied to all sorts of multipart parts? Yes, if you
+want to, but by default, only @samp{text/plain} parts are given the
+treatment. This is controlled by the @code{gnus-article-treat-types}
+variable, which is a list of regular expressions that are matched to the
+type of the part. This variable is ignored if the value of the
+controlling variable is a predicate list, as described above.
+
+The following treatment options are available. The easiest way to
+customize this is to examine the @code{gnus-article-treat} customization
+group.
+
+@table @code
+@item gnus-treat-highlight-signature
+@item gnus-treat-buttonize
+@item gnus-treat-buttonize-head
+@item gnus-treat-emphasize
+@item gnus-treat-fill-article
+@item gnus-treat-strip-cr
+@item gnus-treat-hide-headers
+@item gnus-treat-hide-boring-headers
+@item gnus-treat-hide-signature
+@item gnus-treat-hide-citation
+@item gnus-treat-strip-pgp
+@item gnus-treat-strip-pem
+@item gnus-treat-highlight-headers
+@item gnus-treat-highlight-citation
+@item gnus-treat-highlight-signature
+@item gnus-treat-date-ut
+@item gnus-treat-date-local
+@item gnus-treat-date-lapsed
+@item gnus-treat-date-original
+@item gnus-treat-strip-trailing-blank-lines
+@item gnus-treat-strip-leading-blank-lines
+@item gnus-treat-strip-multiple-blank-lines
+@item gnus-treat-strip-blank-lines
+@item gnus-treat-overstrike
+@item gnus-treat-display-xface
+@item gnus-treat-display-smileys
+@item gnus-treat-display-picons
+@end table
+
+@vindex gnus-part-display-hook
+You can, of course, write your own functions to be called from
+@code{gnus-part-display-hook}. The functions are called narrowed to the
+part, and you can do anything you like, pretty much. There is no
+information that you have to keep in the buffer---you can change
+everything. However, you shouldn't delete any headers. Instead make
+them invisible if you want to make them go away.
@node Article Keymap
@kindex C-c ^ (Article)
@findex gnus-article-refer-article
If point is in the neighborhood of a @code{Message-ID} and you press
-@kbd{r}, Gnus will try to get that article from the server
+@kbd{C-c ^}, Gnus will try to get that article from the server
(@code{gnus-article-refer-article}).
@item C-c C-m
@kindex ? (Article)
@findex gnus-article-describe-briefly
Give a very brief description of the available keystrokes
-(@code{gnus-article-describe-briefly}).
+(@code{gnus-article-describe-briefly}).
@item TAB
@kindex TAB (Article)
@item M-TAB
@kindex M-TAB (Article)
@findex gnus-article-prev-button
-Go to the previous button, if any (@code{gnus-article-prev-button}).
+Go to the previous button, if any (@code{gnus-article-prev-button}).
@end table
(This is the default.) If @code{nil}, each group will have its own
article buffer.
+@vindex gnus-article-decode-hook
+@item gnus-article-decode-hook
+@cindex MIME
+Hook used to decode @sc{mime} articles. The default value is
+@code{(article-decode-charset article-decode-encoded-words)}
+
@vindex gnus-article-prepare-hook
@item gnus-article-prepare-hook
This hook is called right after the article has been inserted into the
depending on the contents; it should probably not be used for changing
the contents of the article buffer.
-@vindex gnus-article-display-hook
-@item gnus-article-display-hook
-This hook is called as the last thing when displaying an article, and is
-intended for modifying the contents of the buffer, doing highlights,
-hiding headers, and the like.
-
@item gnus-article-mode-hook
@vindex gnus-article-mode-hook
Hook called in article mode buffers.
@item gnus-article-mode-syntax-table
@vindex gnus-article-mode-syntax-table
Syntax table used in article buffers. It is initialized from
-@code{text-mode-syntax-table}.
+@code{text-mode-syntax-table}.
@vindex gnus-article-mode-line-format
@item gnus-article-mode-line-format
This variable is a format string along the same lines as
-@code{gnus-summary-mode-line-format}. It accepts the same
-format specifications as that variable, with one extension:
+@code{gnus-summary-mode-line-format} (@pxref{Mode Line Formatting}). It
+accepts the same format specifications as that variable, with one
+extension:
@table @samp
@item w
The @dfn{wash status} of the article. This is a short string with one
character for each possible article wash operation that may have been
-performed.
+performed.
+@item m
+The number of @sc{mime} parts in the article.
@end table
@vindex gnus-break-pages
article using the foreign server, you can give a prefix to @kbd{C-c C-c}
to make Gnus try to post using the foreign server.
-@menu
+@menu
* Mail:: Mailing and replying.
* Post:: Posting and following up.
* Posting Server:: What server should you post via?
* Mail and Post:: Mailing and posting at the same time.
* Archived Messages:: Where Gnus stores the messages you've sent.
+* Posting Styles:: An easier way to specify who you are.
* Drafts:: Postponing messages and rejected messages.
* Rejected Articles:: What happens if the server doesn't like your article?
@end menu
the ``current'' server for posting.
If you give a zero prefix (i.e., @kbd{C-u 0 C-c C-c}) to that command,
-Gnus will prompt you for what method to use for posting.
+Gnus will prompt you for what method to use for posting.
You can also set @code{gnus-post-method} to a list of select methods.
If that's the case, Gnus will always prompt you for what method to use
-for posting.
+for posting.
+
+Finally, if you want to always post using the same select method as
+you're reading from (which might be convenient if you're reading lots of
+groups from different private servers), you can set this variable to
+@code{current}.
@node Mail and Post
@cindex ispell
@findex ispell-message
@lisp
-(add-hook 'message-send-hook 'ispell-message)
+(add-hook 'message-send-hook 'ispell-message)
@end lisp
@lisp
(setq gnus-message-archive-method
- '(nnfolder "archive"
+ '(nnfolder "archive"
(nnfolder-inhibit-expiry t)
(nnfolder-active-file "~/News/sent-mail/active")
(nnfolder-directory "~/News/sent-mail/")))
@cindex Gcc
Gnus will insert @code{Gcc} headers in all outgoing messages that point
to one or more group(s) on that server. Which group to use is
-determined by the @code{gnus-message-archive-group} variable.
+determined by the @code{gnus-message-archive-group} variable.
This variable can be used to do the following:
Save to different groups based on what group you are in:
@lisp
-(setq gnus-message-archive-group
+(setq gnus-message-archive-group
'(("^alt" "sent-to-alt")
("mail" "sent-to-mail")
(".*" "sent-to-misc")))
More complex stuff:
@lisp
-(setq gnus-message-archive-group
+(setq gnus-message-archive-group
'((if (message-news-p)
- "misc-news"
+ "misc-news"
"misc-mail")))
-@end lisp
+@end lisp
How about storing all news messages in one file, but storing all mail
messages in one file per month:
@lisp
(setq gnus-message-archive-group
'((if (message-news-p)
- "misc-news"
- (concat "mail." (format-time-string
+ "misc-news"
+ (concat "mail." (format-time-string
"%Y-%m" (current-time))))))
@end lisp
this will disable archiving.
@table @code
-@item gnus-outgoing-message-group
-@vindex gnus-outgoing-message-group
+@item gnus-outgoing-message-group
+@vindex gnus-outgoing-message-group
All outgoing messages will be put in this group. If you want to store
all your outgoing mail and articles in the group @samp{nnml:archive},
you set this variable to that value. This variable can also be a list of
@end table
-@c @node Posting Styles
-@c @section Posting Styles
-@c @cindex posting styles
-@c @cindex styles
-@c
-@c All them variables, they make my head swim.
-@c
-@c So what if you want a different @code{Organization} and signature based
-@c on what groups you post to? And you post both from your home machine
-@c and your work machine, and you want different @code{From} lines, and so
-@c on?
-@c
-@c @vindex gnus-posting-styles
-@c One way to do stuff like that is to write clever hooks that change the
-@c variables you need to have changed. That's a bit boring, so somebody
-@c came up with the bright idea of letting the user specify these things in
-@c a handy alist. Here's an example of a @code{gnus-posting-styles}
-@c variable:
-@c
-@c @lisp
-@c ((".*"
-@c (signature . "Peace and happiness")
-@c (organization . "What me?"))
-@c ("^comp"
-@c (signature . "Death to everybody"))
-@c ("comp.emacs.i-love-it"
-@c (organization . "Emacs is it")))
-@c @end lisp
-@c
-@c As you might surmise from this example, this alist consists of several
-@c @dfn{styles}. Each style will be applicable if the first element
-@c ``matches'', in some form or other. The entire alist will be iterated
-@c over, from the beginning towards the end, and each match will be
-@c applied, which means that attributes in later styles that match override
-@c the same attributes in earlier matching styles. So
-@c @samp{comp.programming.literate} will have the @samp{Death to everybody}
-@c signature and the @samp{What me?} @code{Organization} header.
-@c
-@c The first element in each style is called the @code{match}. If it's a
-@c string, then Gnus will try to regexp match it against the group name.
-@c If it's a function symbol, that function will be called with no
-@c arguments. If it's a variable symbol, then the variable will be
-@c referenced. If it's a list, then that list will be @code{eval}ed. In
-@c any case, if this returns a non-@code{nil} value, then the style is said
-@c to @dfn{match}.
-@c
-@c Each style may contain a arbitrary amount of @dfn{attributes}. Each
-@c attribute consists of a @var{(name . value)} pair. The attribute name
-@c can be one of @code{signature}, @code{organization} or @code{from}. The
-@c attribute name can also be a string. In that case, this will be used as
-@c a header name, and the value will be inserted in the headers of the
-@c article.
-@c
-@c The attribute value can be a string (used verbatim), a function (the
-@c return value will be used), a variable (its value will be used) or a
-@c list (it will be @code{eval}ed and the return value will be used).
-@c
-@c So here's a new example:
-@c
-@c @lisp
-@c (setq gnus-posting-styles
-@c '((".*"
-@c (signature . "~/.signature")
-@c (from . "user@@foo (user)")
-@c ("X-Home-Page" . (getenv "WWW_HOME"))
-@c (organization . "People's Front Against MWM"))
-@c ("^rec.humor"
-@c (signature . my-funny-signature-randomizer))
-@c ((equal (system-name) "gnarly")
-@c (signature . my-quote-randomizer))
-@c (posting-from-work-p
-@c (signature . "~/.work-signature")
-@c (from . "user@@bar.foo (user)")
-@c (organization . "Important Work, Inc"))
-@c ("^nn.+:"
-@c (signature . "~/.mail-signature"))))
-@c @end lisp
+@node Posting Styles
+@section Posting Styles
+@cindex posting styles
+@cindex styles
+
+All them variables, they make my head swim.
+
+So what if you want a different @code{Organization} and signature based
+on what groups you post to? And you post both from your home machine
+and your work machine, and you want different @code{From} lines, and so
+on?
+
+@vindex gnus-posting-styles
+One way to do stuff like that is to write clever hooks that change the
+variables you need to have changed. That's a bit boring, so somebody
+came up with the bright idea of letting the user specify these things in
+a handy alist. Here's an example of a @code{gnus-posting-styles}
+variable:
+
+@lisp
+((".*"
+ (signature "Peace and happiness")
+ (organization "What me?"))
+ ("^comp"
+ (signature "Death to everybody"))
+ ("comp.emacs.i-love-it"
+ (organization "Emacs is it")))
+@end lisp
+
+As you might surmise from this example, this alist consists of several
+@dfn{styles}. Each style will be applicable if the first element
+``matches'', in some form or other. The entire alist will be iterated
+over, from the beginning towards the end, and each match will be
+applied, which means that attributes in later styles that match override
+the same attributes in earlier matching styles. So
+@samp{comp.programming.literate} will have the @samp{Death to everybody}
+signature and the @samp{What me?} @code{Organization} header.
+
+The first element in each style is called the @code{match}. If it's a
+string, then Gnus will try to regexp match it against the group name.
+If it's a function symbol, that function will be called with no
+arguments. If it's a variable symbol, then the variable will be
+referenced. If it's a list, then that list will be @code{eval}ed. In
+any case, if this returns a non-@code{nil} value, then the style is said
+to @dfn{match}.
+
+Each style may contain a arbitrary amount of @dfn{attributes}. Each
+attribute consists of a @var{(name . value)} pair. The attribute name
+can be one of @code{signature}, @code{signature-file},
+@code{organization}, @code{address}, @code{name} or @code{body}. The
+attribute name can also be a string. In that case, this will be used as
+a header name, and the value will be inserted in the headers of the
+article.
+
+The attribute value can be a string (used verbatim), a function (the
+return value will be used), a variable (its value will be used) or a
+list (it will be @code{eval}ed and the return value will be used).
+
+If you wish to check whether the message you are about to compose is
+meant to be a news article or a mail message, you can check the values
+of the two dynamically bound variables @code{message-this-is-news} and
+@code{message-this-is-mail}.
+
+@vindex message-this-is-mail
+@vindex message-this-is-news
+
+So here's a new example:
+
+@lisp
+(setq gnus-posting-styles
+ '((".*"
+ (signature-file "~/.signature")
+ (name "User Name")
+ ("X-Home-Page" (getenv "WWW_HOME"))
+ (organization "People's Front Against MWM"))
+ ("^rec.humor"
+ (signature my-funny-signature-randomizer))
+ ((equal (system-name) "gnarly")
+ (signature my-quote-randomizer))
+ (message-this-is-news
+ (signature my-news-signature))
+ (posting-from-work-p
+ (signature-file "~/.work-signature")
+ (address "user@@bar.foo")
+ (body "You are fired.\n\nSincerely, your boss.")
+ (organization "Important Work, Inc"))
+ ("^nn.+:"
+ (signature-file "~/.mail-signature"))))
+@end lisp
+
@node Drafts
@section Drafts
automatically associate to an article in a special @dfn{draft} group.
If you save the buffer the normal way (@kbd{C-x C-s}, for instance), the
article will be saved there. (Auto-save files also go to the draft
-group.)
+group.)
@cindex nndraft
@vindex nndraft-directory
If the group doesn't exist, it will be created and you'll be subscribed
to it. The only way to make it disappear from the Group buffer is to
-unsubscribe it.
+unsubscribe it.
@c @findex gnus-dissociate-buffer-from-draft
@c @kindex C-c M-d (Mail)
@c (@code{gnus-dissociate-buffer-from-draft}) command does that for you.
@c If you change your mind and want to turn the auto-saving back on again,
@c @kbd{C-c C-d} (@code{gnus-associate-buffer-with-draft} does that.
-@c
+@c
@c @vindex gnus-use-draft
@c To leave association with the draft group off by default, set
-@c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
+@c @code{gnus-use-draft} to @code{nil}. It is @code{t} by default.
@findex gnus-draft-edit-message
@kindex D e (Draft)
@table @samp
-@item h
+@item h
How the news is fetched---the backend name.
@item n
@vindex gnus-server-mode-line-format
The mode line can also be customized by using the
-@code{gnus-server-mode-line-format} variable. The following specs are
-understood:
+@code{gnus-server-mode-line-format} variable (@pxref{Mode Line
+Formatting}). The following specs are understood:
@table @samp
@item S
@findex gnus-server-scan-server
Request that the server scan its sources for new articles
(@code{gnus-server-scan-server}). This is mainly sensible with mail
-servers.
+servers.
@item g
@kindex g (Server)
@node Example Methods
@subsection Example Methods
-Most select methods are pretty simple and self-explanatory:
+Most select methods are pretty simple and self-explanatory:
@lisp
(nntp "news.funet.fi")
As you can see, the first element in a select method is the name of the
backend, and the second is the @dfn{address}, or @dfn{name}, if you
-will.
+will.
After these two elements, there may be an arbitrary number of
@var{(variable form)} pairs.
Here's the method for a public spool:
@lisp
-(nnmh "public"
- (nnmh-directory "/usr/information/spool/")
+(nnmh "public"
+ (nnmh-directory "/usr/information/spool/")
(nnmh-get-new-mail nil))
@end lisp
("telnet" "the.real.nntp.host" "nntp")))
@end lisp
+If you want to use the wonderful @code{ssh} program to provide a
+compressed connection over the modem line, you could create a virtual
+server that would look something like this:
+
+@lisp
+(nntp "news"
+ (nntp-address "copper.uio.no")
+ (nntp-rlogin-program "ssh")
+ (nntp-open-connection-function nntp-open-rlogin)
+ (nntp-end-of-line "\n")
+ (nntp-rlogin-parameters
+ ("telnet" "news.uio.no" "nntp")))
+@end lisp
+
+This means that you have to have set up @code{ssh-agent} correctly to
+provide automatic authorization, of course. And to get a compressed
+connection, you have to have the @samp{Compression} option in the
+@code{ssh} @file{config} file.
@node Creating a Virtual Server
manual, but here's an example @code{nnml} definition:
@lisp
-(nnml "public"
+(nnml "public"
(nnml-directory "~/my-mail/")
(nnml-active-file "~/my-mail/active")
(nnml-newsgroups-file "~/my-mail/newsgroups"))
@kindex D (Server)
@findex gnus-server-deny-server
Mark the current server as unreachable
-(@code{gnus-server-deny-server}).
+(@code{gnus-server-deny-server}).
@item M-o
@kindex M-o (Server)
@findex gnus-server-open-all-servers
Open the connections to all servers in the buffer
-(@code{gnus-server-open-all-servers}).
+(@code{gnus-server-open-all-servers}).
@item M-c
@kindex M-c (Server)
@findex gnus-server-close-all-servers
Close the connections to all servers in the buffer
-(@code{gnus-server-close-all-servers}).
+(@code{gnus-server-close-all-servers}).
@item R
@kindex R (Server)
@findex gnus-server-remove-denials
Remove all marks to whether Gnus was denied connection from any servers
-(@code{gnus-server-remove-denials}).
+(@code{gnus-server-remove-denials}).
@end table
you feel like. There will be no name collisions.
The following variables can be used to create a virtual @code{nntp}
-server:
+server:
@table @code
@code{nntp-send-mode-reader} function. This function should always be
present in this hook.
-@item nntp-authinfo-function
-@vindex nntp-authinfo-function
+@item nntp-authinfo-function
+@vindex nntp-authinfo-function
@findex nntp-send-authinfo
@vindex nntp-authinfo-file
This function will be used to send @samp{AUTHINFO} to the @sc{nntp}
server. The default function is @code{nntp-send-authinfo}, which looks
through your @file{~/.authinfo} (or whatever you've set the
-@code{nntp-authinfo-file} variable to) for applicable entries. If
-none are found, it will prompt you for a login name and a password. The
-format of the @file{~/.authinfo} file is the same as the @code{ftp}
-@file{~/.netrc} file, which is defined in the @code{ftp} manual page,
-but here are the salient facts:
+@code{nntp-authinfo-file} variable to) for applicable entries. If none
+are found, it will prompt you for a login name and a password. The
+format of the @file{~/.authinfo} file is (almost) the same as the
+@code{ftp} @file{~/.netrc} file, which is defined in the @code{ftp}
+manual page, but here are the salient facts:
@enumerate
@item
@item
Each line may contain an arbitrary number of token/value pairs. The
-valid tokens include @samp{machine}, @samp{login}, and @samp{password}.
+valid tokens include @samp{machine}, @samp{login}, @samp{password},
+@samp{default} and @samp{force}. (The latter is not a valid
+@file{.netrc}/@code{ftp} token, which is the only way the
+@file{.authinfo} file format deviates from the @file{.netrc} file
+format.)
@end enumerate
@example
machine news.uio.no login larsi password geheimnis
-machine nntp.ifi.uio.no login larsi
+machine nntp.ifi.uio.no login larsi force yes
@end example
The token/value pairs may appear in any order; @samp{machine} doesn't
In this example, both login name and password have been supplied for the
former server, while the latter has only the login name listed, and the
-user will be prompted for the password.
+user will be prompted for the password. The latter also has the
+@samp{force} tag, which means that the authinfo will be sent to the
+@var{nntp} server upon connection; the default (i.e., when there is not
+@samp{force} tag) is to not send authinfo to the @var{nntp} server
+until the @var{nntp} server asks for it.
+
+You can also add @samp{default} lines that will apply to all servers
+that don't have matching @samp{machine} lines.
+
+@example
+default force yes
+@end example
+
+This will force sending @samp{AUTHINFO} commands to all servers not
+previously mentioned.
Remember to not leave the @file{~/.authinfo} file world-readable.
-@item nntp-server-action-alist
-@vindex nntp-server-action-alist
+@item nntp-server-action-alist
+@vindex nntp-server-action-alist
This is a list of regexps to match on server types and actions to be
taken when matches are made. For instance, if you want Gnus to beep
every time you connect to innd, you could say something like:
The default value is
@lisp
-'(("nntpd 1\\.5\\.11t"
+'(("nntpd 1\\.5\\.11t"
(remove-hook 'nntp-server-opened-hook 'nntp-send-mode-reader)))
@end lisp
This ensures that Gnus doesn't send the @code{MODE READER} command to
-nntpd 1.5.11t, since that command chokes that server, I've been told.
+nntpd 1.5.11t, since that command chokes that server, I've been told.
@item nntp-maximum-request
@vindex nntp-maximum-request
@c number of seconds, shut down the connection, start a new one, and resend
@c the command. This should hopefully be transparent to the user. A
@c likely number is 30 seconds.
-@c
+@c
@c @item nntp-retry-on-break
@c @vindex nntp-retry-on-break
@c If this variable is non-@code{nil}, you can also @kbd{C-g} if Gnus
@findex nntp-open-network-stream
@item nntp-open-connection-function
@vindex nntp-open-connection-function
-This function is used to connect to the remote system. Three pre-made
-functions are @code{nntp-open-network-stream}, which is the default, and
-simply connects to some port or other on the remote system. The other
-two are @code{nntp-open-rlogin}, which does an @samp{rlogin} on the
+This function is used to connect to the remote system. Four pre-made
+functions are supplied:
+
+@table @code
+@item nntp-open-network-stream
+This is the default, and simply connects to some port or other on the
+remote system.
+
+@item nntp-open-rlogin
+Does an @samp{rlogin} on the
remote system, and then does a @samp{telnet} to the @sc{nntp} server
-available there, and @code{nntp-open-telnet}, which does a @samp{telnet}
-to the remote system and then another @samp{telnet} to get to the
-@sc{nntp} server.
+available there.
@code{nntp-open-rlogin}-related variables:
@table @code
-@item nntp-rlogin-program
-@vindex nntp-rlogin-program
+@item nntp-rlogin-program
+@vindex nntp-rlogin-program
Program used to log in on remote machines. The default is @samp{rsh},
but @samp{ssh} is a popular alternative.
@end table
+@item nntp-open-telnet
+Does a @samp{telnet} to the remote system and then another @samp{telnet}
+to get to the @sc{nntp} server.
+
@code{nntp-open-telnet}-related variables:
@table @code
@end table
+@findex nntp-open-ssl-stream
+@item nntp-open-ssl-stream
+Opens a connection to a server over a @dfn{secure} channel. To use this
+you must have SSLay installed
+(@file{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}, and you also need
+@file{ssl.el} (from the W3 distributeion, for instance). You then
+define a server as follows:
+
+@lisp
+;; Type `C-c C-c' after you've finished editing.
+;;
+;; "snews" is port 563 and is predefined in our /etc/services
+;;
+(nntp "snews.bar.com"
+ (nntp-open-connection-function nntp-open-ssl-stream)
+ (nntp-port-number "snews")
+ (nntp-address "snews.bar.com"))
+@end lisp
+
+@end table
+
@item nntp-end-of-line
@vindex nntp-end-of-line
String to use as end-of-line marker when talking to the @sc{nntp}
@item nntp-rlogin-user-name
@vindex nntp-rlogin-user-name
User name on the remote system when using the @code{rlogin} connect
-function.
+function.
@item nntp-address
@vindex nntp-address
@vindex nntp-buggy-select
Set this to non-@code{nil} if your select routine is buggy.
-@item nntp-nov-is-evil
-@vindex nntp-nov-is-evil
+@item nntp-nov-is-evil
+@vindex nntp-nov-is-evil
If the @sc{nntp} server does not support @sc{nov}, you could set this
variable to @code{t}, but @code{nntp} usually checks automatically whether @sc{nov}
can be used.
@cindex XOVER
List of strings used as commands to fetch @sc{nov} lines from a
server. The default value of this variable is @code{("XOVER"
-"XOVERVIEW")}.
+"XOVERVIEW")}.
@item nntp-nov-gap
@vindex nntp-nov-gap
Subscribing to a foreign group from the local spool is extremely easy,
and might be useful, for instance, to speed up reading groups that
contain very big articles---@samp{alt.binaries.pictures.furniture}, for
-instance.
+instance.
Anyways, you just specify @code{nnspool} as the method and @code{""} (or
anything else) as the address.
@item nnspool-inews-switches
@vindex nnspool-inews-switches
-Parameters given to the inews program when posting an article.
+Parameters given to the inews program when posting an article.
@item nnspool-spool-directory
@vindex nnspool-spool-directory
Where @code{nnspool} looks for the articles. This is normally
@file{/usr/spool/news/}.
-@item nnspool-nov-directory
-@vindex nnspool-nov-directory
+@item nnspool-nov-directory
+@vindex nnspool-nov-directory
Where @code{nnspool} will look for @sc{nov} files. This is normally
@file{/usr/spool/news/over.view/}.
@menu
* Getting Started Reading Mail:: A simple cookbook example.
* Splitting Mail:: How to create mail groups.
+* Mail Sources:: How to tell Gnus where to get mail from.
* Mail Backend Variables:: Variables for customizing mail handling.
* Fancy Mail Splitting:: Gnus can do hairy splitting of incoming mail.
-* Mail and Procmail:: Reading mail groups that procmail create.
* Incorporating Old Mail:: What about the old mail you have?
* Expiring Mail:: Getting rid of unwanted mail.
* Washing Mail:: Removing gruft from the mail you get.
This should be sufficient for reading mail with Gnus. You might want to
give the other sections in this part of the manual a perusal, though.
-Especially @pxref{Choosing a Mail Backend} and @pxref{Expiring Mail}.
+Especially @pxref{Choosing a Mail Backend} and @pxref{Expiring Mail}.
@node Splitting Mail
insert sub-expressions from the matched text. For instance:
@lisp
-("list.\\1" "From:.*\\(.*\\)-list@@majordomo.com")
+("list.\\1" "From:.* \\(.*\\)-list@@majordomo.com")
@end lisp
-If the first element is the special symbol @code{junk}, then messages
-that match the regexp will disappear into the aether. Use with
-extreme caution.
-
The second element can also be a function. In that case, it will be
called narrowed to the headers with the first element of the rule as the
argument. It should return a non-@code{nil} value if it thinks that the
the crossposted articles. However, not all file systems support hard
links. If that's the case for you, set
@code{nnmail-crosspost-link-function} to @code{copy-file}. (This
-variable is @code{add-name-to-file} by default.)
+variable is @code{add-name-to-file} by default.)
+
+@findex nnmail-split-header-length-limit
+Header lines may be arbitrarily long. However, the longer a line is,
+the longer it takes to match them. Very long lines may lead to Gnus
+taking forever to split the mail, so Gnus excludes lines that are longer
+than @code{nnmail-split-header-length-limit} (which defaults to 1024).
@kindex M-x nnmail-split-history
@kindex nnmail-split-history
month's rent money.
-@node Mail Backend Variables
-@subsection Mail Backend Variables
+@node Mail Sources
+@subsection Mail Sources
-These variables are (for the most part) pertinent to all the various
-mail backends.
+Mail can be gotten from many different sources---the mail spool, from a
+POP mail server, or from a procmail directory, for instance.
+
+@menu
+* Mail Source Specifiers:: How to specify what a mail source is.
+* Mail Source Customization:: Some variables that influence things.
+* Fetching Mail:: Using the mail source specifiers.
+@end menu
+
+
+@node Mail Source Specifiers
+@subsubsection Mail Source Specifiers
+@cindex POP
+@cindex mail server
+@cindex procmail
+@cindex mail spool
+@cindex mail source
+
+You tell Gnus how to fetch mail by creating a @dfn{mail source
+specifier}.
+
+Here's an example:
+
+@lisp
+(pop :server "pop3.mailserver.com" :user "myname")
+@end lisp
+
+As can be observed, a mail source specifier is a list where the first
+element is a @dfn{mail source type}, followed by an arbitrary number of
+@dfn{keywords}. Keywords that are not explicitly specified are given
+default values.
+
+The following mail source types are available:
@table @code
-@vindex nnmail-read-incoming-hook
-@item nnmail-read-incoming-hook
-The mail backends all call this hook after reading new mail. You can
-use this hook to notify any mail watch programs, if you want to.
+@item file
+Get mail from a single file; typically from the mail spool.
+
+Keywords:
+
+@table @code
+@item :path
+The path of the file. Defaults to the value of the @code{MAIL}
+environment variable or @file{/usr/mail/spool/user-name}.
+@end table
+
+An example file mail source:
+
+@lisp
+(file :path "/usr/spool/mail/user-name")
+@end lisp
+
+Or using the default path:
+
+@lisp
+(file)
+@end lisp
+
+@item directory
+Get mail from several files in a directory. This is typically used when
+you have procmail split the incoming mail into several files.
+
+Keywords:
+
+@table @code
+@item :path
+The path of the directory where the files are. There is no default
+value.
+
+@item :suffix
+Only files ending with this suffix are used. The default is
+@samp{.spool}.
+
+@item :predicate
+Only files that have this predicate return non-@code{nil} are returned.
+The default is @code{identity}. This is used as an additional
+filter---only files that have the right suffix @emph{and} satisfy this
+predicate are considered.
+
+@end table
+
+An example directory mail source:
+
+@lisp
+(directory :path "/home/user-name/procmail-dir/"
+ :suffix ".prcml")
+@end lisp
+
+@item pop
+Get mail from a POP server.
+
+Keywords:
+
+@table @code
+@item :server
+The name of the POP server. The default is taken from the
+@code{MAILHOST} environment variable.
+
+@item :port
+The port number of the POP server. The default is @samp{pop3}.
+
+@item :user
+The user name to give to the POP server. The default is the login
+name.
+
+@item :password
+The password to give to the POP server. If not specified, the user is
+prompted.
+
+@item :program
+The program to use to fetch mail from the POP server. This is should be
+a @code{format}-like string. Here's an example:
+
+@example
+fetchmail %u@@%s -P %p %t
+@end example
+
+The valid format specifier characters are:
+
+@table @samp
+@item t
+The name of the file the mail is to be moved to. This must always be
+included in this string.
+
+@item s
+The name of the server.
+
+@item P
+The port number of the server.
+
+@item u
+The user name to use.
+
+@item p
+The password to use.
+@end table
+
+The values used for these specs are taken from the values you give the
+corresponding keywords.
+
+@item :prescript
+A script to be run before fetching the mail. The syntax is the same as
+the @code{:program} keyword. This can also be a function to be run.
+
+@item :postscript
+A script to be run after fetching the mail. The syntax is the same as
+the @code{:program} keyword. This can also be a function to be run.
+
+@item :function
+The function to use to fetch mail from the POP server. The function is
+called with one parameter---the name of the file where the mail should
+be moved to.
+
+@item :authentication
+This can be either the symbol @code{password} or the symbol @code{apop}
+and says what authentication scheme to use. The default is
+@code{password}.
+
+@end table
+
+If the @code{:program} and @code{:function} keywords aren't specified,
+@code{pop3-movemail} will be used.
+
+Here are some examples. Fetch from the default POP server, using the
+default user name, and default fetcher:
+
+@lisp
+(pop)
+@end lisp
+
+Fetch from a named server with a named user and password:
+
+@lisp
+(pop :server "my.pop.server"
+ :user "user-name" :password "secret")
+@end lisp
+
+Use @samp{movemail} to move the mail:
+
+@lisp
+(pop :program "movemail"
+ :args (format "po:%s %s %s" user mail-source-crash-box password))
+@end lisp
+
+@item maildir
+Get mail from a maildir. This is a type of mailbox currently only
+supported by qmail, where each file in a special directory contains
+exactly one mail.
+
+Keywords:
+
+@table @code
+@item :path
+The path of the directory where the mails are stored. The default is
+@samp{~/Maildir/new}.
+
+If you sometimes look at your mail through a pop3 daemon before fetching
+them with Gnus, you may also have to fetch your mails from the
+@code{cur} directory inside the maildir, like in the following example.
+
+@end table
+
+An example maildir mail source:
+
+@lisp
+(maildir :path "/home/user-name/Maildir/cur")
+@end lisp
+
+@end table
+
+
+@node Mail Source Customization
+@subsubsection Mail Source Customization
+
+The following is a list of variables that influence how the mail is
+fetched. You would normally not need to set or change any of these
+variables.
+
+@table @code
+@item mail-source-movemail-program
+@vindex mail-source-movemail-program
+A command to be executed to move mail from the inbox. The default is
+@samp{movemail}.
+
+This can also be a function. In that case, the function will be
+called with two parameters -- the name of the INBOX file, and the file
+to be moved to.
+
+@item mail-source-movemail-args
+@vindex mail-source-movemail-args
+Extra arguments to give to the command described above.
+
+@item mail-source-crash-box
+@vindex mail-source-crash-box
+File where mail will be stored while processing it. The default is
+@file{~/.emacs-mail-crash-box}.
+
+@item mail-source-delete-incoming
+@vindex mail-source-delete-incoming
+If non-@code{nil}, delete incoming files after handling them.
+
+@item mail-source-directory
+@vindex mail-source-directory
+Directory where files (if any) will be stored. The default is
+@file{~/Mail/}. At present, the only thing this is used for is to say
+where the incoming files will be stored if the previous variable is
+@code{nil}.
+
+@item mail-source-default-file-modes
+@vindex mail-source-default-file-modes
+All new mail files will get this file mode. The default is 384.
+
+@end table
+
+
+@node Fetching Mail
+@subsubsection Fetching Mail
+
+The way to actually tell Gnus where to get new mail from is to set
+@code{nnmail-spool-file} to a list of mail source specifiers
+(@pxref{Mail Source Specifiers}).
+
+If this variable is @code{nil}, the mail backends will never attempt to
+fetch mail by themselves.
+
+If you want to fetch mail both from your local spool as well as a POP
+mail server, you'd say something like:
+
+@lisp
+(setq nnmail-spool-file
+ '((file)
+ (pop :server "pop3.mail.server"
+ :password "secret")))
+@end lisp
+
+Or, if you don't want to use any of the keyword defaults:
+
+@lisp
+(setq nnmail-spool-file
+ '((file :path "/var/spool/mail/user-name")
+ (pop :server "pop3.mail.server"
+ :user "user-name"
+ :port "pop3"
+ :password "secret")))
+@end lisp
-@vindex nnmail-spool-file
-@item nnmail-spool-file
-@cindex POP mail
-@cindex MAILHOST
-@cindex movemail
-@vindex nnmail-pop-password
-@vindex nnmail-pop-password-required
-The backends will look for new mail in this file. If this variable is
-@code{nil}, the mail backends will never attempt to fetch mail by
-themselves. If you are using a POP mail server and your name is
-@samp{larsi}, you should set this variable to @samp{po:larsi}. If
-your name is not @samp{larsi}, you should probably modify that
-slightly, but you may have guessed that already, you smart & handsome
-devil! You can also set this variable to @code{pop}, and Gnus will try
-to figure out the POP mail string by itself. In any case, Gnus will
-call @code{movemail} which will contact the POP server named in the
-@code{MAILHOST} environment variable. If the POP server needs a
-password, you can either set @code{nnmail-pop-password-required} to
-@code{t} and be prompted for the password, or set
-@code{nnmail-pop-password} to the password itself.
-
-@code{nnmail-spool-file} can also be a list of mailboxes.
-
-Your Emacs has to have been configured with @samp{--with-pop} before
-compilation. This is the default, but some installations have it
-switched off.
When you use a mail backend, Gnus will slurp all your mail from your
inbox and plonk it down in your home directory. Gnus doesn't move any
pentagram, lightened the candles, and sacrificed the goat, you really
shouldn't be too surprised when Gnus moves your mail.
-@vindex nnmail-use-procmail
-@vindex nnmail-procmail-suffix
-@item nnmail-use-procmail
-If non-@code{nil}, the mail backends will look in
-@code{nnmail-procmail-directory} for incoming mail. All the files in
-that directory that have names ending in @code{nnmail-procmail-suffix}
-will be considered incoming mailboxes, and will be searched for new
-mail.
-@vindex nnmail-crash-box
-@item nnmail-crash-box
-When a mail backend reads a spool file, mail is first moved to this
-file, which is @file{~/.gnus-crash-box} by default. If this file
-already exists, it will always be read (and incorporated) before any
-other spool files.
-@vindex nnmail-prepare-incoming-hook
-@item nnmail-prepare-incoming-hook
-This is run in a buffer that holds all the new incoming mail, and can be
-used for, well, anything, really.
+@node Mail Backend Variables
+@subsection Mail Backend Variables
+
+These variables are (for the most part) pertinent to all the various
+mail backends.
+
+@table @code
+@vindex nnmail-read-incoming-hook
+@item nnmail-read-incoming-hook
+The mail backends all call this hook after reading new mail. You can
+use this hook to notify any mail watch programs, if you want to.
@vindex nnmail-split-hook
@item nnmail-split-hook
-@findex article-decode-rfc1522
+@findex article-decode-encoded-words
@findex RFC1522 decoding
+@findex RFC2047 decoding
Hook run in the buffer where the mail headers of each message is kept
just before the splitting based on these headers is done. The hook is
free to modify the buffer contents in any way it sees fit---the buffer
is discarded after the splitting has been done, and no changes performed
-in the buffer will show up in any files. @code{gnus-article-decode-rfc1522}
-is one likely function to add to this hook.
+in the buffer will show up in any files.
+@code{gnus-article-decode-encoded-words} is one likely function to add
+to this hook.
@vindex nnmail-pre-get-new-mail-hook
@vindex nnmail-post-get-new-mail-hook
default file modes the new mail files get:
@lisp
-(add-hook 'gnus-pre-get-new-mail-hook
+(add-hook 'gnus-pre-get-new-mail-hook
(lambda () (set-default-file-modes 511)))
-(add-hook 'gnus-post-get-new-mail-hook
+(add-hook 'gnus-post-get-new-mail-hook
(lambda () (set-default-file-modes 551)))
@end lisp
-@item nnmail-tmp-directory
-@vindex nnmail-tmp-directory
-This variable says where to move incoming mail to -- while processing
-it. This is usually done in the same directory that the mail backend
-inhabits (e.g., @file{~/Mail/}), but if this variable is non-@code{nil},
-it will be used instead.
-
-@item nnmail-movemail-program
-@vindex nnmail-movemail-program
-This program is executed to move mail from the user's inbox to her home
-directory. The default is @samp{movemail}.
-
-This can also be a function. In that case, the function will be called
-with two parameters -- the name of the inbox, and the file to be moved
-to.
-
-@item nnmail-delete-incoming
-@vindex nnmail-delete-incoming
-@cindex incoming mail files
-@cindex deleting incoming files
-If non-@code{nil}, the mail backends will delete the temporary incoming
-file after splitting mail into the proper groups. This is @code{t} by
-default.
-
-@c This is @code{nil} by
-@c default for reasons of security.
-
-@c Since Red Gnus is an alpha release, it is to be expected to lose mail.
-(No Gnus release since (ding) Gnus 0.10 (or something like that) have
-lost mail, I think, but that's not the point. (Except certain versions
-of Red Gnus.)) By not deleting the Incoming* files, one can be sure not
-to lose mail -- if Gnus totally whacks out, one can always recover what
-was lost.
-
-You may delete the @file{Incoming*} files at will.
-
@item nnmail-use-long-file-names
@vindex nnmail-use-long-file-names
If non-@code{nil}, the mail backends will use long file and directory
@item nnmail-delete-file-function
@vindex nnmail-delete-file-function
@findex delete-file
-Function called to delete files. It is @code{delete-file} by default.
+Function called to delete files. It is @code{delete-file} by default.
@item nnmail-cache-accepted-message-ids
@vindex nnmail-cache-accepted-message-ids
@enumerate
-@item
-@samp{group}: If the split is a string, that will be taken as a group name.
+@item
+@samp{group}: If the split is a string, that will be taken as a group
+name. Normal regexp match expansion will be done. See below for
+examples.
@item
@var{(FIELD VALUE SPLIT)}: If the split is a list, the first element of
@var{(& SPLIT...)}: If the split is a list, and the first element is
@code{&}, then process all SPLITs in the list.
-@item
+@item
@code{junk}: If the split is the symbol @code{junk}, then don't save
-this message.
+this message. Use with extreme caution.
@item
@var{(: function arg1 arg2 ...)}: If the split is a list, and the first
function with @var{args} given as arguments. The function should return
a SPLIT.
+@item
+@code{nil}: If the split is @code{nil}, it is ignored.
+
@end enumerate
In these splits, @var{FIELD} must match a complete field name.
If you want to have Gnus create groups dynamically based on some
information in the headers (i.e., do @code{replace-match}-like
-substitions in the group names), you can say things like:
+substitutions in the group names), you can say things like:
@example
-(any "debian-\\(\\w*\\)@@lists.debian.org" "mail.debian.\\1")
+(any "debian-\\b\\(\\w+\\)@@lists.debian.org" "mail.debian.\\1")
@end example
-@node Mail and Procmail
-@subsection Mail and Procmail
-@cindex procmail
-
-@cindex slocal
-@cindex elm
-Many people use @code{procmail} (or some other mail filter program or
-external delivery agent---@code{slocal}, @code{elm}, etc) to split
-incoming mail into groups. If you do that, you should set
-@code{nnmail-spool-file} to @code{procmail} to ensure that the mail
-backends never ever try to fetch mail by themselves.
-
-If you have a combined @code{procmail}/POP/mailbox setup, you can do
-something like the following:
-
-@vindex nnmail-use-procmail
-@lisp
-(setq nnmail-use-procmail t)
-(setq nnmail-spool-file
- '("/usr/spool/mail/my-name" "po:my-name"))
-@end lisp
-
-This also means that you probably don't want to set
-@code{nnmail-split-methods} either, which has some, perhaps, unexpected
-side effects.
-
-When a mail backend is queried for what groups it carries, it replies
-with the contents of that variable, along with any groups it has figured
-out that it carries by other means. None of the backends, except
-@code{nnmh}, actually go out to the disk and check what groups actually
-exist. (It's not trivial to distinguish between what the user thinks is
-a basis for a newsgroup and what is just a plain old file or directory.)
-
-This means that you have to tell Gnus (and the backends) by hand what
-groups exist.
-
-Let's take the @code{nnmh} backend as an example:
-
-The folders are located in @code{nnmh-directory}, say, @file{~/Mail/}.
-There are three folders, @file{foo}, @file{bar} and @file{mail.baz}.
-
-Go to the group buffer and type @kbd{G m}. When prompted, answer
-@samp{foo} for the name and @samp{nnmh} for the method. Repeat
-twice for the two other groups, @samp{bar} and @samp{mail.baz}. Be sure
-to include all your mail groups.
-
-That's it. You are now set to read your mail. An active file for this
-method will be created automatically.
-
-@vindex nnmail-procmail-suffix
-@vindex nnmail-procmail-directory
-If you use @code{nnfolder} or any other backend that store more than a
-single article in each file, you should never have procmail add mails to
-the file that Gnus sees. Instead, procmail should put all incoming mail
-in @code{nnmail-procmail-directory}. To arrive at the file name to put
-the incoming mail in, append @code{nnmail-procmail-suffix} to the group
-name. The mail backends will read the mail from these files.
-
-@vindex nnmail-resplit-incoming
-When Gnus reads a file called @file{mail.misc.spool}, this mail will be
-put in the @code{mail.misc}, as one would expect. However, if you want
-Gnus to split the mail the normal way, you could set
-@code{nnmail-resplit-incoming} to @code{t}.
-
-@vindex nnmail-keep-last-article
-If you use @code{procmail} to split things directly into an @code{nnmh}
-directory (which you shouldn't do), you should set
-@code{nnmail-keep-last-article} to non-@code{nil} to prevent Gnus from
-ever expiring the final article (i.e., the article with the highest
-article number) in a mail newsgroup. This is quite, quite important.
-
-Here's an example setup: The incoming spools are located in
-@file{~/incoming/} and have @samp{""} as suffixes (i.e., the incoming
-spool files have the same names as the equivalent groups). The
-@code{nnfolder} backend is to be used as the mail interface, and the
-@code{nnfolder} directory is @file{~/fMail/}.
-
-@lisp
-(setq nnfolder-directory "~/fMail/")
-(setq nnmail-spool-file 'procmail)
-(setq nnmail-procmail-directory "~/incoming/")
-(setq gnus-secondary-select-methods '((nnfolder "")))
-(setq nnmail-procmail-suffix "")
-@end lisp
+If the string contains the element @samp{\&}, then the previously
+matched string will be substituted. Similarly, the elements @samp{\\1}
+up to @samp{\\9} will be substituted with the text matched by the
+groupings 1 through 9.
@node Incorporating Old Mail
@item
Go to the group buffer.
-@item
+@item
Type `G f' and give the path to the mbox file when prompted to create an
@code{nndoc} group from the mbox file (@pxref{Foreign Groups}).
-@item
+@item
Type `SPACE' to enter the newly created group.
@item
Type `M P b' to process-mark all articles in this group's buffer
(@pxref{Setting Process Marks}).
-@item
+@item
Type `B r' to respool all the process-marked articles, and answer
@samp{nnml} when prompted (@pxref{Mail Group Commands}).
@end enumerate
@vindex gnus-mark-article-hook
@lisp
-(remove-hook 'gnus-mark-article-hook
- 'gnus-summary-mark-read-and-unread-as-read)
+(remove-hook 'gnus-mark-article-hook
+ 'gnus-summary-mark-read-and-unread-as-read)
(add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
@end lisp
articles you have read to disappear after a while:
@lisp
-(setq gnus-auto-expirable-newsgroups
+(setq gnus-auto-expirable-newsgroups
"mail.nonsense-list\\|mail.nice-list")
@end lisp
Another way to have auto-expiry happen is to have the element
-@code{auto-expire} in the group parameters of the group.
+@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
-don't really mix very well.
+don't really mix very well.
@vindex nnmail-expiry-wait
The @code{nnmail-expiry-wait} variable supplies the default time an
@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.
+Most people make most of their mail groups total-expirable, though.
+
+@vindex gnus-inhibit-user-auto-expire
+If @code{gnus-inhibit-user-auto-expire} is non-@code{nil}, user marking
+commands will not mark an article as expirable, even if the group has
+auto-expire turned on.
@node Washing Mail
@item nnmail-prepare-incoming-hook
@vindex nnmail-prepare-incoming-hook
This hook is called before doing anything with the mail and is meant for
-grand, sweeping gestures. Functions to be used include:
+grand, sweeping gestures. It is called in a buffer that contains all
+the new, incoming mail. Functions to be used include:
@table @code
@item nnheader-ms-strip-cr
@item nnmail-remove-leading-whitespace
@findex nnmail-remove-leading-whitespace
Clear leading white space that ``helpful'' listservs have added to the
-headers to make them look nice. Aaah.
+headers to make them look nice. Aaah.
@item nnmail-remove-list-identifiers
@findex nnmail-remove-list-identifiers
@item nnmail-remove-tabs
@findex nnmail-remove-tabs
-Translate all @samp{TAB} characters into @samp{SPACE} characters.
+Translate all @samp{TAB} characters into @samp{SPACE} characters.
+
+@item nnmail-fix-eudora-headers
+@findex nnmail-fix-eudora-headers
+@cindex Eudora
+Eudora produces broken @code{References} headers, but OK
+@code{In-Reply-To} headers. This function will get rid of the
+@code{References} headers.
@end table
@item nnmail-prepare-incoming-message-hook
@vindex nnmail-prepare-incoming-message-hook
This hook is called narrowed to each message. Functions to be used
-include:
+include:
@table @code
@item article-de-quoted-unreadable
Or something like:
@lisp
-(setq nnmail-split-methods
+(setq nnmail-split-methods
'(("duplicates" "^Gnus-Warning:")
;; Other rules.
[...]))
@table @code
@item nnmbox-mbox-file
@vindex nnmbox-mbox-file
-The name of the mail box in the user's home directory.
+The name of the mail box in the user's home directory.
@item nnmbox-active-file
@vindex nnmbox-active-file
@item nnbabyl-get-new-mail
@vindex nnbabyl-get-new-mail
-If non-@code{nil}, @code{nnbabyl} will read incoming mail.
+If non-@code{nil}, @code{nnbabyl} will read incoming mail.
@end table
@table @code
@item nnml-directory
@vindex nnml-directory
-All @code{nnml} directories will be placed under this directory.
+All @code{nnml} directories will be placed under this directory.
@item nnml-active-file
@vindex nnml-active-file
@item nnml-newsgroups-file
@vindex nnml-newsgroups-file
The @code{nnml} group descriptions file. @xref{Newsgroups File
-Format}.
+Format}.
@item nnml-get-new-mail
@vindex nnml-get-new-mail
@item nnml-nov-is-evil
@vindex nnml-nov-is-evil
-If non-@code{nil}, this backend will ignore any @sc{nov} files.
+If non-@code{nil}, this backend will ignore any @sc{nov} files.
@item nnml-nov-file-name
@vindex nnml-nov-file-name
-The name of the @sc{nov} files. The default is @file{.overview}.
+The name of the @sc{nov} files. The default is @file{.overview}.
@item nnml-prepare-save-mail-hook
@vindex nnml-prepare-save-mail-hook
entire @code{nnml} hierarchy, looking at each and every article, so it
might take a while to complete. A better interface to this
functionality can be found in the server buffer (@pxref{Server
-Commands}).
+Commands}).
@node MH Spool
@table @code
@item nnfolder-directory
@vindex nnfolder-directory
-All the @code{nnfolder} mail boxes will be stored under this directory.
+All the @code{nnfolder} mail boxes will be stored under this directory.
@item nnfolder-active-file
@vindex nnfolder-active-file
@item nnfolder-get-new-mail
@vindex nnfolder-get-new-mail
If non-@code{nil}, @code{nnfolder} will read incoming mail.
+
+@item nnfolder-save-buffer-hook
+@vindex nnfolder-save-buffer-hook
+@cindex backup files
+Hook run before saving the folders. Note that Emacs does the normal
+backup renaming of files even with the @code{nnfolder} buffers. If you
+wish to switch this off, you could say something like the following in
+your @file{.emacs} file:
+
+@lisp
+(defun turn-off-backup ()
+ (set (make-local-variable 'backup-inhibited) t))
+
+(add-hook 'nnfolder-save-buffer-hook 'turn-off-backup)
+@end lisp
+
+@item nnfolder-delete-mail-hook
+@vindex nnfolder-delete-mail-hook
+Hook run in a buffer narrowed to the message that is to be deleted.
+This function can be used to copy the message to somewhere else, or to
+extract some information from it before removing it.
+
@end table
+
@findex nnfolder-generate-active-file
@kindex M-x nnfolder-generate-active-file
If you have lots of @code{nnfolder}-like files you'd like to read with
@code{nnfolder}, you can use the @kbd{M-x nnfolder-generate-active-file}
command to make @code{nnfolder} aware of all likely files in
-@code{nnfolder-directory}.
+@code{nnfolder-directory}. This only works if you use long file names,
+though.
@node Other Sources
All files that match this regexp will be ignored. Nice to use to exclude
auto-save files and the like, which is what it does by default.
+@item nneething-include-files
+@vindex nneething-include-files
+Regexp saying what files to include in the group. If this variable is
+non-@code{nil}, only files matching this regexp will be included.
+
@item nneething-map-file
@vindex nneething-map-file
Name of the map files.
@item forward
Forwarded articles.
-@item mime-digest
-@cindex digest
-@cindex MIME digest
-@cindex 1153 digest
-@cindex RFC 1153 digest
-@cindex RFC 341 digest
-MIME (RFC 1341) digest format.
+@item mime-parts
+MIME multipart messages.
@item standard-digest
The standard (RFC 1153) digest format.
@item slack-digest
-Non-standard digest format---matches most things, but does it badly.
+Non-standard digest format---matches most things, but does it badly.
@end table
You can also use the special ``file type'' @code{guess}, which means
@vindex nndoc-article-type
This should be one of @code{mbox}, @code{babyl}, @code{digest},
@code{news}, @code{rnews}, @code{mmdf}, @code{forward}, @code{rfc934},
-@code{rfc822-forward}, @code{mime-digest}, @code{standard-digest},
+@code{rfc822-forward}, @code{mime-parts}, @code{standard-digest},
@code{slack-digest}, @code{clari-briefs} or @code{guess}.
@item nndoc-post-type
First, here's an example document type definition:
@example
-(mmdf
+(mmdf
(article-begin . "^\^A\^A\^A\^A\n")
(body-end . "^\^A\^A\^A\^A\n"))
@end example
@item first-article
If present, @code{nndoc} will skip past all text until it finds
something that match this regexp. All text before this will be
-totally ignored.
+totally ignored.
@item article-begin
This setting has to be present in all document type definitions. It
@item nndoc-head-begin
If present, this should be a regexp that matches the head of the
-article.
+article.
@item nndoc-head-end
This should match the end of the head of the article. It defaults to
@item file-end
If present, this should match the end of the file. All text after this
-regexp will be totally ignored.
+regexp will be totally ignored.
@end table
@item prepare-body-function
If present, this function will be called when requesting an article. It
will be called with point at the start of the body, and is useful if the
-document has encoded some parts of its contents.
+document has encoded some parts of its contents.
@item article-transform-function
If present, this function is called when requesting an article. It's
Of course, us Unix Weenie types of human beans use things like
@code{uucp} and, like, @code{nntpd} and set up proper news and mail
transport things like Ghod intended. And then we just use normal
-newsreaders.
+newsreaders.
However, it can sometimes be convenient to do something a that's a bit
easier on the brain if you have a very slow modem, and you're not really
-that interested in doing things properly.
+that interested in doing things properly.
A file format called @sc{soup} has been developed for transporting news
and mail from servers to home machines and back again. It can be a bit
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
+@item
You transfer the packet home. Rail, boat, car or modem will do fine.
@item
You read articles and mail and answer and followup to the things you
want (@pxref{SOUP Replies}).
-@item
+@item
You do the @kbd{G s r} command to pack these replies into a @sc{soup}
packet.
-@item
-You transfer this packet to the server.
+@item
+You transfer this packet to the server.
@item
You use Gnus to mail this packet out with the @kbd{G s s} command.
@kindex G s s (Group)
@findex gnus-soup-send-replies
Send all replies from the replies packet
-(@code{gnus-soup-send-replies}).
+(@code{gnus-soup-send-replies}).
@item G s p
@kindex G s p (Group)
@findex gnus-soup-pack-packet
-Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
+Pack all files into a @sc{soup} packet (@code{gnus-soup-pack-packet}).
@item G s r
@kindex G s r (Group)
@findex nnsoup-pack-replies
-Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
+Pack all replies into a replies packet (@code{nnsoup-pack-replies}).
@item O s
@kindex O s (Summary)
@findex gnus-soup-add-article
This summary-mode command adds the current article to a @sc{soup} packet
(@code{gnus-soup-add-article}). It understands the process/prefix
-convention (@pxref{Process/Prefix}).
+convention (@pxref{Process/Prefix}).
@end table
There are a few variables to customize where Gnus will put all these
-thingies:
+thingies:
@table @code
@item gnus-soup-directory
@vindex gnus-soup-directory
Directory where Gnus will save intermediate files while composing
-@sc{soup} packets. The default is @file{~/SoupBrew/}.
+@sc{soup} packets. The default is @file{~/SoupBrew/}.
@item gnus-soup-replies-directory
@vindex gnus-soup-replies-directory
@item gnus-soup-prefix-file
@vindex gnus-soup-prefix-file
Name of the file where Gnus stores the last used prefix. The default is
-@samp{gnus-prefix}.
+@samp{gnus-prefix}.
@item gnus-soup-packer
@vindex gnus-soup-packer
A format string command for packing a @sc{soup} packet. The default is
-@samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
+@samp{tar cf - %s | gzip > $HOME/Soupout%d.tgz}.
@item gnus-soup-unpacker
@vindex gnus-soup-unpacker
@item gnus-soup-packet-directory
@vindex gnus-soup-packet-directory
-Where Gnus will look for reply packets. The default is @file{~/}.
+Where Gnus will look for reply packets. The default is @file{~/}.
@item gnus-soup-packet-regexp
@vindex gnus-soup-packet-regexp
Regular expression matching @sc{soup} reply packets in
-@code{gnus-soup-packet-directory}.
+@code{gnus-soup-packet-directory}.
@end table
-
+
@node SOUP Groups
@subsubsection @sc{soup} Groups
@item nnsoup-tmp-directory
@vindex nnsoup-tmp-directory
When @code{nnsoup} unpacks a @sc{soup} packet, it does it in this
-directory. (@file{/tmp/} by default.)
+directory. (@file{/tmp/} by default.)
@item nnsoup-directory
@vindex nnsoup-directory
@code{nnsoup} then moves each message and index file to this directory.
The default is @file{~/SOUP/}.
-@item nnsoup-replies-directory
-@vindex nnsoup-replies-directory
+@item nnsoup-replies-directory
+@vindex nnsoup-replies-directory
All replies will be stored in this directory before being packed into a
reply packet. The default is @file{~/SOUP/replies/"}.
@item nnsoup-packer
@vindex nnsoup-packer
Format string command for packing a reply @sc{soup} packet. The default
-is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
+is @samp{tar cf - %s | gzip > $HOME/Soupin%d.tgz}.
@item nnsoup-unpacker
@vindex nnsoup-unpacker
Format string command for unpacking incoming @sc{soup} packets. The
-default is @samp{gunzip -c %s | tar xvf -}.
+default is @samp{gunzip -c %s | tar xvf -}.
@item nnsoup-packet-directory
@vindex nnsoup-packet-directory
Where @code{nnsoup} will look for incoming packets. The default is
-@file{~/}.
+@file{~/}.
@item nnsoup-packet-regexp
@vindex nnsoup-packet-regexp
@vindex nnweb-type-definition
Type-to-definition alist. This alist says what @code{nnweb} should do
with the various search engine types. The following elements must be
-present:
+present:
@table @code
@item article
Function to decode the article and provide something that Gnus
-understands.
+understands.
@item map
-Function to create an article number to message header and URL alist.
+Function to create an article number to message header and URL alist.
@item search
Function to send the search string to the search engine.
@item address
The address the aforementioned function should send the search string
-to.
+to.
@item id
Format string URL to fetch an article by @code{Message-ID}.
Server variables:
@table @code
-@item nngateway-address
-@vindex nngateway-address
+@item nngateway-address
+@vindex nngateway-address
This is the address of the mail-to-news gateway.
@item nngateway-header-transformation
@vindex nngateway-header-transformation
News headers often have to be transformed in some odd way or other
-for the mail-to-news gateway to accept it. This variable says what
+for the mail-to-news gateway to accept it. This variable says what
transformation should be called, and defaults to
@code{nngateway-simple-header-transformation}. The function is called
narrowed to the headers to be transformed and with one parameter---the
To: alt-religion-emacs@@GATEWAY
@end example
+The following pre-defined functions exist:
+
+@findex nngateway-simple-header-transformation
+@table @code
+
+@item nngateway-simple-header-transformation
+Creates a @code{To} header that looks like
+@var{newsgroup}@@@code{nngateway-address}.
+
+@findex nngateway-mail2news-header-transformation
+
+@item nngateway-mail2news-header-transformation
+Creates a @code{To} header that looks like
+@code{nngateway-address}.
+
+Here's an example:
+
+@lisp
+(setq gnus-post-method
+ '(nngateway "mail2news@@replay.com"
+ (nngateway-header-transformation
+ nngateway-mail2news-header-transformation)))
+@end lisp
+
+@end table
+
+
@end table
So, to use this, simply say something like:
@subsection Virtual Groups
@cindex nnvirtual
@cindex virtual groups
+@cindex merging groups
An @dfn{nnvirtual group} is really nothing more than a collection of
other groups.
and a server in Norway, you could use the following as the group regexp:
@example
-"^nntp\\+some\\.server\\.jp:soc\\.motss$\\|^nntp\\+some\\.server\\.no:soc\\.motss$"
+"^nntp\\+server\\.jp:soc\\.motss$\\|^nntp\\+server\\.no:soc\\.motss$"
@end example
(Remember, though, that if you're creating the group with @kbd{G m}, you
Or you can just tap @code{M-g} on the virtual group every time before
you enter it---it'll have much the same effect.
+@code{nnvirtual} can have both mail and news groups as component groups.
+When responding to articles in @code{nnvirtual} groups, @code{nnvirtual}
+has to ask the backend of the component group the article comes from
+whether it is a news or mail backend. However, when you do a @kbd{^},
+there is typically no sure way for the component backend to know this,
+and in that case @code{nnvirtual} tells Gnus that the article came from a
+not-news backend. (Just to be on the safe side.)
+
+@kbd{C-c C-t} in the message buffer will insert the @code{Newsgroups}
+line from the article you respond to in these cases.
+
+
@node Kibozed Groups
@subsection Kibozed Groups
@kindex G k (Group)
To create a kibozed group, use the @kbd{G k} command in the group
-buffer.
+buffer.
The address field of the @code{nnkiboze} method is, as with
@code{nnvirtual}, a regexp to match groups to be ``included'' in the
* Agent Variables:: Customizing is fun.
* Example Setup:: An example @file{.gnus.el} file for offline people.
* Batching Agents:: How to fetch news from a @code{cron} job.
+* Agent Caveats:: What you think it'll do and what it does.
@end menu
Agent is @dfn{plugged}.
The @dfn{local} machine is the one you're running on, and which isn't
-connected to the net continously.
+connected to the net continuously.
@dfn{Downloading} means fetching things from the net to your local
machine. @dfn{Uploading} is doing the opposite.
primary select method, which is listed on the bottom in the buffer.
@item
-Decide on download policy. @xref{Agent Categories}
+Decide on download policy. @xref{Agent Categories}.
@item
Uhm... that's it.
you're interested in the articles anyway.
The main way to control what is to be downloaded is to create a
-@dfn{category} and then assign some (or all) groups to this category.
+@dfn{category} and then assign some (or all) groups to this category.
Gnus has its own buffer for creating and managing categories.
@menu
@item
a score rule which (generally) gives you a finer granularity when
deciding what articles to download. (Note that this @dfn{download
-score} is wholly unrelated to normal scores.)
+score} is not necessarily related to normal scores.)
@end enumerate
-A predicate consists of predicates with logical operators sprinkled in
-between.
+A predicate in its simplest form can be a single predicate such as
+@code{true} or @code{false}. These two will download every available
+article or nothing respectively. In the case of these two special
+predicates an additional score rule is superfluous.
+
+Predicates of @code{high} or @code{low} download articles in respect of
+their scores in relationship to @code{gnus-agent-high-score} and
+@code{gnus-agent-low-score} as descibed below.
+
+To gain even finer control of what is to be regarded eligible for
+download a predicate can consist of a number of predicates with logical
+operators sprinkled in between.
Perhaps some examples are in order.
Always false.
@end table
-If you want to create your own predicate function, here's what you have
-to know: The functions are called with no parameters, but the
-@code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
-useful values.
+If you want to create your own predicate function, here's what you have
+to know: The functions are called with no parameters, but the
+@code{gnus-headers} and @code{gnus-score} dynamic variables are bound to
+useful values.
+
+For example, you could decide that you don't want to download articles
+that were posted more than a certain number of days ago (e.g. posted
+more than @code{gnus-agent-expire-days} ago) you might write a function
+something along the lines of the following:
+
+@lisp
+(defun my-article-old-p ()
+ "Say whether an article is old."
+ (< (time-to-day (date-to-time (mail-header-date gnus-headers)))
+ (- (time-to-day (current-time)) gnus-agent-expire-days)))
+@end lisp
+
+with the predicate then defined as:
+
+@lisp
+(not my-article-old-p)
+@end lisp
+
+or you could append your predicate to the predefined
+@code{gnus-category-predicate-alist} in your @file{~/.gnus.el} or
+wherever. (Note: this would have to be at a point *after*
+@code{gnus-agent} has been loaded via @code{(gnus-agentize)})
+
+@lisp
+(defvar gnus-category-predicate-alist
+ (append gnus-category-predicate-alist
+ '((old . my-article-old-p))))
+@end lisp
+
+and simply specify your predicate as:
+
+@lisp
+(not old)
+@end lisp
+
+If/when using something like the above, be aware that there are many
+misconfigured systems/mailers out there and so an article's date is not
+always a reliable indication of when it was posted. Hell, some people
+just don't give a damm.
+
+
+The above predicates apply to *all* the groups which belong to the
+category. However, if you wish to have a specific predicate for an
+individual group within a category, or you're just too lazy to set up a
+new category, you can enter a group's individual predicate in it's group
+parameters like so:
+
+@lisp
+(agent-predicate . short)
+@end lisp
+
+This is the group parameter equivalent of the agent category
+default. Note that when specifying a single word predicate like this,
+the @code{agent-predicate} specification must be in dotted pair
+notation.
+
+The equivalent of the longer example from above would be:
+
+@lisp
+(agent-predicate or high (and (not low) (not long)))
+@end lisp
+
+The outer parenthesis required in the category specification are not
+entered here as, not being in dotted pair notation, the value of the
+predicate is assumed to be a list.
+
+
+Now, the syntax of the download score is the same as the syntax of
+normal score files, except that all elements that require actually
+seeing the article itself are verboten. This means that only the
+following headers can be scored on: @code{Subject}, @code{From},
+@code{Date}, @code{Message-ID}, @code{References}, @code{Chars},
+@code{Lines}, and @code{Xref}.
+
+As with predicates, the specification of the @code{download score rule}
+to use in respect of a group can be in either the category definition if
+it's to be applicable to all groups in therein, or a group's parameters
+if it's to be specific to that group.
+
+In both of these places the @code{download score rule} can take one of
+three forms:
+
+@enumerate
+@item
+Score rule
+
+This has the same syntax as a normal gnus score file except only a
+subset of scoring keywords are available as mentioned above.
+
+example:
+
+@itemize @bullet
+@item
+Category specification
+
+@lisp
+(("from"
+ ("Lars Ingebrigtsen" 1000000 nil s))
+("lines"
+ (500 -100 nil <)))
+@end lisp
+
+@item
+Group Parameter specification
+
+@lisp
+(agent-score ("from"
+ ("Lars Ingebrigtsen" 1000000 nil s))
+ ("lines"
+ (500 -100 nil <)))
+@end lisp
+
+Again, note the omission of the outermost parenthesis here.
+@end itemize
+
+@item
+Agent score file
+
+These score files must *only* contain the permitted scoring keywords
+stated above.
+
+example:
+
+@itemize @bullet
+@item
+Category specification
+
+@lisp
+("~/News/agent.SCORE")
+@end lisp
+
+or perhaps
+
+@lisp
+("~/News/agent.SCORE" "~/News/agent.group.SCORE")
+@end lisp
+
+@item
+Group Parameter specification
+
+@lisp
+(agent-score "~/News/agent.SCORE")
+@end lisp
+
+Additional score files can be specified as above. Need I say anything
+about parenthesis.
+@end itemize
+
+@item
+Use @code{normal} score files
+
+If you dont want to maintain two sets of scoring rules for a group, and
+your desired @code{downloading} criteria for a group are the same as your
+@code{reading} criteria then you can tell the agent to refer to your
+@code{normal} score files when deciding what to download.
+
+These directives in either the category definition or a group's
+parameters will cause the agent to read in all the applicable score
+files for a group, *filtering out* those those sections that do not
+relate to one of the permitted subset of scoring keywords.
+
+@itemize @bullet
+@item
+Category Specification
+
+@lisp
+file
+@end lisp
-Now, the syntax of the download score is the same as the syntax of
-normal score files, except that all elements that require actually
-seeing the article itself are verboten. This means that only the
-following headers can be scored on: @code{From}, @code{Subject},
-@code{Date}, @code{Xref}, @code{Lines}, @code{Chars}, @code{Message-ID},
-and @code{References}.
+@item
+Group Parameter specification
+@lisp
+(agent-score . file)
+@end lisp
+@end itemize
+@end enumerate
@node The Category Buffer
@subsubsection The Category Buffer
@item gnus-category-line-format
@vindex gnus-category-line-format
Format of the lines in the category buffer (@pxref{Formatting
-Variables}). Legal elements are:
+Variables}). Valid elements are:
@table @samp
@item c
@item gnus-category-mode-line-format
@vindex gnus-category-mode-line-format
-Format of the category mode line.
+Format of the category mode line (@pxref{Mode Line Formatting}).
-@item gnus-agent-short-article
-@vindex gnus-agent-short-article
+@item gnus-agent-short-article
+@vindex gnus-agent-short-article
Articles that have fewer lines than this are short. Default 100.
-@item gnus-agent-long-article
-@vindex gnus-agent-long-article
+@item gnus-agent-long-article
+@vindex gnus-agent-long-article
Articles that have more lines than this are long. Default 200.
-@item gnus-agent-low-score
-@vindex gnus-agent-low-score
+@item gnus-agent-low-score
+@vindex gnus-agent-low-score
Articles that have a score lower than this have a low score. Default
-0.
+0.
-@item gnus-agent-high-score
-@vindex gnus-agent-high-score
+@item gnus-agent-high-score
+@vindex gnus-agent-high-score
Articles that have a score higher than this have a high score. Default
-0.
+0.
@end table
@subsubsection Group Agent Commands
@table @kbd
-@item J u
+@item J u
@kindex J u (Agent Group)
@findex gnus-agent-fetch-groups
Fetch all eligible articles in the current group
@kindex J S (Agent Group)
@findex gnus-group-send-drafts
Send all sendable messages in the draft group
-(@code{gnus-agent-fetch-session}). @xref{Drafts}
+(@code{gnus-agent-fetch-session}). @xref{Drafts}.
@item J a
@kindex J a (Agent Group)
@findex gnus-agent-add-group
Add the current group to an Agent category
-(@code{gnus-agent-add-group}).
+(@code{gnus-agent-add-group}). This command understands the
+process/prefix convention (@pxref{Process/Prefix}).
+
+@item J r
+@kindex J r (Agent Group)
+@findex gnus-agent-remove-group
+Remove the current group from its category, if any
+(@code{gnus-agent-remove-group}). This command understands the
+process/prefix convention (@pxref{Process/Prefix}).
@end table
@node Agent Expiry
@subsection Agent Expiry
-@vindex gnus-agent-expiry-days
-@findex gnus-agent-expiry
-@kindex M-x gnus-agent-expiry
+@vindex gnus-agent-expire-days
+@findex gnus-agent-expire
+@kindex M-x gnus-agent-expire
+@cindex Agent expiry
+@cindex Gnus Agent expiry
+@cindex expiry
@code{nnagent} doesn't handle expiry. Instead, there's a special
-@code{gnus-agent-expiry} command that will expire all read articles that
-are older than @code{gnus-agent-expiry-days} days. It can be run
+@code{gnus-agent-expire} command that will expire all read articles that
+are older than @code{gnus-agent-expire-days} days. It can be run
whenever you feel that you're running out of space. It's not
particularly fast or efficient, and it's not a particularly good idea to
interrupt it (with @kbd{C-g} or anything else) once you've started it.
+@vindex gnus-agent-expire-all
+if @code{gnus-agent-expire-all} is non-@code{nil}, this command will
+expire all articles---unread, read, ticked and dormant. If @code{nil}
+(which is the default), only read articles are eligible for expiry, and
+unread, ticked and dormant articles will be kept indefinitely.
+
@node Outgoing Messages
@subsection Outgoing Messages
@end example
+@node Agent Caveats
+@subsection Agent Caveats
+
+The Gnus Agent doesn't seem to work like most other offline
+newsreaders. Here are some common questions that some imaginary people
+may ask:
+
+@table @dfn
+@item If I read an article while plugged, do they get entered into the
+Agent?
+
+@strong{No.}
+
+@item If I read an article while plugged, and the article already exists
+in the Agent, will it get downloaded once more?
+
+@strong{Yes.}
+
+@end table
+
+In short, when Gnus is unplugged, it only looks into the locally stored
+articles; when it's plugged, it only talks to your ISP.
+
@node Scoring
@chapter Scoring
temporary and have not been used for, say, a week, will be removed
silently to help keep the sizes of the score files down.
-@menu
+@menu
* Summary Score Commands:: Adding score entries for the current group.
* Group Score Commands:: General score commands.
* Score Variables:: Customize your scoring. (My, what terminology).
@item V s
@kindex V s (Summary)
@findex gnus-summary-set-score
-Set the score of the current article (@code{gnus-summary-set-score}).
+Set the score of the current article (@code{gnus-summary-set-score}).
@item V S
@kindex V S (Summary)
@findex gnus-summary-current-score
Display the score of the current article
-(@code{gnus-summary-current-score}).
+(@code{gnus-summary-current-score}).
@item V t
@kindex V t (Summary)
@findex gnus-score-find-trace
Display all score rules that have been used on the current article
-(@code{gnus-score-find-trace}).
+(@code{gnus-score-find-trace}).
@item V R
@kindex V R (Summary)
around with your score files behind Gnus' back and want to see the
effect you're having.
-@item V a
-@kindex V a (Summary)
-@findex gnus-summary-score-entry
-Add a new score entry, and allow specifying all elements
-(@code{gnus-summary-score-entry}).
-
@item V c
@kindex V c (Summary)
@findex gnus-score-change-score-file
Make a different score file the current
-(@code{gnus-score-change-score-file}).
+(@code{gnus-score-change-score-file}).
@item V e
@kindex V e (Summary)
@kindex V C (Summary)
@findex gnus-score-customize
Customize a score file in a visually pleasing manner
-(@code{gnus-score-customize}).
+(@code{gnus-score-customize}).
@end table
The keystrokes for actually making score entries follow a very regular
pattern, so there's no need to list all the commands. (Hundreds of
-them.)
+them.)
@findex gnus-summary-increase-score
@findex gnus-summary-lower-score
@enumerate
@item
The first key is either @kbd{I} (upper case i) for increasing the score
-or @kbd{L} for lowering the score.
+or @kbd{L} for lowering the score.
@item
The second key says what header you want to score on. The following
keys are available:
Score on the subject line.
@item x
-Score on the Xref line---i.e., the cross-posting line.
+Score on the @code{Xref} line---i.e., the cross-posting line.
-@item t
-Score on thread---the References line.
+@item r
+Score on the @code{References} line.
@item d
Score on the date.
Score on the number of lines.
@item i
-Score on the Message-ID.
+Score on the @code{Message-ID} header.
@item f
-Score on followups.
+Score on followups---this matches the author name, and adds scores to
+the followups to this author.
@item b
Score on the body.
@item h
Score on the head.
+
+@item t
+Score on thead.
+
@end table
@item
@table @code
-@item strings
+@item strings
@table @kbd
Before date.
@item a
-At date.
+After date.
@item n
This date.
@end table
@end table
-@item
+@item
The fourth and final key says whether this is a temporary (i.e., expiring)
score entry, or a permanent (i.e., non-expiring) score entry, or whether
it is to be done immediately, without adding to the score file.
@findex gnus-score-flush-cache
Gnus maintains a cache of score alists to avoid having to reload them
all the time. This command will flush the cache
-(@code{gnus-score-flush-cache}).
+(@code{gnus-score-flush-cache}).
@end table
@findex gnus-batch-score
@cindex batch scoring
@example
-$ emacs -batch -l ~/.emacs -l gnus -f gnus-batch-score
+$ emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-batch-score
@end example
@item gnus-score-find-score-files-function
@vindex gnus-score-find-score-files-function
Function used to find score files for the current group. This function
-is called with the name of the group as the argument.
+is called with the name of the group as the argument.
Predefined functions available are:
@table @code
@item gnus-score-find-bnews
@findex gnus-score-find-bnews
Apply all score files that match, using bnews syntax. This is the
-default. If the current group is @samp{gnu.emacs.gnus}, for instance,
+default. If the current group is @samp{gnu.emacs.gnus}, for instance,
@file{all.emacs.all.SCORE}, @file{not.alt.all.SCORE} and
@file{gnu.all.SCORE} would all apply. In short, the instances of
@samp{all} in the score file names are translated into @samp{.*}, and
then a regexp match is done.
This means that if you have some score entries that you want to apply to
-all groups, then you put those entries in the @file{all.SCORE} file.
+all groups, then you put those entries in the @file{all.SCORE} file.
The score files are applied in a semi-random order, although Gnus will
try to apply the more general score files before the more specific score
non-matching entries will become too old while matching entries will
stay fresh and young.) However, if you set this variable to @code{nil},
even matching entries will grow old and will have to face that oh-so
-grim reaper.
+grim reaper.
@item gnus-score-after-write-file-function
@vindex gnus-score-after-write-file-function
score entry has one to four elements.
@enumerate
-@item
+@item
The first element is the @dfn{match element}. On most headers this will
be a string, but on the Lines and Chars headers, this must be an
-integer.
+integer.
-@item
+@item
If the second element is present, it should be a number---the @dfn{score
element}. This number should be an integer in the neginf to posinf
interval. This number is added to the score of the article if the match
@code{gnus-score-interactive-default-score} number will be used
instead. This is 1000 by default.
-@item
+@item
If the third element is present, it should be a number---the @dfn{date
element}. This date says when the last time this score entry matched,
which provides a mechanism for expiring the score entries. It this
element is not present, the score entry is permanent. The date is
represented by the number of days since December 31, 1 BCE.
-@item
+@item
If the fourth element is present, it should be a symbol---the @dfn{type
element}. This element specifies what function should be used to see
whether this score entry matches the article. What match types that can
@item Lines, Chars
These two headers use different match types: @code{<}, @code{>},
-@code{=}, @code{>=} and @code{<=}. When matching on @code{Lines}, be
-careful because some backends (like @code{nndir}) do not generate
-@code{Lines} header, so every article ends up being marked as having 0
-lines. This can lead to strange results if you happen to lower score of
-the articles with few lines.
+@code{=}, @code{>=} and @code{<=}.
+
+These predicates are true if
+
+@example
+(PREDICATE HEADER MATCH)
+@end example
+
+evaluates to non-@code{nil}. For instance, the advanced match
+@code{("lines" 4 <)} (@pxref{Advanced Scoring}) will result in the
+following form:
+
+@lisp
+(< header-value 4)
+@end lisp
+
+Or to put it another way: When using @code{<} on @code{Lines} with 4 as
+the match, we get the score added if the article has less than 4 lines.
+(It's easy to get confused and think it's the other way around. But
+it's not. I think.)
+
+When matching on @code{Lines}, be careful because some backends (like
+@code{nndir}) do not generate @code{Lines} header, so every article ends
+up being marked as having 0 lines. This can lead to strange results if
+you happen to lower score of the articles with few lines.
@item Date
For the Date header we have three kinda silly match types:
decrease the score of followups to the articles of some known
trouble-maker. Uses the same match types as the @code{From} header
uses. (Using this match key will lead to creation of @file{ADAPT}
-files.)
+files.)
@item Thread
This match key works along the same lines as the @code{Followup} match
@item exclude-files
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.
+other.
@item eval
The value of this entry will be @code{eval}el. This element will be
-ignored when handling global score files.
+ignored when handling global score files.
@item read-only
Read-only score files will not be updated or saved. Global score files
not want adaptive scoring. If you only want adaptive scoring in a few
groups, you'd set @code{gnus-use-adaptive-scoring} to @code{nil}, and
insert @code{(adapt t)} in the score files of the groups where you want
-it.
+it.
@item adapt-file
All adaptive score entries will go to the file named by this entry. It
You normally enter all scoring commands from the summary buffer, but you
might feel the urge to edit them by hand as well, so we've supplied you
-with a mode for that.
+with a mode for that.
It's simply a slightly customized @code{emacs-lisp} mode, with these
additional commands:
@kindex C-c C-c (Score)
@findex gnus-score-edit-done
Save the changes you have made and return to the summary buffer
-(@code{gnus-score-edit-done}).
+(@code{gnus-score-edit-done}).
@item C-c C-d
@kindex C-c C-d (Score)
The adaptive score files are saved in an unformatted fashion. If you
intend to read one of these files, you want to @dfn{pretty print} it
first. This command (@code{gnus-score-pretty-print}) does that for
-you.
+you.
@end table
To take @code{gnus-del-mark} as an example---this alist says that all
articles that have that mark (i.e., are marked with @samp{D}) will have a
score entry added to lower based on the @code{From} header by -4, and
-lowered by @code{Subject} by -1. Change this to fit your prejudices.
+lowered by @code{Subject} by -1. Change this to fit your prejudices.
If you have marked 10 articles with the same subject with
@code{gnus-del-mark}, the rule for that mark will be applied ten times.
@code{chars} and @code{date}. In addition, you can score on
@code{followup}, which will create an adaptive score entry that matches
on the @code{References} header using the @code{Message-ID} of the
-current article, thereby matching the following thread.
+current article, thereby matching the following thread.
You can also score on @code{thread}, which will try to score all
articles that appear in a thread. @code{thread} matches uses a
After using adaptive scoring for a week or so, Gnus should start to
become properly trained and enhance the authors you like best, and kill
-the authors you like least, without you having to say so explicitly.
+the authors you like least, without you having to say so explicitly.
You can control what groups the adaptive scoring is to be performed on
by using the score files (@pxref{Score File Format}). This will also
each instance of a word should add given a mark.
@lisp
-(setq gnus-default-adaptive-word-score-alist
+(setq gnus-default-adaptive-word-score-alist
`((,gnus-read-mark . 30)
(,gnus-catchup-mark . -10)
(,gnus-killed-mark . -20)
word scoring process will never bring down the score of an article to
below this number. The default is @code{nil}.
+@vindex gnus-adaptive-word-no-group-words
+If @code{gnus-adaptive-word-no-group-words} is set to @code{t}, gnus
+won't adaptively word score any of the words in the group name. Useful
+for groups like @samp{comp.editors.emacs}, where most of the subject
+lines contain the word @samp{emacs}.
+
After using this scheme for a while, it might be nice to write a
@code{gnus-psychoanalyze-user} command to go through the rules and see
what words you like and what words you don't like. Or perhaps not.
Note that the adaptive word scoring thing is highly experimental and is
likely to change in the future. Initial impressions seem to indicate
that it's totally useless as it stands. Some more work (involving more
-rigorous statistical methods) will have to be done to make this useful.
+rigorous statistical methods) will have to be done to make this useful.
@node Home Score File
@enumerate
@item
A string. Then this file will be used as the home score file for all
-groups.
+groups.
@item
A function. The result of this function will be used as the home score
file. The function will be called with the name of the group as the
-parameter.
+parameter.
@item
A list. The elements in this list can be:
@enumerate
-@item
+@item
@var{(regexp file-name)}. If the @var{regexp} matches the group name,
the @var{file-name} will will be used as the home score file.
-@item
+@item
A function. If the function returns non-nil, the result will be used as
the home score file.
-@item
+@item
A string. Use the string as the home score file.
@end enumerate
If you want to use @file{gnu.SCORE} for all @samp{gnu} groups and
@file{rec.SCORE} for all @samp{rec} groups (and so on), you can say:
+@findex gnus-hierarchial-home-score-file
@lisp
(setq gnus-home-score-file
'gnus-hierarchial-home-score-file)
@end lisp
This is a ready-made function provided for your convenience.
+Other functions include
+
+@table @code
+@item gnus-current-home-score-file
+@findex gnus-current-home-score-file
+Return the ``current'' regular score file. This will make scoring
+commands add entry to the ``innermost'' matching score file.
+
+@end table
If you want to have one score file for the @samp{emacs} groups and
another for the @samp{comp} groups, while letting all other groups use
@lisp
(setq gnus-home-score-file
;; All groups that match the regexp "\\.emacs"
- '("\\.emacs" "emacs.SCORE")
- ;; All the comp groups in one score file
- ("^comp" "comp.SCORE"))
+ '(("\\.emacs" "emacs.SCORE")
+ ;; All the comp groups in one score file
+ ("^comp" "comp.SCORE")))
@end lisp
-
+
@vindex gnus-home-adapt-file
@code{gnus-home-adapt-file} works exactly the same way as
@code{gnus-home-score-file}, but says what the home adaptive score file
@item gnus-score-followup-article
@findex gnus-score-followup-article
This will add a score to articles that directly follow up your own
-article.
+article.
@item gnus-score-followup-thread
@findex gnus-score-followup-thread
@vindex message-sent-hook
These two functions are both primarily meant to be used in hooks like
-@code{message-sent-hook}.
+@code{message-sent-hook}.
If you look closely at your own @code{Message-ID}, you'll notice that
the first two or three characters are always the same. Here's two of
-mine:
+mine:
@example
<x6u3u47icf.fsf@@eyesore.no>
So ``my'' ident on this machine is @samp{x6}. This can be
exploited---the following rule will raise the score on all followups to
-myself:
+myself:
@lisp
("references"
and stick with it in each score file. If you use any two, each article
will be fetched @emph{twice}. If you want to match a bit on the
@code{Head} and a bit on the @code{Body}, just use @code{All} for all
-the matches.
+the matches.
@item Marking as read
You will probably want to mark articles that has a score below a certain
@lisp
((mark -100))
@end lisp
-You may also consider doing something similar with @code{expunge}.
+You may also consider doing something similar with @code{expunge}.
@item Negated character classes
If you say stuff like @code{[^abcd]*}, you may get unexpected results.
premises! Yay! The net is saved!
Here are some tips for the would-be retro-moderator, off the top of my
-head:
+head:
@itemize @bullet
-@item
-Articles heavily crossposted are probably junk.
+@item
+Articles heavily crossposted are probably junk.
@item
To lower a single inappropriate article, lower by @code{Message-ID}.
@item
-Particularly brilliant authors can be raised on a permanent basis.
+Particularly brilliant authors can be raised on a permanent basis.
@item
Authors that repeatedly post off-charter for the group can safely be
lowered out of existence.
Set the @code{mark} and @code{expunge} atoms to obliterate the nastiest
articles completely.
-@item
+@item
Use expiring score entries to keep the size of the file down. You
should probably have a long expiry period, though, as some sites keep
old articles for a long time.
Other programs use a totally different kill file syntax. If Gnus
encounters what looks like a @code{rn} kill file, it will take a stab at
-interpreting it.
+interpreting it.
Two summary functions for editing a GNUS kill file:
@item gnus-kill-save-kill-file
If this variable is non-@code{nil}, Gnus will save the
kill file after processing, which is necessary if you use expiring
-kills.
+kills.
@item gnus-apply-kill-hook
@vindex gnus-apply-kill-hook
The kill to score conversion package isn't included in Gnus by default.
You can fetch it from
-@file{http://www.ifi.uio.no/~larsi/ding-other/gnus-kill-to-score}.
+@file{http://www.stud.ifi.uio.no/~larsi/ding-other/gnus-kill-to-score}.
If your old kill files are very complex---if they contain more
non-@code{gnus-kill} forms than not, you'll have to convert them by
hand. Or just let them be as they are. Gnus will still use them as
-before.
+before.
@node GroupLens
@item grouplens-newsgroups
@vindex grouplens-newsgroups
-A list of groups that you want to get GroupLens predictions for.
+A list of groups that you want to get GroupLens predictions for.
@end table
@table @code
@item prediction-spot
The higher the prediction, the further to the right an @samp{*} is
-displayed.
+displayed.
@item confidence-interval
A numeric confidence interval.
prediction value by this number to arrive at the effective score. The
default is 0.
-@item grouplens-score-scale-factor
+@item grouplens-score-scale-factor
This variable allows the user to magnify the effect of GroupLens scores.
The scale factor is applied after the offset. The default is 1.
This logical operator will evaluate each of its arguments until it finds
one that evaluates to @code{false}, and then it'll stop. If all arguments
evaluate to @code{true} values, then this operator will return
-@code{true}.
+@code{true}.
@item |
@itemx or
when he's talking about Gnus:
@example
-((&
+((&
("from" "Lars Ingebrigtsen")
("subject" "Gnus"))
1000)
Quite simple, huh?
-When he writes long articles, he sometimes has something nice to say:
+When he writes long articles, he sometimes has something nice to say:
@example
-((&
+((&
("from" "Lars Ingebrigtsen")
(|
("subject" "Gnus")
@example
(1-
- (&
+ (&
("from" "Lars")
("subject" "Gnus")))
@end example
@vindex gnus-decay-scores
@findex gnus-decay-score
-@vindex gnus-score-decay-function
+@vindex gnus-decay-score-function
Gnus provides a mechanism for decaying scores to help with this problem.
When score files are loaded and @code{gnus-decay-scores} is
non-@code{nil}, Gnus will run the score files through the decaying
mechanism thereby lowering the scores of all non-permanent score rules.
-The decay itself if performed by the @code{gnus-score-decay-function}
+The decay itself if performed by the @code{gnus-decay-score-function}
function, which is @code{gnus-decay-score} by default. Here's the
definition of that function:
@lisp
(defun gnus-decay-score (score)
- "Decay SCORE according to `gnus-score-decay-constant' and `gnus-score-decay-scale'."
+ "Decay SCORE.
+This is done according to `gnus-score-decay-constant'
+and `gnus-score-decay-scale'."
(floor
(- score
(* (if (< score 0) 1 -1)
* Moderation:: What to do if you're a moderator.
* XEmacs Enhancements:: There are more pictures and stuff under XEmacs.
* Fuzzy Matching:: What's the big fuzz?
-* Thwarting Email Spam:: A how-to on avoiding unsolited commercial email.
+* Thwarting Email Spam:: A how-to on avoiding unsolicited commercial email.
* Various Various:: Things that are really various.
@end menu
@item gnus-interactive-exit
@vindex gnus-interactive-exit
Require confirmation before exiting Gnus. This variable is @code{t} by
-default.
+default.
@end table
@cindex symbolic prefixes
Quite a lot of Emacs commands react to the (numeric) prefix. For
-instance, @kbd{C-u 4 C-f} moves point four charaters forward, and
+instance, @kbd{C-u 4 C-f} moves point four characters forward, and
@kbd{C-u 9 0 0 I s s p} adds a permanent @code{Subject} substring score
rule of 900 to the current article.
@section Formatting Variables
@cindex formatting variables
-Throughout this manual you've probably noticed lots of variables called things like @code{gnus-group-line-format} and
+Throughout this manual you've probably noticed lots of variables called
+things like @code{gnus-group-line-format} and
@code{gnus-summary-mode-line-format}. These control how Gnus is to
output lines in the various buffers. There's quite a lot of them.
Fortunately, they all use the same syntax, so there's not that much to
Here's an example format spec (from the group buffer): @samp{%M%S%5y:
%(%g%)\n}. We see that it is indeed extremely ugly, and that there are
-lots of percentages everywhere.
+lots of percentages everywhere.
-@menu
+@menu
* Formatting Basics:: A formatting variable is basically a format string.
+* Mode Line Formatting:: Some rules about mode line formatting variables.
* Advanced Formatting:: Modifying output in various ways.
* User-Defined Specs:: Having Gnus call your own functions.
* Formatting Fonts:: Making the formatting look colorful and nice.
Gnus includes a command to help you while creating your own format
specs. @kbd{M-x gnus-update-format} will @code{eval} the current form,
update the spec in question and pop you to a buffer where you can
-examine the resulting lisp code to be run to generate the line.
+examine the resulting lisp code to be run to generate the line.
less than 4 characters wide.
+@node Mode Line Formatting
+@subsection Mode Line Formatting
+
+Mode line formatting variables (e.g.,
+@code{gnus-summary-mode-line-format}) follow the same rules as other,
+buffer line oriented formatting variables (@pxref{Formatting Basics})
+with the following two differences:
+
+@enumerate
+
+@item
+There must be no newline (@samp{\n}) at the end.
+
+@item
+The special @samp{%%b} spec can be used to display the buffer name.
+Well, it's no spec at all, really---@samp{%%} is just a way to quote
+@samp{%} to allow it to pass through the formatting machinery unmangled,
+so that Emacs receives @samp{%b}, which is something the Emacs mode line
+display interprets to mean ``show the buffer name''. For a full list of
+mode line specs Emacs understands, see the documentation of the
+@code{mode-line-format} variable.
+
+@end enumerate
+
+
@node Advanced Formatting
@subsection Advanced Formatting
@item max-right
Cut off characters from the right until it reaches the specified
-length.
+length.
@item cut
@itemx cut-left
Cut off the specified number of characters from the right.
@item ignore
-Return an empty string if the field is equal to the specified value.
+Return an empty string if the field is equal to the specified value.
@item form
Use the specified form as the field value when the @samp{@@} spec is
-used.
+used.
@end table
Let's take an example. The @samp{%o} spec in the summary mode lines
than 6 characters to make it look nice in columns.)
Ignoring is done first; then cutting; then maxing; and then as the very
-last operation, padding.
+last operation, padding.
If you use lots of these advanced thingies, you'll find that Gnus gets
quite slow. This can be helped enormously by running @kbd{M-x
gnus-compile} when you are satisfied with the look of your lines.
-@xref{Compilation}.
+@xref{Compilation}.
@node User-Defined Specs
highlighted (with @code{gnus-mouse-face}) when you put the mouse pointer
over it.
-Text inside the @samp{%[} and @samp{%]} specifiers will have their
+Text inside the @samp{%@{} and @samp{%@}} specifiers will have their
normal faces set using @code{gnus-face-0}, which is @code{bold} by
-default. If you say @samp{%1[}, you'll get @code{gnus-face-1} instead,
+default. If you say @samp{%1@{}, you'll get @code{gnus-face-1} instead,
and so on. Create as many faces as you wish. The same goes for the
@code{mouse-face} specs---you can say @samp{%3(hello%)} to have
@samp{hello} mouse-highlighted with @code{gnus-mouse-face-3}.
+Text inside the @samp{%<} and @samp{%>} specifiers will get the special
+@code{balloon-help} property set to @code{gnus-balloon-face-0}. If you say
+@samp{%1<}, you'll get @code{gnus-balloon-face-1} and so on. The
+@code{gnus-balloon-face-*} variables should be either strings or
+symbols naming functions that return a string. Under @code{balloon-help-mode},
+when the mouse passes over text with this property set, a balloon window
+will appear and display the string. Please refer to the doc string of
+@code{balloon-help-mode} for more information on this.
+
Here's an alternative recipe for the group buffer:
@lisp
(setq gnus-face-1 'bold)
(setq gnus-face-3 'italic)
-;; We want the article count to be in
-;; a bold and green face. So we create
+;; We want the article count to be in
+;; a bold and green face. So we create
;; a new face called `my-green-bold'.
(copy-face 'bold 'my-green-bold)
;; Set the color.
(setq gnus-face-2 'my-green-bold)
;; Set the new & fancy format.
-(setq gnus-group-line-format
+(setq gnus-group-line-format
"%M%S%3@{%5y%@}%2[:%] %(%1@{%g%@}%)\n")
@end lisp
other windows and occupy the entire Emacs screen by itself. It is
@code{t} by default.
+Setting this variable to @code{nil} kinda works, but there are
+glitches. Use at your own peril.
+
@vindex gnus-buffer-configuration
@code{gnus-buffer-configuration} describes how much space each Gnus
buffer should be given. Here's an excerpt of this variable:
@lisp
((group (vertical 1.0 (group 1.0 point)
(if gnus-carpal (group-carpal 4))))
- (article (vertical 1.0 (summary 0.25 point)
+ (article (vertical 1.0 (summary 0.25 point)
(article 1.0))))
@end lisp
size spec per split.
Point will be put in the buffer that has the optional third element
-@code{point}.
+@code{point}. In a @code{frame} split, the last subsplit having a leaf
+split where the tag @code{frame-focus} is a member (i.e. is the third or
+fourth element in the list, depending on whether the @code{point} tag is
+present) gets focus.
Here's a more complicated example:
(article 1.0)))
@end lisp
-If the size spec is an integer instead of a floating point number,
+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.
Not complicated enough for you? Well, try this on for size:
@lisp
-(article (horizontal 1.0
+(article (horizontal 1.0
(vertical 0.5
(group 1.0)
(gnus-carpal 4))
@end lisp
Whoops. Two buffers with the mystery 100% tag. And what's that
-@code{horizontal} thingie?
+@code{horizontal} thingie?
If the first element in one of the split is @code{horizontal}, Gnus will
split the window horizontally, giving you two windows side-by-side.
frame = "(frame " size *split ")"
horizontal = "(horizontal " size *split ")"
vertical = "(vertical " size *split ")"
-buffer = "(" buffer-name " " size *[ "point" ] ")"
+buffer = "(" buffer-name " " size *[ "point" ] *[ "frame-focus"] ")"
size = number | frame-params
buffer-name = group | article | summary ...
@end example
The limitations are that the @code{frame} split can only appear as the
top-level split. @var{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 @code{vertical} and @code{horizontal} splits.
+may contain any number of @code{vertical} and @code{horizontal} splits.
@vindex gnus-window-min-width
@vindex gnus-window-min-height
look straight away, without going through the normal Gnus channels.
Play with it until you're satisfied, and then use
@code{gnus-add-configuration} to add your new creation to the buffer
-configuration list.
+configuration list.
@lisp
(gnus-configure-frame
(gnus-configure-frame
'(frame 1.0
(vertical 1.0
- (summary 0.25 point)
+ (summary 0.25 point frame-focus)
(article 1.0))
(vertical ((height . 5) (width . 15)
(user-position . t)
Reference Manual}. Under XEmacs, a frame property list will be
accepted, too---for instance, @code{(height 5 width 15 left -1 top 1)}
is such a plist.
-
-Here's a list of all possible keys for
-@code{gnus-buffer-configuration}:
-
-@code{group}, @code{summary}, @code{article}, @code{server},
-@code{browse}, @code{message}, @code{pick}, @code{info},
-@code{summary-faq}, @code{edit-group}, @code{edit-server},
-@code{edit-score}, @code{post}, @code{reply}, @code{forward},
-@code{reply-yank}, @code{mail-bounce}, @code{draft}, @code{pipe},
-@code{bug}, @code{compose-bounce}, and @code{score-trace}.
+The list of all possible keys for @code{gnus-buffer-configuration} can
+be found in its default value.
Note that the @code{message} key is used for both
@code{gnus-group-mail} and @code{gnus-summary-mail-other-window}. If
(group 1.0)))))
@end lisp
+One common desire for a multiple frame split is to have a separate frame
+for composing mail and news while leaving the original frame intact. To
+accomplish that, something like the following can be done:
+
+@lisp
+(message (frame 1.0
+ (if (not (buffer-live-p gnus-summary-buffer))
+ (car (cdr (assoc 'group gnus-buffer-configuration)))
+ (car (cdr (assoc 'summary gnus-buffer-configuration))))
+ (vertical ((user-position . t) (top . 1) (left . 1)
+ (name . "Message"))
+ (message 1.0 point))))
+@end lisp
+
@findex gnus-add-configuration
Since the @code{gnus-buffer-configuration} variable is so long and
complicated, there's a function you can use to ease changing the config
``right'' window configuration, you can set
@code{gnus-always-force-window-configuration} to non-@code{nil}.
+If you're using tree displays (@pxref{Tree Display}), and the tree
+window is displayed vertically next to another window, you may also want
+to fiddle with @code{gnus-tree-minimize-window} to avoid having the
+windows resized.
+
@node Faces and Fonts
@section Faces and Fonts
Fiddling with fonts and faces used to be very difficult, but these days
it is very simple. You simply say @kbd{M-x customize-face}, pick out
the face you want to alter, and alter it via the standard Customize
-interface.
+interface.
@node Compilation
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.)
+course.)
To help with this, you can run @kbd{M-x gnus-compile} after you've
fiddled around with the variables and feel that you're (kind of)
@end lisp
Here's a handler that scans for PGP headers every hour when Emacs is
-idle:
+idle:
@lisp
(gnus-demon-scan-pgp 60 t)
If @var{idle} is a number and @var{time} is @code{nil}, the function
will be called once every time Emacs has been idle for @var{idle}
-minutes.
+minutes.
And if @var{time} is a string, it should look like @samp{07:31}, and
the function will then be called once every day somewhere near that
seconds. This is 60 by default. If you change that variable,
all the timings in the handlers will be affected.)
-@vindex gnus-use-demon
-To set the whole thing in motion, though, you have to set
-@code{gnus-use-demon} to @code{t}.
-
So, if you want to add a handler, you could put something like this in
your @file{.gnus} file:
@findex gnus-demon-add-disconnection
Some ready-made functions to do this have been created:
@code{gnus-demon-add-nocem}, @code{gnus-demon-add-disconnection},
-@code{gnus-demon-add-nntp-close-connection},
+@code{gnus-demon-add-nntp-close-connection},
@code{gnus-demon-add-scan-timestamps}, @code{gnus-demon-add-rescan}, and
@code{gnus-demon-add-scanmail}. Just put those functions in your
@file{.gnus} if you want those abilities.
run @code{gnus-demon-init} to make the changes take hold. To cancel all
daemons, you can use the @code{gnus-demon-cancel} function.
-Note that adding daemons can be pretty naughty if you overdo it. Adding
+Note that adding daemons can be pretty naughty if you over do 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.
@cindex spam
@dfn{Spamming} is posting the same article lots and lots of times.
-Spamming is bad. Spamming is evil.
+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 @dfn{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.
+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
messages, which are distributed in the @samp{alt.nocem.misc} newsgroup.
Gnus can read and parse the messages in this group automatically, and
-this will make spam disappear.
+this will make spam disappear.
There are some variables to customize, of course:
@item gnus-use-nocem
@vindex gnus-use-nocem
Set this variable to @code{t} to set the ball rolling. It is @code{nil}
-by default.
+by default.
@item gnus-nocem-groups
@vindex gnus-nocem-groups
Gnus will look for NoCeM messages in the groups in this list. The
default is @code{("news.lists.filters" "news.admin.net-abuse.bulletins"
-"alt.nocem.misc" "news.admin.net-abuse.announce")}.
+"alt.nocem.misc" "news.admin.net-abuse.announce")}.
@item gnus-nocem-issuers
@vindex gnus-nocem-issuers
@item Automoose-1
@cindex CancelMoose[tm]
The CancelMoose[tm] on autopilot. The CancelMoose[tm] is reputed to be
-Norwegian, and was the person(s) who invented NoCeM.
+Norwegian, and was the person(s) who invented NoCeM.
@item jem@@xpat.com;
@cindex Jem
@item gnus-nocem-directory
@vindex gnus-nocem-directory
This is where Gnus will store its NoCeM cache files. The default is
-@file{~/News/NoCeM/}.
+@file{~/News/NoCeM/}.
@item gnus-nocem-expiry-wait
@vindex gnus-nocem-expiry-wait
is used if @code{gnus-use-undo} is non-@code{nil}, which is the
default. The @kbd{M-C-_} key performs the @code{gnus-undo} command
command, which should feel kinda like the normal Emacs @code{undo}
-command.
+command.
@node Moderation
supposed to work:
@enumerate
-@item
+@item
You split your incoming mail by matching on
@samp{Newsgroups:.*rec.zoofle}, which will put all the to-be-posted
articles in some mail group---for instance, @samp{nnml:rec.zoofle}.
@end iflatex
@end iftex
-@quotation
+@quotation
@dfn{Picons} is short for ``personal icons''. They're small,
constrained images used to represent users and domains on the net,
organized into databases so that the appropriate image for a given
@vindex gnus-picons-piconsearch-url
If you have a permanent connection to the Internet you can use Steve
Kinzler's Picons Search engine by setting
-@code{gnus-picons-piconsearch-url} to the string
+@code{gnus-picons-piconsearch-url} to the string @*
@file{http://www.cs.indiana.edu/picons/search.html}.
@vindex gnus-picons-database
Otherwise you need a local copy of his database. For instructions on
-obtaining and installing the picons databases, point your Web browser at
+obtaining and installing the picons databases, point your Web browser at @*
@file{http://www.cs.indiana.edu/picons/ftp/index.html}. Gnus expects
picons to be installed into a location pointed to by
@code{gnus-picons-database}.
@lisp
(setq gnus-use-picons t)
-(add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
-(add-hook 'gnus-article-display-hook 'gnus-picons-article-display-x-face)
+(setq gnus-treat-display-picons t)
@end lisp
and make sure @code{gnus-picons-database} points to the directory
Alternatively if you want to use the web piconsearch engine add this:
@lisp
-(setq gnus-picons-piconsearch-url "http://www.cs.indiana.edu:800/piconsearch")
+(setq gnus-picons-piconsearch-url
+ "http://www.cs.indiana.edu:800/piconsearch")
@end lisp
@node Hard Picons
-@subsubsection Hard Picons
+@subsubsection Hard Picons
@iftex
@iflatex
feature, you need to select where to get the picons from, and where to
display them.
-@table @code
+@table @code
@item gnus-picons-database
@vindex gnus-picons-database
this is @code{nil} 'the default), then picons are fetched from local
database indicated by @code{gnus-picons-database}.
-@item gnus-picons-display-where
-@vindex gnus-picons-display-where
+@item gnus-picons-display-where
+@vindex gnus-picons-display-where
Where the picon images should be displayed. It is @code{picons} by
default (which by default maps to the buffer @samp{*Picons*}). Other
valid places could be @code{article}, @code{summary}, or
@item gnus-picons-group-excluded-groups
@vindex gnus-picons-group-excluded-groups
Groups that are matched by this regexp won't have their group icons
-displayed.
+displayed.
@end table
functions to the appropriate hooks so these pictures will get displayed
at the right time.
-@vindex gnus-article-display-hook
@vindex gnus-picons-display-where
@table @code
@item gnus-article-display-picons
@findex gnus-article-display-picons
Looks up and displays the picons for the author and the author's domain
-in the @code{gnus-picons-display-where} buffer. Should be added to the
-@code{gnus-article-display-hook}.
+in the @code{gnus-picons-display-where} buffer.
@item gnus-picons-article-display-x-face
@findex gnus-article-display-picons
-Decodes and displays the X-Face header if present. This function
-should be added to @code{gnus-article-display-hook}.
+Decodes and displays the X-Face header if present.
@end table
-Note: You must append them to the hook, so make sure to specify 't'
-for the append flag of @code{add-hook}:
-
-@lisp
-(add-hook 'gnus-article-display-hook 'gnus-article-display-picons t)
-@end lisp
@node Picon Useless Configuration
Ordered list of suffixes on picon file names to try. Defaults to
@code{("xpm" "gif" "xbm")} minus those not builtin your XEmacs.
+@item gnus-picons-setup-hook
+@vindex gnus-picons-setup-hook
+Hook run in the picon buffer, if that is displayed.
+
@item gnus-picons-display-article-move-p
@vindex gnus-picons-display-article-move-p
Whether to move point to first empty line when displaying picons. This
has only an effect if `gnus-picons-display-where' has value `article'.
+If @code{nil}, display the picons in the @code{From} and
+@code{Newsgroups} lines. This is the defailt.
+
@item gnus-picons-clear-cache-on-shutdown
@vindex gnus-picons-clear-cache-on-shutdown
Whether to clear the picons cache when exiting gnus. Gnus caches every
@file{.gnus.el} file:
@lisp
-(add-hook 'gnus-article-display-hook 'gnus-smiley-display t)
+(setq gnus-treat-display-smiley t)
@end lisp
Smiley maps text smiley faces---@samp{:-)}, @samp{:-=}, @samp{:-(} and
@item gnus-xmas-logo-color-style
@vindex gnus-xmas-logo-color-style
This is the key used to look up the color in the alist described above.
-Legal values include @code{flame}, @code{pine}, @code{moss},
+Valid values include @code{flame}, @code{pine}, @code{moss},
@code{irish}, @code{sky}, @code{tin}, @code{velvet}, @code{grape},
@code{labia}, @code{berry}, @code{neutral}, and @code{september}.
@item gnus-xmas-modeline-glyph
@vindex gnus-xmas-modeline-glyph
A glyph displayed in all Gnus mode lines. It is a tiny gnu head by
-default.
+default.
@iftex
@iflatex
@cindex fuzzy matching
Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
-things like scoring, thread gathering and thread comparison.
+things like scoring, thread gathering and thread comparison.
As opposed to regular expression matching, fuzzy matching is very fuzzy.
It's so fuzzy that there's not even a definition of what @dfn{fuzziness}
false pretenses. I press @kbd{g} and Gnus merrily informs me that I
have 10 new emails. I say ``Golly gee! Happy is me!'' and select the
mail group, only to find two pyramid schemes, seven advertisements
-(``New! Miracle tonic for growing full, lustrouos hair on your toes!'')
+(``New! Miracle tonic for growing full, lustrous hair on your toes!'')
and one mail asking me to repent and find some god.
This is annoying.
In addition, many mail spammers talk directly to your @code{smtp} server
and do not include your email address explicitly in the @code{To}
header. Why they do this is unknown---perhaps it's to thwart this
-twarting scheme? In any case, this is trivial to deal with---you just
+thwarting scheme? In any case, this is trivial to deal with---you just
put anything not addressed to you in the @samp{spam} group by ending
your fancy split rule in this way:
each unsolicited commercial email---at your leisure.
If you are also a lazy net citizen, you will probably prefer complaining
-automatically with the @file{gnus-junk.el} package, availiable FOR FREE
-at @file{<URL:http://stud2.tuwien.ac.at/~e9426626/gnus-junk.html>}.
+automatically with the @file{gnus-junk.el} package, available FOR FREE
+at @* @file{<URL:http://stud2.tuwien.ac.at/~e9426626/gnus-junk.html>}.
Since most e-mail spam is sent automatically, this may reconcile the
cosmic balance somewhat.
This works for me. It allows people an easy way to contact me (they can
just press @kbd{r} in the usual way), and I'm not bothered at all with
spam. It's a win-win situation. Forging @code{From} headers to point
-to non-existant domains is yucky, in my opinion.
+to non-existent domains is yucky, in my opinion.
@node Various Various
which defaults to the @samp{SAVEDIR} environment variable, or
@file{~/News/} if that variable isn't set.
+Note that Gnus is mostly loaded when the @file{.gnus.el} file is read.
+This means that other directory variables that are initialized from this
+variable won't be set properly if you set this variable in
+@file{.gnus.el}. Set this variable in @file{.emacs} instead.
+
@item gnus-default-directory
@vindex gnus-default-directory
Not related to the above variable at all---this variable says what the
variable is @code{nil}, there is no upper read bound. If it is
@code{t}, the backends won't try to read the articles piece by piece,
but read the entire articles. This makes sense with some versions of
-@code{ange-ftp} or @code{efs}.
+@code{ange-ftp} or @code{efs}.
@item nnheader-head-chop-length
@vindex nnheader-head-chop-length
This variable (default 2048) says how big a piece of each article to
read when doing the operation described above.
-@item nnheader-file-name-translation-alist
-@vindex nnheader-file-name-translation-alist
+@item nnheader-file-name-translation-alist
+@vindex nnheader-file-name-translation-alist
@cindex file names
@cindex invalid characters in file names
@cindex characters in file names
on your system (you OS/2 user you), you could say something like:
@lisp
-(setq nnheader-file-name-translation-alist
+(setq nnheader-file-name-translation-alist
'((?: . ?_)))
@end lisp
@item gnus-shell-command-separator
@vindex gnus-shell-command-separator
-String used to separate two shell commands. The default is @samp{;}.
+String used to separate two shell commands. The default is @samp{;}.
@end table
@chapter 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.
+touch. Say hello to your cats from me.
My @strong{ghod}---I just can't stand goodbyes. Sniffle.
* 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.
+* Gnus Reference Guide:: Rilly, rilly technical stuff.
* Emacs for Heathens:: A short introduction to Emacsian terms.
* Frequently Asked Questions:: A question-and-answer session.
@end menu
If you want to investigate the person responsible for this outrage, you
can point your (feh!) web browser to
-@file{http://www.ifi.uio.no/~larsi/}. This is also the primary
+@file{http://www.stud.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.
releases)) was released under the name ``Gnus 5.2'' (40 releases).
On July 28th 1996 work on Red Gnus was begun, and it was released on
-January 25th 1997 (after 84 releases) as ``Gnus 5.4''.
+January 25th 1997 (after 84 releases) as ``Gnus 5.4'' (67 releases).
+
+On September 13th 1997, Quassia Gnus was started and lasted 37
+releases. If was released as ``Gnus 5.6 on March 8th 1998.
If you happen upon a version of Gnus that has a prefixed name --
``(ding) Gnus'', ``September Gnus'', ``Red Gnus'', ``Quassia Gnus'' --
* Compatibility:: Just how compatible is Gnus with @sc{gnus}?
* Conformity:: Gnus tries to conform to all standards.
* Emacsen:: Gnus can be run on a few modern Emacsen.
-* Contributors:: Oodles of people.
+* 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.
@end menu
@node Why?
@subsection Why?
-What's the point of Gnus?
+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
their names.
The @code{gnus-uu} package has changed drastically. @xref{Decoding
-Articles}.
+Articles}.
One major compatibility question is the presence of several summary
buffers. All variables relevant while reading a group are
@sc{gnus} internals should suffer no problems. If problems occur,
please let me know by issuing that magic command @kbd{M-x gnus-bug}.
+@vindex gnus-bug-create-help-buffer
+If you are in the habit of sending bug reports @emph{very} often, you
+may find the helpful help buffer annoying after a while. If so, set
+@code{gnus-bug-create-help-buffer} to @code{nil} to avoid having it pop
+up at you.
+
@node Conformity
@subsection Conformity
@table @emph
-@item 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.
-
@item 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 @code{tin} and @code{Netscape} I know not to use either of
-those for posting articles. I would not have known that if it wasn't
-for the @code{X-Newsreader} header.
+@itemx User-Agent
+These are considered to be ``vanity headers'', while I consider them
+to be consumer information. After seeing so many badly formatted
+articles coming from @code{tin} and @code{Netscape} I know not to use
+either of those for posting articles. I would not have known that if
+it wasn't for the @code{X-Newsreader} header.
@end table
+@item USEFOR
+@cindex USEFOR
+USEFOR is an IETF working group writing a successor to RFC 1036, based
+on Son-of-RFC 1036. They have produced a number of drafts proposing
+various changes to the format of news articles. The Gnus towers will
+look into implementing the changes when the draft is accepted as an RFC.
+
@end table
If you ever notice Gnus acting non-compliant with regards to the texts
Gnus should work on :
-@itemize @bullet
+@itemize @bullet
@item
-Emacs 19.32 and up.
+Emacs 20.3 and up.
@item
-XEmacs 19.14 and up.
-
-@item
-Mule versions based on Emacs 19.32 and up.
+XEmacs 20.4 and up.
@end itemize
-Gnus will absolutely not work on any Emacsen older than that. Not
-reliably, at least.
+This Gnus version will absolutely not work on any Emacsen older than
+that. Not reliably, at least. Older versions of Gnus may work on older
+Emacs versions.
There are some vague differences between Gnus on the various
platforms---XEmacs features more graphics (a logo and a toolbar)---but
other than that, things should look pretty much the same under all
-Emacsen.
+Emacsen.
@node Contributors
@itemize @bullet
-@item
+@item
Masanobu @sc{Umeda}---the writer of the original @sc{gnus}.
-@item
+@item
Per Abrahamsen---custom, scoring, highlighting and @sc{soup} code (as
well as numerous other things).
-@item
+@item
Luis Fernandes---design and graphics.
@item
Erik Naggum---help, ideas, support, code and stuff.
-@item
+@item
+Shenghuo Zhu---uudecode.el, mm-uu.el, rfc1843.el and many other things
+connected with @sc{mime} and other types of en/decoding.
+
+@item
Wes Hardaker---@file{gnus-picon.el} and the manual section on
@dfn{picons} (@pxref{Picons}).
@item
Kim-Minh Kaplan---further work on the picon code.
-@item
+@item
Brad Miller---@file{gnus-gl.el} and the GroupLens manual section
(@pxref{GroupLens}).
-@item
+@item
Sudish Joseph---innumerable bug fixes.
-@item
+@item
Ilja Weis---@file{gnus-topic.el}.
-@item
+@item
Steven L. Baur---lots and lots and lots of bugs detections and fixes.
-@item
+@item
Vladimir Alexiev---the refcard and reference booklets.
-@item
-Felix Lee & Jamie Zawinsky---I stole some pieces from the XGnus
+@item
+Felix Lee & Jamie Zawinski---I stole some pieces from the XGnus
distribution by Felix Lee and JWZ.
-@item
+@item
Scott Byer---@file{nnfolder.el} enhancements & rewrite.
-@item
+@item
Peter Mutsaers---orphan article scoring code.
-@item
+@item
Ken Raeburn---POP mail support.
-@item
+@item
Hallvard B Furuseth---various bits and pieces, especially dealing with
.newsrc files.
-@item
+@item
Brian Edmonds---@file{gnus-bbdb.el}.
@item
-David Moore---rewrite of @file{nnvirtual.el} and many other things.
+David Moore---rewrite of @file{nnvirtual.el} and many other things.
-@item
+@item
Kevin Davidson---came up with the name @dfn{ding}, so blame him.
@item
This manual was proof-read by Adrian Aichner, with Ricardo Nassif, Mark
Borges, and Jost Krieger proof-reading parts of the manual.
-The following people have contributed many patches and suggestions:
+The following people have contributed many patches and suggestions:
Christopher Davis,
Andrew Eskilsson,
Kai Grossjohann,
David Kågedal,
Richard Pieri,
-Fabrice Popineau,
-Daniel Quinlan,
+Fabrice Popineau,
+Daniel Quinlan,
Jason L. Tibbitts, III,
and
Jack Vinson.
Jari Aalto,
Adrian Aichner,
+Vladimir Alexiev,
Russ Allbery,
-Peter Arius,
+Peter Arius,
Matt Armstrong,
Marc Auslander,
+Miles Bader,
+Frank Bennett,
Robert Bihlmeyer,
Chris Bone,
Mark Borges,
Lance A. Brown,
Kees de Bruin,
Martin Buchholz,
+Joe Buehler,
Kevin Buhr,
Alastair Burt,
Joao Cachopo,
Zlatko Calusic,
Massimo Campostrini,
+Castor,
+David Charlap,
Dan Christensen,
+Kevin Christian,
Michael R. Cook,
-Glenn Coombs,
-Frank D. Cringle,
+Glenn Coombs,
+Frank D. Cringle,
Geoffrey T. Dairiki,
Andre Deparade,
Ulrik Dickow,
Michael Welsh Duggan,
Dave Edmondson,
Paul Eggert,
+Karl Eichwalder,
Enami Tsugutomo, @c Enami
Michael Ernst,
Luc Van Eycken,
Sam Falkner,
Nelson Jose dos Santos Ferreira,
Sigbjorn Finne,
+Paul Fisher,
+Decklin Foster,
Gary D. Foster,
-Paul Franklin,
+Paul Franklin,
Guy Geens,
Arne Georg Gleditsch,
David S. Goldberg,
Michelangelo Grigni,
-D. Hall,
+Dale Hagglund,
+D. Hall,
Magnus Hammerin,
Kenichi Handa, @c Handa
Raja R. Harinath,
+Yoshiki Hayashi, @c ?
+P. E. Jareth Hein,
Hisashige Kenji, @c Hisashige
Marc Horowitz,
Gunnar Horrigmo,
Brad Howes,
François Felix Ingrand,
Ishikawa Ichiro, @c Ishikawa
-Lee Iverson,
+Lee Iverson,
Iwamuro Motonori, @c Iwamuro
Rajappa Iyer,
Andreas Jaeger,
Randell Jesup,
-Fred Johansen,
+Fred Johansen,
+Gareth Jones,
Simon Josefsson,
Greg Klanderman,
Karl Kleinpaste,
Peter Skov Knudsen,
Shuhei Kobayashi, @c Kobayashi
+Koseki Yoshinori, @c Koseki
Thor Kristoffersen,
Jens Lautenbacher,
+Martin Larose,
Seokchan Lee, @c Lee
+Joerg Lenneis,
Carsten Leonhardt,
James LewisMoss,
Christian Limpach,
Markus Linnala,
Dave Love,
+Mike McEwan,
Tonny Madsen,
Shlomo Mahlab,
Nat Makarevitch,
Istvan Marko,
David Martin,
-Jason R Mastaler,
+Jason R. Mastaler,
Gordon Matzigkeit,
Timo Metzemakers,
Richard Mlynarik,
Stephen Peters,
Jens-Ulrik Holger Petersen,
Ulrich Pfeifer,
+Matt Pharr,
+Andy Piper,
John McClary Prevost,
+Bill Pringlemeir,
+Mike Pullen,
+Jim Radford,
Colin Rafferty,
Lasse Rasinen,
Lars Balker Rasmussen,
Roland B. Roberts,
Bart Robinson,
Christian von Roques,
+Markus Rost,
Jason Rumney,
+Wolfgang Rupprecht,
Jay Sachs,
Dewey M. Sasser,
+Conrad Sauerwald,
Loren Schall,
Dan Schmidt,
Ralph Schleicher,
Philippe Schnoebelen,
+Andreas Schwab,
Randal L. Schwartz,
Justin Sheehy,
-Danny Siu,
+Danny Siu,
Matt Simmons,
Paul D. Smith,
Jeff Sparkes,
Michael Sperber,
Darren Stalder,
Richard Stallman,
-Greg Stark,
+Greg Stark,
+Sam Steingold,
+Jonas Steverud,
Paul Stodghill,
Kurt Swanson,
-Samuel Tardieu,
+Samuel Tardieu,
Teddy,
Chuck Thompson,
Philippe Troin,
James Troup,
-Aaron M. Ucko,
+Trung Tran-Duc,
+Aaron M. Ucko,
Aki Vehtari,
Didier Verna,
Jan Vroonhof,
Barry A. Warsaw,
Christoph Wedler,
Joe Wells,
+Lee Willis,
+Katsumi Yamaoka @c Yamaoka
and
-Katsumi Yamaoka. @c Yamaoka
+Lloyd Zusman.
+
For a full overview of what each person has done, the ChangeLogs
included in the Gnus alpha distributions should give ample reading
(550kB and counting).
Apologies to everybody that I've forgotten, of which there are many, I'm
-sure.
+sure.
Gee, that's quite a list of people. I guess that must mean that there
actually are people who are using Gnus. Who'd'a thunk it!
* ding Gnus:: New things in Gnus 5.0/5.1, the first new Gnus.
* September Gnus:: The Thing Formally Known As Gnus 5.3/5.3.
* Red Gnus:: Third time best---Gnus 5.4/5.5.
-* Quassia Gnus:: Two times two is four, or Gnus 5.6.1.7.
+* Quassia Gnus:: Two times two is four, or Gnus 5.6/5.7.
@end menu
These lists are, of course, just @emph{short} overviews of the
@item
The look of all buffers can be changed by setting format-like variables
-(@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
-
-@item
+(@pxref{Group Buffer Format} and @pxref{Summary Buffer Format}).
+
+@item
Local spool and several @sc{nntp} servers can be used at once
-(@pxref{Select Methods}).
+(@pxref{Select Methods}).
-@item
+@item
You can combine groups into virtual groups (@pxref{Virtual Groups}).
-@item
+@item
You can read a number of different mail formats (@pxref{Getting Mail}).
All the mail backends implement a convenient mail expiry scheme
-(@pxref{Expiring Mail}).
+(@pxref{Expiring Mail}).
@item
Gnus can use various strategies for gathering threads that have lost
can go back and retrieve enough headers to build a complete thread
(@pxref{Customizing Threading}).
-@item
+@item
Killed groups can be displayed in the group buffer, and you can read
them as well (@pxref{Listing Groups}).
-@item
+@item
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
(@pxref{The Active File}).
-@item
+@item
Gnus implements a sliding scale of subscribedness to groups
(@pxref{Group Levels}).
-@item
+@item
You can score articles according to any number of criteria
(@pxref{Scoring}). You can even get Gnus to find out how to score
articles for you (@pxref{Adaptive Scoring}).
-@item
+@item
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 (@pxref{Auto Save}).
+read if your machine should go down (@pxref{Auto Save}).
-@item
+@item
Gnus now has its own startup file (@file{.gnus}) to avoid cluttering up
the @file{.emacs} file.
-@item
+@item
You can set the process mark on both groups and articles and perform
operations on all the marked items (@pxref{Process/Prefix}).
-@item
+@item
You can grep through a subset of groups and create a group from the
-results (@pxref{Kibozed Groups}).
+results (@pxref{Kibozed Groups}).
-@item
+@item
You can list subsets of groups according to, well, anything
-(@pxref{Listing Groups}).
+(@pxref{Listing Groups}).
-@item
+@item
You can browse foreign servers and subscribe to groups from those
-servers (@pxref{Browse Foreign Server}).
+servers (@pxref{Browse Foreign Server}).
-@item
+@item
Gnus can fetch articles, asynchronously, on a second connection to the
server (@pxref{Asynchronous Fetching}).
-@item
-You can cache articles locally (@pxref{Article Caching}).
+@item
+You can cache articles locally (@pxref{Article Caching}).
-@item
+@item
The uudecode functions have been expanded and generalized
-(@pxref{Decoding Articles}).
+(@pxref{Decoding Articles}).
@item
You can still post uuencoded articles, which was a little-known feature
-of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
+of @sc{gnus}' past (@pxref{Uuencoding and Posting}).
@item
Fetching parents (and other articles) now actually works without
-glitches (@pxref{Finding the Parent}).
+glitches (@pxref{Finding the Parent}).
@item
Gnus can fetch FAQs and group descriptions (@pxref{Group Information}).
Digests (and other files) can be used as the basis for groups
(@pxref{Document Groups}).
-@item
+@item
Articles can be highlighted and customized (@pxref{Customizing
-Articles}).
+Articles}).
-@item
+@item
URLs and other external references can be buttonized (@pxref{Article
-Buttons}).
+Buttons}).
@item
You can do lots of strange stuff with the Gnus window & frame
@item
You can click on buttons instead of using the keyboard
-(@pxref{Buttons}).
+(@pxref{Buttons}).
@end itemize
@item
Gnus is now able to generate @dfn{sparse} threads---threads where
missing articles are represented by empty nodes (@pxref{Customizing
-Threading}).
+Threading}).
@lisp
(setq gnus-build-sparse-threads 'some)
@item
Outgoing articles are stored on a special archive server
-(@pxref{Archived Messages}).
+(@pxref{Archived Messages}).
@item
Partial thread regeneration now happens when articles are
-referred.
+referred.
@item
Gnus can make use of GroupLens predictions (@pxref{GroupLens}).
@item
-Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
+Picons (personal icons) can be displayed under XEmacs (@pxref{Picons}).
@item
A @code{trn}-like tree buffer can be displayed (@pxref{Tree Display}).
@item
In binary groups you can use a special binary minor mode (@pxref{Binary
-Groups}).
+Groups}).
@item
Groups can be grouped in a folding topic hierarchy (@pxref{Group
@item
Article headers can be buttonized (@pxref{Article Washing}).
-@lisp
-(add-hook 'gnus-article-display-hook
- 'gnus-article-add-buttons-to-head)
-@end lisp
-
@item
All mail backends support fetching articles by @code{Message-ID}.
@item
All summary mode commands are available directly from the article
-buffer (@pxref{Article Keymap}).
+buffer (@pxref{Article Keymap}).
@item
Frames can be part of @code{gnus-buffer-configuration} (@pxref{Windows
@end lisp
@item
-Many new hooks have been introduced to make customizing easier.
+Many new hooks have been introduced to make customizing easier.
@item
Gnus respects the @code{Mail-Copies-To} header.
(@pxref{Customizing Threading}).
@lisp
-(setq gnus-summary-thread-gathering-function
+(setq gnus-summary-thread-gathering-function
'gnus-gather-threads-by-references)
@end lisp
@item
Read articles can be stored in a special backlog buffer to avoid
-refetching (@pxref{Article Backlog}).
+refetching (@pxref{Article Backlog}).
@lisp
(setq gnus-keep-backlog 50)
@item
Gnus doesn't have to do as much prompting when saving (@pxref{Saving
-Articles}).
+Articles}).
@lisp
(setq gnus-prompt-before-saving t)
@item
@code{gnus-uu} can view decoded files asynchronously while fetching
-articles (@pxref{Other Decode Variables}).
+articles (@pxref{Other Decode Variables}).
@lisp
(setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-view)
@item
Boring headers can be hidden (@pxref{Article Hiding}).
-@lisp
-(add-hook 'gnus-article-display-hook
- 'gnus-article-hide-boring-headers t)
-@end lisp
-
@item
Default scoring values can now be set from the menu bar.
@file{nntp.el} has been totally rewritten in an asynchronous fashion.
@item
-Article prefetching functionality has been moved up into
-Gnus (@pxref{Asynchronous Fetching}).
+Article prefetching functionality has been moved up into
+Gnus (@pxref{Asynchronous Fetching}).
@item
Scoring can now be performed with logical operators like @code{and},
@item
@code{nndoc} was rewritten to be easily extendable (@pxref{Document
-Server Internals}).
+Server Internals}).
@item
Groups can inherit group parameters from parent topics (@pxref{Topic
@item
Adaptive scoring can be done on a Subject word-by-word basis
-(@pxref{Adaptive Scoring}).
+(@pxref{Adaptive Scoring}).
@lisp
(setq gnus-use-adaptive-scoring '(word))
@item
Scores can be decayed (@pxref{Score Decays}).
-
+
@lisp
(setq gnus-decay-scores t)
@end lisp
@item
A new command for reading collections of documents
(@code{nndoc} with @code{nnvirtual} on top) has been added---@kbd{M-C-d}
-(@pxref{Really Various Summary Commands}).
+(@pxref{Really Various Summary Commands}).
@item
Process mark sets can be pushed and popped (@pxref{Setting Process
@item
Emphasized text can be properly fontisized:
-@lisp
-(add-hook 'gnus-article-display-hook 'gnus-article-emphasize)
-@end lisp
-
@end itemize
@node Quassia Gnus
@subsubsection Quassia Gnus
-New features in Gnus 5.6.1.7:
+New features in Gnus 5.6:
@itemize @bullet
@samp{\\1}-expressions are now valid in @code{nnmail-split-methods}.
@item
- The @code{custom-face-lookup} function has been removed.
+ The @code{custom-face-lookup} function has been removed.
If you used this function in your initialization files, you must
rewrite them to use @code{face-spec-set} instead.
@item
- Cancelling now uses the current select method. Symbolic prefix
+ Canceling now uses the current select method. Symbolic prefix
@kbd{a} forces normal posting method.
@item
- New command to translate M@item
-@item
-** sm*rtq**t*s into proper text---@kbd{W d}.
+ New command to translate M******** sm*rtq**t*s into proper
+text---@kbd{W d}.
@item
For easier debugging of @code{nntp}, you can set
@cindex todo
Also known as the @dfn{todo list}. Sure to be implemented before the
-next millennium.
+next millennium.
Be afraid. Be very afraid.
@itemize @bullet
@item
-Native @sc{mime} support is something that should be done.
-
-@item
-Really do unbinhexing.
-
-@item
I would like the zombie-page to contain an URL to the source of the
latest version of gnus or some explanation on where to find it.
nnmh-be-safe means that crossposted articles will
be marked as unread.
@item
- Orphan score entries dont show on "V t" score trace
+ Orphan score entries don't show on "V t" score trace
@item
when clearing out data, the cache data should also be reset.
@item
rewrite gnus-summary-limit-children to be non-recursive
to avoid exceeding lisp nesting on huge groups.
@item
- expinged articles are counted when computing scores.
+ expunged articles are counted when computing scores.
@item
implement gnus-batch-brew-soup
@item
@item
nndoc should always allocate unique Message-IDs.
@item
- implement gnus-score-thread
-@item
If there are mail groups the first time you use Gnus, Gnus'll
-make the mail groups killed.
+make the mail groups killed.
@item
no "no news is good news" when using topics.
@item
@item
using a virtual server name as `gnus-select-method' doesn't work?
@item
- when killing/yanking a group from one topic to another in a slave, the
-master will yank it first to one topic and then add it to another.
+ when killing/yanking a group from one topic to another in a slave, the
+master will yank it first to one topic and then add it to another.
Perhaps.
@item
warn user about `=' redirection of a group in the active file?
@item
- really unbinhex binhex files.
-@item
take over the XEmacs menubar and offer a toggle between the XEmacs
bar and the Gnus bar.
@item
the selected article show have its Subject displayed in its summary line.
@item
when entering groups, get the real number of unread articles from
-the server?
+the server?
@item
sort after gathering threads -- make false roots have the
-headers of the oldest orhpan with a 0 article number?
+headers of the oldest orphan with a 0 article number?
@item
nndoc groups should inherit the score files of their parents? Also
inherit copy prompts and save files.
on. Eg. -- `(("nnml:" . 1))'.
@item
easier interface to nnkiboze to create ephemeral groups that
-contaion groups that match a regexp.
+contain groups that match a regexp.
@item
allow newlines in <URL:> urls, but remove them before using
the URL.
@item
gnus-dont-move-articles-to-same-group variable when respooling.
@item
- when messages are crossposted between several auto-expirable groups,
+ when messages are crossposted between several auto-expirable groups,
articles aren't properly marked as expirable.
@item
nneething should allow deletion/moving.
TAB on the last button should go to the first button.
@item
if the car of an element in `mail-split-methods' is a function,
-and the function returns non-nil, use that as the name of the group(s) to
+and the function returns non-nil, use that as the name of the group(s) to
save mail in.
@item
command for listing all score files that have been applied.
nnmail-group-spool-alist -- says where each group should use
as a spool file.
@item
- when an article is crossposted to an auto-expirable group, the article
+ when an article is crossposted to an auto-expirable group, the article
should be marker as expirable.
@item
article mode command/menu for "send region as URL to browser".
@item
`1 0 A M' to do matches on the active hashtb.
@item
- duplicates -- command to remove Gnus-Warning header, use the read
+ duplicates -- command to remove Gnus-Warning header, use the read
Message-ID, delete the "original".
@item
when replying to several messages at once, put the "other" message-ids
the file whenever we read the active file or the list
of killed groups in the .eld file reaches a certain length.
@item
- function for starting to edit a file to put into
+ function for starting to edit a file to put into
the current mail group.
@item
- score-find-trace should display the total score of the article.
+ score-find-trace should display the total score of the article.
@item
- "ghettozie" -- score on Xref header and nix it out after using it
+ "ghettozie" -- score on Xref header and nix it out after using it
to avoid marking as read in other groups it has been crossposted to.
@item
look at procmail splitting. The backends should create
@item
function for backends to register themselves with Gnus.
@item
- when replying to several process-marked articles,
+ when replying to several process-marked articles,
have all the From end up in Cc headers? Variable to toggle.
@item
- command to delete a crossposted mail article from all
+ command to delete a crossposted mail article from all
groups it has been mailed to.
@item
- `B c' and `B m' should be crosspost aware.
+ `B c' and `B m' should be crosspost aware.
@item
hide-pgp should also hide PGP public key blocks.
@item
- Command in the group buffer to respoll process-marked groups.
+ Command in the group buffer to respool process-marked groups.
@item
`gnus-summary-find-matching' should accept
pseudo-"headers" like "body", "head" and "all"
Process-marking all groups in a topic should process-mark
groups in subtopics as well.
@item
- Add non-native groups to the list of killed groups when killing them.
+ Add non-native groups to the list of killed groups when killing them.
@item
nntp-suggest-kewl-config to probe the nntp server and suggest
variable settings.
@item
checking for bogus groups should clean topic alists as well.
@item
- cancelling articles in foreign groups.
+ canceling articles in foreign groups.
@item
article number in folded topics isn't properly updated by
Xref handling.
@item
a backend for reading collections of babyl files nnbabylfolder?
@item
- a command for making the native groups into foreign groups.
+ a command for making the native groups into foreign groups.
@item
server mode command for clearing read marks from all groups
from a server.
@item
- when following up mulitple articles, include all To, Cc, etc headers
+ when following up multiple articles, include all To, Cc, etc headers
from all articles.
@item
a command for deciding what the total score of the current
@item
be able to control word adaptive scoring from the score files.
@item
- a variable to make `C-c C-c' post using the "current" select method.
+ a variable to make `C-c C-c' post using the "current" select method.
@item
`limit-exclude-low-scored-articles'.
@item
@item
command to nix out all nnoo state information.
@item
- nnmail-process-alist that calls functions if group names
+ nnmail-process-alist that calls functions if group names
matches an alist -- before saving.
@item
use buffer-invisibility-spec everywhere for hiding text.
command to fetch a Message-ID from any buffer, even
starting Gnus first if necessary.
@item
- when posting and checking whether a group exists or not, just
+ when posting and checking whether a group exists or not, just
ask the nntp server instead of relying on the active hashtb.
@item
buttonize the output of `C-c C-a' in an apropos-like way.
command to create an ephemeral nnvirtual group that
matches some regexp(s).
@item
- nndoc should understand "Content-Type: message/rfc822" forwarded messages.
+ nndoc should understand "Content-Type: message/rfc822" forwarded messages.
@item
it should be possible to score "thread" on the From header.
@item
new group parameter -- `post-to-server' that says to post
using the current server. Also a variable to do the same.
@item
- the slave dribble files should autosave to the slave file names.
+ the slave dribble files should auto-save to the slave file names.
@item
a group parameter that says what articles to display on group entry, based
on article marks.
a way to visually distinguish slave Gnusae from masters. (Whip instead
of normal logo?)
@item
- Use DJ Bernstein "From " quoting/dequoting, where appliccable.
+ Use DJ Bernstein "From " quoting/dequoting, where applicable.
@item
Why is hide-citation-maybe and hide-citation different? Also
clear up info.
problem is that archives are spread all over the net, unlike FAQs.
What would be best I suppose is to find the one closest to your site.
-In any case, there is a list of general news group archives at
+In any case, there is a list of general news group archives at @*
ftp://ftp.neosoft.com/pub/users/claird/news.lists/newsgroup_archives.html
@item
LMI> Well, nnbabyl could alter the group info to heed labels like
-LMI> answered and read, I guess.
+LMI> answered and read, I guess.
It could also keep them updated (the same for the Status: header of
unix mbox files).
`M u <name> RET' remove label <name> from current message.
`/ l <expr> RET' limit summary buffer according to <expr>.
-<expr> would be a boolean expression on the labels, e.g.
+<expr> would be a boolean expression on the labels, e.g.
- `/ l bug & !fixed RET'
+`/ l bug & !fixed RET'
@end example
would show all the messages which are labeled `bug' but not labeled
-`fixed'.
+`fixed'.
-One could also immagine the labels being used for highliting, or
+One could also imagine the labels being used for highlighting, or
affect the summary line format.
- If it is a directory containing numbered files, create an nndir
summary buffer.
-- For other directories, create a nneething summaru buffer.
+- For other directories, create a nneething summary buffer.
- For files matching "\\`From ", create a nndoc/mbox summary.
decend into ucd?
The problem above is that since there is really only one subsection of
-science, shouldn't it prompt you for only decending sci.something? If
+science, shouldn't it prompt you for only descending sci.something? If
there was a sci.somethingelse group or section, then it should prompt
for sci? first the sci.something? then sci.somethingelse?...
What i want is for Gnus to treat any sequence or combination of the following
as a single spoiler warning and hide it all, replacing it with a "Next Page"
button:
-
- ^L's
- more than n blank lines
-
- more than m identical lines
- (which should be replaced with button to show them)
+^L's
+
+more than n blank lines
+
+more than m identical lines
+(which should be replaced with button to show them)
- any whitespace surrounding any of the above
+any whitespace surrounding any of the above
@item
Well, we could allow a new value to `gnus-thread-ignore-subject' --
`spaces', or something. (We could even default to that.) And then
subjects that differ in white space only could be considered the
-"same" subject for threading purposes.
+"same" subject for threading purposes.
@item
Modes to preprocess the contents (e.g. jka-compr) use the second form
Group-mode
show-list-of-articles-in-group
- if (key-pressed == SPACE)
- if (no-more-articles-in-group-to-select)
- if (articles-selected)
- start-reading-selected-articles;
- junk-unread-articles;
- next-group;
- else
- show-next-page;
-
- else if (key-pressed = '.')
- if (consolidated-menus) # same as hide-thread in Gnus
- select-thread-under-cursor;
- else
- select-article-under-cursor;
-
+ if (key-pressed == SPACE)
+ if (no-more-articles-in-group-to-select)
+ if (articles-selected)
+ start-reading-selected-articles;
+ junk-unread-articles;
+ next-group;
+ else
+ show-next-page;
+
+ else if (key-pressed = '.')
+ if (consolidated-menus) # same as hide-thread in Gnus
+ select-thread-under-cursor;
+ else
+ select-article-under-cursor;
+
Article-mode
- if (key-pressed == SPACE)
- if (more-pages-in-article)
- next-page;
- else if (more-selected-articles-to-read)
- next-article;
- else
- next-group;
+ if (key-pressed == SPACE)
+ if (more-pages-in-article)
+ next-page;
+ else if (more-selected-articles-to-read)
+ next-article;
+ else
+ next-group;
@end example
@item
the wildcard expression).
@item
-It would be nice if it also handled
+It would be nice if it also handled
- <URL:news://sunsite.auc.dk/>
+ <URL:news://sunsite.auc.dk/>
which should correspond to `B nntp RET sunsite.auc.dk' in *Group*.
`x' should retain any sortings that have been performed.
@item
- allow the user to specify the presedence of the secondary marks. Also
+ allow the user to specify the precedence of the secondary marks. Also
allow them to be displayed separately.
@item
(let ((buffer-read-only nil))
(goto-char (point-min))
(while (search-forward "\221" nil t)
- (replace-match "`" t t))
+ (replace-match "`" t t))
(goto-char (point-min))
(while (search-forward "\222" nil t)
- (replace-match "'" t t))
+ (replace-match "'" t t))
(goto-char (point-min))
(while (search-forward "\223" nil t)
- (replace-match "\"" t t))
+ (replace-match "\"" t t))
(goto-char (point-min))
(while (search-forward "\224" nil t)
- (replace-match "\"" t t)))))
+ (replace-match "\"" t t)))))
@end example
@item
(add-hook 'gnus-exit-query-functions
'(lambda ()
(if (and (file-exists-p nnmail-spool-file)
- (> (nnheader-file-size nnmail-spool-file) 0))
+ (> (nnheader-file-size nnmail-spool-file) 0))
(yes-or-no-p "New mail has arrived. Quit Gnus anyways? ")
(y-or-n-p "Are you sure you want to quit Gnus? "))))
@end example
numbers and match on the age of the article.
@item
- gnus-cacheable-groups
-
-@item
@example
> > > If so, I've got one gripe: It seems that when I fire up gnus 5.2.25
> > > under xemacs-19.14, it's creating a new frame, but is erasing the
> > > buffer in the frame that it was called from =:-O
->
+>
> > Hm. How do you start up Gnus? From the toolbar or with
-> > `M-x gnus-other-frame'?
->
+> > `M-x gnus-other-frame'?
+>
> I normally start it up from the toolbar; at
> least that's the way I've caught it doing the
> deed before.
add a way to select which NoCeM type to apply -- spam, troll, etc.
@item
- nndraft-request-group should tally autosave files.
+ nndraft-request-group should tally auto-save files.
@item
implement nntp-retry-on-break and nntp-command-timeout.
@item
Read Netscape discussion groups:
-snews://secnews.netscape.com/netscape.communicator.unix
+snews://secnews.netscape.com/netscape.communicator.unix
@item
One command to edit the original version if an article, and one to edit
Allow breaking lengthy NNTP commands.
@item
-gnus-article-highlight-limit, to disable highlighting in big articles.
+gnus-article-highlight-limit, to disable highlighting in big articles.
@item
Editing an article should put the article to be edited
in a special, unique buffer.
@item
+A command to send a mail to the admin-address group param.
+
+@item
+A Date scoring type that will match if the article
+is less than a certain number of days old.
+
+@item
+New spec: %~(tab 56) to put point on column 56
+
+@item
+Allow Gnus Agent scoring to use normal score files.
+
+@item
+Rething the Agent active file thing. `M-g' doesn't update the active
+file, for instance.
+
+@item
+With dummy roots, `^' and then selecing the first article
+in any other dummy thread will make Gnus highlight the
+dummy root instead of the first article.
+
+@item
+Propagate all group properties (marks, article numbers, etc) up to the
+topics for displaying.
+
+@item
+`n' in the group buffer with topics should go to the next group
+with unread articles, even if that group is hidden in a topic.
+
+@item
+gnus-posting-styles doesn't work in drafts.
+
+@item
+gnus-summary-limit-include-cached is slow when there are
+many articles in the cache, since it regenerates big parts of the
+summary buffer for each article.
+
+@item
+Implement gnus-batch-brew-soup.
+
+@item
+Group parameters and summary commands for un/subscribing to mailing
+lists.
+
+@item
+Introduce nnmail-home-directory.
+
+@item
+gnus-fetch-group and friends should exit Gnus when the user
+exits the group.
+
+@item
+The jingle is only played on the second invocation of Gnus.
+
+@item
+Bouncing articles should do MIME.
+
+@item
+Crossposted articles should "inherit" the % or @ mark from the other
+groups it has been crossposted to, or something. (Agent.)
+
+@item
+`S D r' should allow expansion of aliases.
+
+@item
+If point is on a group that appears multiple times in topics, and
+you press `l', point will move to the first instance of the group.
+
+@item
+The documentation should mention pop3.el, fetchmail, smtpmail and why
+po:username often fails.
+
+@item
+Fetch by Message-ID from dejanews.
+
+<URL:http://search.dejanews.com/msgid.xp?MID=%3C62h9l9$hm4@@basement.replay.com%3E&fmt=raw>
+
+@item
+A spec for the group line format to display the number of
+agent-downloaded articles in the group.
+
+@item
+Some nntp servers never respond when posting, so there should be a
+timeout for all commands.
+
+@item
Solve the halting problem.
@c TODO
either @code{texi2dvi}
@iflatex
or my own home-brewed TeXinfo to \LaTeX\ transformer,
-and then run through @code{latex} and @code{dvips}
+and then run through @code{latex} and @code{dvips}
@end iflatex
to get what you hold in your hands now.
@item
This is a @file{file}
-@item
+@item
This is a @code{symbol}
@end enumerate
@cindex mail message
A message that has been mailed.
-@item message
+@item message
@cindex message
A mail message or news article
@item body
@cindex body
The rest of an article. Everything not in the head is in the
-body.
+body.
@item header
@cindex header
-A line from the head of an article.
+A line from the head of an article.
@item headers
@cindex headers
number of unread articles is called @dfn{activating the group}.
Un-activated groups are listed with @samp{*} in the group buffer.
-@item server
+@item server
@cindex server
A machine one can connect to and get news (or mail) from.
@cindex washing
Taking a buffer and running it through a filter of some sort. The
result will (more often than not) be cleaner and more pleasing than the
-original.
+original.
@item ephemeral groups
@cindex ephemeral groups
Most groups store data on what articles you have read. @dfn{Ephemeral}
groups are groups that will have no data stored---when you exit the
-group, it'll disappear into the aether.
+group, it'll disappear into the aether.
@item solid groups
@cindex solid groups
useful data is in the summary buffer, anyway. Set this variable to
@samp{^NEVVVVER} or @samp{From:}, or whatever you feel you need.
-@item gnus-article-display-hook
Set this hook to all the available hiding commands:
@lisp
-(setq gnus-article-display-hook
- '(gnus-article-hide-headers gnus-article-hide-signature
- gnus-article-hide-citation))
+(setq gnus-treat-hide-headers 'head
+ gnus-treat-hide-signature t
+ gnus-treat-hide-citation t)
@end lisp
@item gnus-use-full-window
If this is @code{nil}, Gnus will never save @file{.newsrc}---it will
only save @file{.newsrc.eld}. This means that you will not be able to
use any other newsreaders than Gnus. This variable is @code{t} by
-default.
+default.
@item gnus-save-killed-list
If this is @code{nil}, Gnus will not save the list of dead groups. You
@code{gnus-nov-is-evil} to @code{nil} to make entering and exiting the
summary buffer faster.
-Set @code{gnus-article-display-hook} to @code{nil} to make article
-processing a bit faster.
-
@page
@node Troubleshooting
@item
Read the help group (@kbd{G h} in the group buffer) for a FAQ and a
-how-to.
+how-to.
@item
@vindex max-lisp-eval-depth
@kbd{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.
+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 just send
@page
-@node A Programmers Guide to Gnus
-@section A Programmer@'s Guide to Gnus
+@node Gnus Reference Guide
+@section Gnus Reference Guide
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
(ditto), data structures (some are less likely to change than others)
and general methods of operation.
-@menu
+@menu
* Gnus Utility Functions:: Common functions and variable to use.
* Backend Interface:: How Gnus communicates with the servers.
* Score File Syntax:: A BNF definition of the score file standard.
@findex gnus-get-info
Returns the group info list for @var{group}.
+@item gnus-group-unread
+@findex gnus-group-unread
+The number of unread articles in @var{group}, or @code{t} if that is
+unknown.
+
+@item gnus-active
+@findex gnus-active
+The active entry for @var{group}.
+
+@item gnus-set-active
+@findex gnus-set-active
+Set the active entry for @var{group}.
+
@item gnus-add-current-to-buffer-list
@findex gnus-add-current-to-buffer-list
Adds the current buffer to the list of buffers to be killed on Gnus
@lisp
(gnus-check-backend-function "request-scan" "nnml:misc")
-=> t
+@result{} t
@end lisp
@item gnus-read-method
name. Take this example:
@lisp
-(nntp "odd-one"
- (nntp-address "ifi.uio.no")
+(nntp "odd-one"
+ (nntp-address "ifi.uio.no")
(nntp-port-number 4324))
@end lisp
Here the virtual server name is @samp{odd-one} while the name of
-the physical server is @samp{ifi.uio.no}.
+the physical server is @samp{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 they pull down/push up when needed.
+server environments that they pull down/push up when needed.
There are two groups of interface functions: @dfn{required functions},
which must be present, and @dfn{optional functions}, which Gnus will
more.
In the examples and definitions I will refer to the imaginary backend
-@code{nnchoke}.
+@code{nnchoke}.
@cindex @code{nnchoke}
@var{articles} is either a range of article numbers or a list of
@code{Message-ID}s. Current backends do not fully support either---only
sequences (lists) of article numbers, and most backends do not support
-retrieval of @code{Message-ID}s. But they should try for both.
+retrieval of @code{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 @code{headers} or @code{nov} to reflect this.
This might later be expanded to @code{various}, which will be a mixture
-of HEADs and NOV lines, but this is currently not supported by Gnus.
+of HEADs and NOV lines, but this is currently not supported by Gnus.
If @var{fetch-old} is non-@code{nil} it says to try fetching "extra
headers", in some meaning of the word. This is generally done by
If the return value is @code{nov}, the data buffer should contain
@dfn{network overview database} lines. These are basically fields
-separated by tabs.
+separated by tabs.
@example
nov-buffer = *nov-line
@end example
For a closer look at what should be in those fields,
-@pxref{Headers}.
+@pxref{Headers}.
@item (nnchoke-open-server SERVER &optional DEFINITIONS)
@var{server} is here the virtual server name. @var{definitions} is a
-list of @code{(VARIABLE VALUE)} pairs that define this virtual server.
+list of @code{(VARIABLE VALUE)} pairs that define 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.
+server. In fact, it should do so.
If the server is opened already, this function should return a
non-@code{nil} value. There should be no data returned.
should be killed. (Not the @code{nntp-server-buffer}, though.) This
function is generally only called when Gnus is shutting down.
-There should be no data returned.
+There should be no data returned.
@item (nnchoke-server-opened &optional SERVER)
@item (nnchoke-status-message &optional SERVER)
-This function should return the last error message from @var{server}.
+This function should return the last error message from @var{server}.
There should be no data returned.
@item (nnchoke-request-group GROUP &optional SERVER FAST)
Get data on @var{group}. This function also has the side effect of
-making @var{group} the current group.
+making @var{group} the current group.
If @var{FAST}, don't bother to return useful data, just make @var{group}
the current group.
@item (nnchoke-close-group GROUP &optional SERVER)
Close @var{group} and free any resources connected to it. This will be
-a no-op on most backends.
+a no-op on most backends.
There should be no data returned.
@item (nnchoke-request-list &optional SERVER)
Return a list of all groups available on @var{server}. And that means
-@emph{all}.
+@emph{all}.
Here's an example from a server that only carries two groups:
The flag says whether the group is read-only (@samp{n}), is moderated
(@samp{m}), is dead (@samp{x}), is aliased to some other group
-(@samp{=other-group}) or none of the above (@samp{y}).
+(@samp{=other-group}) or none of the above (@samp{y}).
@item (nnchoke-request-post &optional SERVER)
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.
+There should be no result data from this function.
@end table
There should be no result data from this function.
+@item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
+
+Set/remove/add marks on articles. Normally Gnus handles the article
+marks (such as read, ticked, expired etc) internally, and store them in
+@code{~/.newsrc.eld}. Some backends (such as IMAP) however carry all
+information about the articles on the server, so Gnus need to propagate
+the mark information to the server.
+
+ACTION is a list of mark setting requests, having this format:
+
+@example
+(RANGE ACTION MARK)
+@end example
+
+Range is a range of articles you wish to update marks on. Action is
+@code{set}, @code{add} or @code{del}, respectively used for removing all
+existing marks and setting them as specified, adding (preserving the
+marks not mentioned) mark and removing (preserving the marks not
+mentioned) marks. Mark is a list of marks; where each mark is a
+symbol. Currently used marks are @code{read}, @code{tick}, @code{reply},
+@code{expire}, @code{killed}, @code{dormant}, @code{save},
+@code{download} and @code{unsend}, but your backend should, if possible,
+not limit itself to theese.
+
+Given contradictory actions, the last action in the list should be the
+effective one. That is, if your action contains a request to add the
+@code{tick} mark on article 1 and, later in the list, a request to
+remove the mark on the same article, the mark should in fact be removed.
+
+An example action list:
+
+@example
+(((5 12 30) 'del '(tick))
+ ((10 . 90) 'add '(read expire))
+ ((92 94) 'del '(read)))
+@end example
+
+The function should return a range of articles it wasn't able to set the
+mark on (currently not used for anything).
+
+There should be no result data from this function.
+
@item (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 @var{article} instead of the original
@var{mark}. If the backend doesn't care, it must return the original
-@var{mark}, and not @code{nil} or any other type of garbage.
+@var{mark}, and not @code{nil} or any other type of garbage.
The only use for this I can see is what @code{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.
+expirable.
There should be no result data from this function.
@item (nnchoke-request-group-description GROUP &optional SERVER)
The result data from this function should be a description of
-@var{group}.
+@var{group}.
@example
description-line = name <TAB> description eol
@item (nnchoke-request-create-group GROUP &optional SERVER)
-This function should create an empty group with name @var{group}.
+This function should create an empty group with name @var{group}.
There should be no return data.
numbers.) It is left up to the backend to decide how old articles
should be before they are removed by this function. If @var{force} is
non-@code{nil}, all @var{articles} should be deleted, no matter how new
-they are.
+they are.
This function should return a list of articles that it did not/was not
able to delete.
&optional LAST)
This function should move @var{article} (which is a number) from
-@var{group} by calling @var{accept-form}.
+@var{group} by calling @var{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
If @var{last} is @code{nil}, that means that there is a high likelihood
that there will be more requests issued shortly, so that allows some
-optimizations.
+optimizations.
The function should return a cons where the @code{car} is the group name and
the @code{cdr} is the article number that the article was entered as.
-There should be no data returned.
+There should be no data returned.
@item (nnchoke-request-accept-article GROUP &optional SERVER LAST)
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.)
+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 @code{nnoo}.
+package called @code{nnoo}.
To inherit functions from other backends (and allow other backends to
inherit functions from the current backend), you should use the
@item defvoo
This macro is equivalent to @code{defvar}, but registers the variable as
a public server variable. Most state-oriented variables should be
-declared with @code{defvoo} instead of @code{defvar}.
+declared with @code{defvoo} instead of @code{defvar}.
In addition to the normal @code{defvar} parameters, it takes a list of
variables in the parent backends to map the variable to when executing
This means that @code{nnml-current-directory} will be set to
@code{nndir-directory} when an @code{nnml} function is called on behalf
-of @code{nndir}. (The same with @code{nnmh}.)
+of @code{nndir}. (The same with @code{nnmh}.)
@item nnoo-define-basics
This macro defines some common functions that almost all backends should
@item mail
This is a mailish backend---followups should (probably) go via mail.
@item post
-This is a newsish backend---followups should (probably) go via news.
+This is a newsish backend---followups should (probably) go via news.
@item post-mail
This backend supports both mail and news.
@item none
This is neither a post nor mail backend---it's something completely
-different.
+different.
@item respool
It supports respooling---or rather, it is able to modify its source
articles and groups.
@item prompt-address
The user should be prompted for an address when doing commands like
@kbd{B} in the group buffer. This is true for backends like
-@code{nntp}, but not @code{nnmbox}, for instance.
+@code{nntp}, but not @code{nnmbox}, for instance.
@end table
One of the things that separate the mail backends from the rest of the
backends is the heavy dependence by the mail backends on common
functions in @file{nnmail.el}. For instance, here's the definition of
-@code{nnml-request-scan}:
+@code{nnml-request-scan}:
@lisp
(deffoo nnml-request-scan (&optional group server)
It simply calls @code{nnmail-get-new-mail} with a few parameters,
and @code{nnmail} takes care of all the moving and splitting of the
-mail.
+mail.
This function takes four parameters.
@code{nnmail-get-new-mail} will call @var{backend}@code{-save-mail} to
save each article. @var{backend}@code{-active-number} will be called to
-find the article number assigned to this article.
+find the article number assigned to this article.
The function also uses the following variables:
@var{backend}@code{-get-new-mail} (to see whether to get new mail for
@node Score File Syntax
@subsection Score File Syntax
-Score files are meant to be easily parsable, but yet extremely
+Score files are meant to be easily parseable, but yet extremely
mallable. It was decided that something that had the same read syntax
as an Emacs Lisp list would fit that spec.
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" /
+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 [ "" /
+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" /
+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 [ "" /
+number-match = "(" <integer> [ "" / [ space score [ "" /
space date [ "" / [ space number-match-t ] ] ] ] ] ")"
number-match-t = "nil" / "=" / "<" / ">" / ">=" / "<="
-date-match = "(" quote <string> quote [ "" / [ space score [ "" /
+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
+optional-atom = adapt / local / eval
mark = "mark" space nil-or-number
nil-or-number = "nil" / <integer>
expunge = "expunge" space nil-or-number
@end example
Any unrecognized elements in a score file should be ignored, but not
-discarded.
+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
These slots are, in order: @code{number}, @code{subject}, @code{from},
@code{date}, @code{id}, @code{references}, @code{chars}, @code{lines},
-@code{xref}. There are macros for accessing and setting these
-slots---they all have predictable names beginning with
+@code{xref}, and @code{extra}. There are macros for accessing and
+setting these slots---they all have predictable names beginning with
@code{mail-header-} and @code{mail-header-set-}, respectively.
-The @code{xref} slot is really a @code{misc} slot. Any extra info will
-be put in there.
+All these slots contain strings, except the @code{extra} slot, which
+contains an alist of header/value pairs (@pxref{To From Newsgroups}).
@node Ranges
@subsection Ranges
@sc{gnus} introduced a concept that I found so useful that I've started
-using it a lot and have elaborated on it greatly.
+using it a lot and have elaborated on it greatly.
The question is simple: If you have a large amount of objects that are
identified by numbers (say, articles, to take a @emph{wild} example)
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.
+sequence.
@example
(1 2 3 4 5 6 10 11 12)
range = simple-range / normal-range
simple-range = "(" number " . " number ")"
normal-range = "(" start-contents ")"
-contents = "" / simple-range *[ " " contents ] /
+contents = "" / simple-range *[ " " contents ] /
number *[ " " contents ]
@end example
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.)
+sequences.)
@node Group Info
second is a more complex one:
@example
-("no.group" 5 (1 . 54324))
+("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 . t) (to-address "ding@@gnus.org")))
+ ((auto-expire . t) (to-address . "ding@@gnus.org")))
@end example
The first element is the @dfn{group name}---as Gnus knows the group,
Here's a BNF definition of the group info format:
@example
-info = "(" group space ralevel space read
+info = "(" group space ralevel space read
[ "" / [ space marks-list [ "" / [ space method [ "" /
- space parameters ] ] ] ] ] ")"
+ space parameters ] ] ] ] ] ")"
group = quote <string> quote
ralevel = rank / level
level = <integer in the range of 1 to inf>
@item A
The current article number---the @code{gnus-summary-article-number}
-function.
+function.
@item H
The current article header---the @code{gnus-summary-article-header}
-function.
+function.
@item g
The current group name---the @code{gnus-group-group-name}
-function.
+function.
@end table
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.
+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
The active file lists all groups available on the server in
question. It also lists the highest and lowest current article numbers
-in each group.
+in each group.
Here's an excerpt from a typical active file:
@item
Q: What is an experienced Emacs user?
-@item
+@item
A: A person who wishes that the terminal had pedals.
@end itemize
@end iftex
@c End:
-
projects / elisp / gnus.git- / blobdiff