The query specifies only one term for retrieving all documents which contain the term. e.g.,
namazu
The query specifies two or more terms for retrieving all
documents which contain both terms. You can insert the
and
operator between the terms. e.g.,
Linux and Netscape
You can omit the and
operator. Terms which is
separated by one ore more spaces is assumed to be AND query.
The query specifies two or more terms for retrieving all
documents which contain either term. You can insert the
or
operator between the terms.
e.g.,
Linux or FreeBSD
The query specifies two or more terms for retrieving all
documents which contain a first term but doesn't contain the
following terms. You can insert the not
operator between the terms to do NOT query. e.g.,
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 which consists of two or more terms
by surrounding them with double quotes like
"..."
or with braces like {...}
.
In Namazu, precision of phrase searching is not 100 %,
so it causes wrong results occasionally. e.g.,
{GNU Emacs}
The are three types of substring matching searching.
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 offers generally Perl compatible flavor.
e.g.,
/pro(gram|blem)s?/
You can limit your search to specific fields such as
Subject:
, From:
,
Message-Id:
. It's especially convenient for
Mail/News documents. e.g.,
+subject:Linux
Linux
in a Subject:
field)
+subject:"GNU Emacs"
GNU Emacs
in a Subject:
field)
+from:foo@bar.jp
foo@bar.jp
in a From:
field)
+message-id:<199801240555.OAA18737@foo.bar.jp>
Message-Id:
)
TCP/IP
. Since this handling isn't complete,
you can describe TCP and IP
instead of
TCP/IP
, but it may cause noisy results.
and
,
or
or not
simply as terms, you can
surround them respectively with double quotes like "..."
or braces like {...}
.