This query specifies only one term for retrieving all of the documents which contain that term, for example:
namazu
This query specifies two or more terms for retrieving all of the documents
which contain both terms. Insert the and operator
between the terms, e.g.
Linux and Netscape
You can omit the and operator. Terms which are
separated by one ore more spaces are assumed to be an AND query.
This query specifies two or more terms for retrieving all documents which
contain any one term. Insert the or operator between
the terms, e.g.
Linux or FreeBSD
This query specifies two or more terms for retrieving all of the documents
which contain a first term but do not contain the following terms. Insert the
not operator between the terms, for example:
Linux not UNIX
You can group queries by surrounding them by parentheses. The parentheses should be separated by one or more spaces. e.g.
( Linux or FreeBSD ) and Netscape not Windows
You can search for a phrase that consists of two or more terms by surrounding
them with double quotation marks or braces such as "..." and {...}. In Namazu,
the precision of phrase searching is not 100 %, so wrong results may
occasionally occur. Example:
{GNU Emacs}
The are three types of searching by substring matching.
inter* (terms which begin with
inter)
*text* (terms which contain text)
*net (terms which terminated with
net) You can use regular expressions for pattern matching. The regular expressions
must be surrounded by slashes like /.../. Namazu
uses Ruby's regular regular expressions
engine. It generally offers a Perl compatible
flavor. e.g.,
/pro(gram|blem)s?/
You can limit your search to specific fields such as Subject:,
From:, Message-Id:. This feature is especially
convenient for Mail/News documents, for example:
+subject:LinuxLinux in a Subject: field)
+subject:"GNU Emacs"GNU Emacs in a Subject:
field)
+from:foo@bar.jpfoo@bar.jp in a From: field)
+message-id:<199801240555.OAA18737@foo.bar.jp>Message-Id:) TCP/IP.
Since this method of handling isn't complete, you can also describe the term
as TCP and IP instead of TCP/IP, but it may cause
noisy results.
and, or or not simply as terms,
you can surround them with double quotes or braces like "..." or {...}.