nnir
-* What is nnir:: What does nnir do.
+* What is nnir?:: What does nnir do.
* Basic Usage:: How to perform simple searches.
* Setting up nnir:: How to set up nnir.
@section Foreign Groups
@cindex foreign groups
+If you recall how to subscribe to servers (@pxref{Finding the News})
+you will remember that @code{gnus-secondary-select-methods} and
+@code{gnus-select-method} let you write a definition in Emacs Lisp of
+what servers you want to see when you start up. The alternate
+approach is to use foreign servers and groups. ``Foreign'' here means
+they are not coming from the select methods. All foreign server
+configuration and subscriptions are stored only in the
+@file{~/.newsrc.eld} file.
+
Below are some group mode commands for making and editing general foreign
groups, as well as commands to ease the creation of a few
special-purpose groups. All these commands insert the newly created
(concat "mail." (format-time-string "%Y-%m")))))
@end lisp
-@c (XEmacs 19.13 doesn't have @code{format-time-string}, so you'll have to
-@c use a different value for @code{gnus-message-archive-group} there.)
-
Now, when you send a message off, it will be stored in the appropriate
group. (If you want to disable storing for just one particular message,
you can just remove the @code{Gcc} header that has been inserted.) The
within gnus.
@menu
-* What is nnir:: What does nnir do?
+* What is nnir?:: What does @code{nnir} do?
* Basic Usage:: How to perform simple searches.
-* Setting up nnir:: How to set up nnir.
+* Setting up nnir:: How to set up @code{nnir}.
@end menu
-@node What is nnir
-@subsection What is nnir
+@node What is nnir?
+@subsection What is nnir?
-@code{nnir} is a gnus interface to a number of tools for searching
+@code{nnir} is a Gnus interface to a number of tools for searching
through mail and news repositories. Different backends (like
@code{nnimap} and @code{nntp}) work with different tools (called
-@dfn{engines} in nnir lingo), but all use the same basic search
+@dfn{engines} in @code{nnir} lingo), but all use the same basic search
interface.
The @code{nnimap} and @code{gmane} search engines should work with no
configuration. Other engines require a local index that needs to be
created and maintained outside of Gnus.
+
@node Basic Usage
@subsection Basic Usage
groups with different search engines you will be prompted for the
special search features for each engine separately.
+
@node Setting up nnir
@subsection Setting up nnir
named @code{home} you can use
@lisp
-(setq gnus-secondary-select-methods '(
- (nnml "home"
- (nnimap-address "localhost")
- (nnir-search-engine namazu))))
+(setq gnus-secondary-select-methods
+ '((nnml "home"
+ (nnimap-address "localhost")
+ (nnir-search-engine namazu))))
@end lisp
Alternatively you might want to use a particular engine for all servers
Documentation for swish++ may be found at the swish++ sourceforge page:
@uref{http://swishplusplus.sourceforge.net}
+@table @code
+
+@item nnir-swish++-program
+The name of the swish++ executable. Defaults to @code{search}
+
+@item nnir-swish++-additional-switches
+A list of strings to be given as additional arguments to
+swish++. @code{nil} by default.
+
+@item nnir-swish++-remove-prefix
+The prefix to remove from each file name returned by swish++ in order
+to get a group name. By default this is @code{$HOME/Mail}.
+
+@end table
+
@node The swish-e Engine
@subsubsection The swish-e Engine
Documentation for swish-e may be found at the swish-e homepage
@uref{http://swish-e.org}
+@table @code
+
+@item nnir-swish-e-program
+The name of the swish-e search program. Defaults to @code{swish-e}.
+
+@item nnir-swish-e-additional-switches
+A list of strings to be given as additional arguments to
+swish-e. @code{nil} by default.
+
+@item nnir-swish-e-remove-prefix
+The prefix to remove from each file name returned by swish-e in order
+to get a group name. By default this is @code{$HOME/Mail}.
+
+@end table
+
@node The namazu Engine
@subsubsection The namazu Engine
@node The hyrex Engine
@subsubsection The hyrex Engine
-FIXME: Add documentation.
+This engine is obsolete.
@node Customizations
@subsubsection Custimozations