xemacs-beta: man/gnus.texi comparison

comparison man/gnus.texi @ 104:cf808b4c4290 r20-1b4

Import from CVS: tag r20-1b4

author	cvs
date	Mon, 13 Aug 2007 09:16:51 +0200
parents	4be1180a9e89
children	360340f9fd5f

comparison

equal deleted inserted replaced

-:30eda07fe280
+:cf808b4c4290
 (add-hook 'gnus-save-standard-newsrc-hook 'turn-off-backup)
 @end lisp
 @vindex gnus-init-file
 When Gnus starts, it will read the @code{gnus-site-init-file}
-(@file{.../site-lisp/gnus.el} by default) and @code{gnus-init-file}
+(@file{.../site-lisp/gnus} by default) and @code{gnus-init-file}
-(@file{~/.gnus.el} by default) files.  These are normal Emacs Lisp files
+(@file{~/.gnus} by default) files.  These are normal Emacs Lisp files
-and can be used to avoid cluttering your @file{.emacs} and
+and can be used to avoid cluttering your @file{~/.emacs} and
-@file{site-init} files with Gnus stuff.
+@file{site-init} files with Gnus stuff.  Gnus will also check for files
+with the same names as these, but with @file{.elc} and @file{.el}
+suffixes.  In other words, if you have set @code{gnus-init-file} to
+@file{~/.gnus}, it will look for @file{~/.gnus.elc}, @file{~/.gnus.el},
+and finally @file{~/.gnus} (in this order).
 @node Auto Save
 @section Auto Save
 @cindex dribble file
 times you start Gnus.
 @item gnus-startup-hook
 @vindex gnus-startup-hook
 A hook that is run after starting up Gnus successfully.
+@item gnus-started-hook
+@vindex gnus-started-hook
+A hook that is run as the very last thing after starting up Gnus
+successfully.
 @item gnus-check-bogus-newsgroups
 @vindex gnus-check-bogus-newsgroups
 If non-@code{nil}, Gnus will check for and delete all bogus groups at
 startup.  A @dfn{bogus group} is a group that you have in your
 variable to a really low number, you'll find that Gnus will gather
 everything in sight into one thread, which isn't very helpful.
 @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.
+use a fuzzy string comparison algorithm on the subjects (@pxref{Fuzzy
+Matching}).
 @item gnus-simplify-subject-fuzzy-regexp
 @vindex gnus-simplify-subject-fuzzy-regexp
 This can either be a regular expression or list of regular expressions
 that match strings that will be removed from subjects if fuzzy subject
 you can fiddle with @code{gnus-thread-operation-ignore-subject}.  If is
 is non-@code{nil} (which it is by default), subjects will be ignored
 when doing thread commands.  If this variable is @code{nil}, articles in
 the same thread with different subjects will not be included in the
 operation in question.  If this variable is @code{fuzzy}, only articles
-that have subjects that are fuzzily equal will be included.
+that have subjects that are fuzzily equal will be included (@pxref{Fuzzy
+Matching}).
 @node Sorting
 @section Sorting
 @node Archived Messages
 @section Archived Messages
 @cindex archived messages
 @cindex sent messages
-Gnus provides a few different methods for storing the mail you send.
+Gnus provides a few different methods for storing the mail and news you
-The default method is to use the @dfn{archive virtual server} to store
+send.  The default method is to use the @dfn{archive virtual server} to
-the mail.  If you want to disable this completely, the
+store the messages.  If you want to disable this completely, the
 @code{gnus-message-archive-group} variable should be @code{nil}, which
 is the default.
 @vindex gnus-message-archive-method
 @code{gnus-message-archive-method} says what virtual server Gnus is to
 group.  If the group gets really big and annoying, you can simply rename
 if (using @kbd{G r} in the group buffer) to something
 nice---@samp{misc-mail-september-1995}, or whatever.  New messages will
 continue to be stored in the old (now empty) group.
-That's the default method of archiving sent mail.  Gnus also a different
+That's the default method of archiving sent messages.  Gnus also a
-way for the people who don't like the default method.  In that case you
+different way for the people who don't like the default method.  In that
-should set @code{gnus-message-archive-group} to @code{nil}; this will
+case you should set @code{gnus-message-archive-group} to @code{nil};
-disable archiving.
+this will disable archiving.
 XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
 use a different value for @code{gnus-message-archive-group} there.
 @table @code
 If you want to have greater control over what group to put each
 message in, you can set this variable to a function that checks the
 current newsgroup name and then returns a suitable group name (or list
 of names).
+This variable can be used instead of @code{gnus-message-archive-group},
+but the latter is the preferred method.
 @end table
 @c @node Posting Styles
 @c @section Posting Styles
 @item s
 Substring matching.
 @item f
-Fuzzy matching.
+Fuzzy matching (@pxref{Fuzzy Matching}).
 @item r
 Regexp matching
 @end table
 @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 ce.
+represented by the number of days since December 31, 1 BCE.
 @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
 exploited---the following rule will raise the score on all followups to
 myself:
 @lisp
 ("references"
-("<x6[0-9a-z]+\\.fsf@.*eyesore.no>" 1000 nil r))
+("<x6[0-9a-z]+\\.fsf@@.*eyesore.no>" 1000 nil r))
 @end lisp
 Whether it's the first two or first three characters that are ``yours''
 is system-dependent.
 * NoCeM::                      How to avoid spam and other fatty foods.
 * Picons::                     How to display pictures of what your reading.
 * Undo::                       Some actions can be undone.
 * Moderation::                 What to do if you're a moderator.
 * XEmacs Enhancements::        There are more pictures and stuff under XEmacs.
+* Fuzzy Matching::             What's the big fuzz?
 * Various Various::            Things that are really various.
 @end menu
 @node Process/Prefix
 @vindex gnus-xmas-modeline-glyph
 A glyph displayed in all Gnus mode lines.  It is a tiny gnu head by
 default.
 @end table
+@node Fuzzy Matching
+@section Fuzzy Matching
+@cindex fuzzy matching
+Gnus provides @dfn{fuzzy matching} of @code{Subject} lines when doing
+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}
+means, and the implementation has changed over time.
+Basically, it tries to remove all noise from lines before comparing.
+@samp{Re: }, parenthetical remarks, white space, and so on, are filtered
+out of the strings before comparing the results.  This often leads to
+adequate results---even when faced with strings generated by text
+manglers masquerading as newsreaders.
 @node Various Various
 @section Various Various
 @cindex mode lines
 @item (nnchoke-request-update-info GROUP INFO &optional SERVER)
 A Gnus group info (@pxref{Group Info}) is handed to the backend for
 alterations.  This comes in handy if the backend really carries all the
-information (as is the case with virtual an imap groups).  This function
+information (as is the case with virtual and imap groups).  This
-should destructively alter the info to suit its needs, and should return
+function should destructively alter the info to suit its needs, and
-the (altered) group info.
+should return the (altered) group info.
 There should be no result data from this function.
 @item (nnchoke-request-type GROUP &optional ARTICLE)

Mercurial > hg > xemacs-beta

comparison man/gnus.texi @ 104:cf808b4c4290 r20-1b4