.TH tracker-search 1 "July 2009" GNU "User Commands"

.SH NAME
tracker-search \- Search for content by type or across all types

.SH SYNOPSIS
\fBtracker search\fR [\fIoptions\fR...] [[\fIexpression1\fR] ...]

.SH DESCRIPTION
.B tracker search
searches all indexed content for \fIexpression\fR. The resource in
which \fIexpression\fR matches must exist (see 
.B \-\-all
for more information). All results are returned in ascending order. In
all cases, if no \fIexpression\fR is given for an argument (like 
.B \-\-folders
for example) then ALL items in that category are returned instead.
.TP
\fIexpression\fR
One or more terms to search. The default operation is a logical AND.
For logical OR operations, see -r.

.SH OPTIONS
.TP
.B \-f, \-\-files
Search for files of any type matching \fIexpression\fR (optional).
.TP
.B \-s, \-\-folders
Search for folders matching \fIexpression\fR (optional).
.TP
.B \-m, \-\-music
Search for music files matching \fIexpression\fR (optional).
.TP
.B \-\-music\-albums
Search for music albums matching \fIexpression\fR (optional).
.TP
.B \-\-music\-artists
Search for music artists matching \fIexpression\fR (optional).
.TP
.B \-i, \-\-images
Search for images matching \fIexpression\fR (optional).
.TP
.B \-v, \-\-videos
Search for videos matching \fIexpression\fR (optional).
.TP
.B \-t, \-\-documents
Search for documents matching \fIexpression\fR (optional).
.TP
.B \-e, \-\-emails
Search for emails matching \fIexpression\fR (optional). Returns a list
of subjects for emails found.
.TP
.B \-c, \-\-contacts
Search for contacts matching \fIexpression\fR (optional). Returns a list
of names and email addresses found.
.TP
.B \-\-software
Search for software installed matching \fIexpression\fR (optional). Returns a list
of desktop files and application titles found.
.TP
.B \-\-software\-categories
Search for software categories matching \fIexpression\fR (optional). Returns a list
of urns and their categories (e.g. Settings, Video, Utility, etc).
.TP
.B \-\-feeds
Search through RSS feed information matching \fIexpression\fR (optional). Returns a list
of those found.
.TP
.B \-b, \-\-bookmarks
Search through bookmarks matching \fIexpression\fR (optional). Returns a list
titles and links for each bookmark found.
.TP
.B \-l, \-\-limit\fR=<\fIlimit\fR>
Limit search to \fIlimit\fR results. The default is 10 or 512 with \-\-disable\-snippets.
.TP
.B \-o, \-\-offset\fR=<\fIoffset\fR>
Offset the search results by \fIoffset\fR. For example, start at item number 10
in the results. The default is 0.
.TP
.B \-r, \-\-or\-operator
Use OR for search terms instead of AND (the default)
.TP
.B \-d, \-\-detailed
Show the unique URN associated with each search result. This does not
apply to \-\-music\-albums and \-\-music\-artists.
.TP
.B \-a, \-\-all
Show results which might not be available. This might bebecause a
removable media is not mounted for example. Without this option,
resources are only shown if they exist. This option applies to all
command line switches except
.TP
.B \-\-disable\-snippets
Results are shown with snippets. Snippets are context around the word
that was searched for in the first place. This gives some idea of if
the resource found is the right one. Snippets require Full Text Search
to be compile time enabled AND to not be disabled with
\-\-disable\-fts. Using \-\-disable\-snippets only shows the resources
which matched, no context is provided about where the match occurred.
.TP
.B \-\-disable\-fts
If Full Text Search (FTS) is available, this option allows it to be
disabled for one off searches. This returns results slightly
using particular properties to match the search terms (like "nie:title")
instead of looking for the search terms amongst ALL properties. It is
more limiting to do this, but sometimes searching without FTS can
yield better results if the FTS ranking is off.
.TP
.B \-\-disable\-color
This disables any ANSI color use on the command line. By default this
is enabled to make it easier to see results.

.SH ENVIRONMENT
.TP
.B TRACKER_SPARQL_BACKEND
This option allows you to choose which backend you use for connecting
to the database. This choice can limit your functionality. There are
three settings.

With "\fBdirect\fR" the connection to the database is made directly to
the file itself on the disk, there is no intermediary daemon or
process. The "\fBdirect\fR" approach is purely \fIread-only\fR.

With "\fBbus\fR" the \fBtracker-store\fR process is used to liase with
the database queuing all requests and managing the connections via an
IPC / D-Bus. This adds a small overhead \fIBUT\fR this is the only
approach you can use if you want to \fIwrite\fR to the database.

With "\fBauto\fR" the backend is decided for you, much like it would
be if this environment variable was undefined.

.SH SEE ALSO
.BR tracker-store (1),
.BR tracker-stats (1),
.BR tracker-tag (1),
.BR tracker-info (1).