1tracker-tag(1) User Commands tracker-tag(1)
2
3
4
6 tracker-tag - Add, remove and list tags.
7
8
10 tracker tag FILE1 [FILE2 ...] [-l <limit>] [-o <offset>] [-r]
11 tracker tag -t [[TAG1] [TAG2] ...] [-s] [-r]
12 tracker tag -a <TAG> [-e <description>]
13 tracker tag -d <TAG>
14
15
17 List tags for local files or by the tag labels themselves if -t is
18 used.
19
20 It's also possible to manage tags with the -a and and -d options.
21
22 The FILE argument can be either a local path or a URI. It also does not
23 have to be an absolute path.
24
25
27 -t, --list
28 List all tags. Results include the number of files associated
29 with that tag and the tag's unique identifier. You can show the
30 files associated with each tag by using --show-files.
31
32 The TAG arguments are optional. If no TAG argument is specified,
33 all tags are listed. If one or more TAGs are given, either
34 matching tags are listed (OR condition). For example, this will
35 match any tags named either foo, bar or baz:
36
37 $ tracker-tag -t foo bar baz
38
39
40 -s, --show-files
41 Show the files associated with each tag. This option is ONLY
42 available WITH the --list option.
43
44 -a, --add=TAG
45 Add a tag with the name TAG. If no FILE arguments are specified,
46 the tag is simply created (if it didn'talready exist) and no
47 files are associated with it. Multiple FILE arguments can be
48 specified.
49
50 -d, --delete=TAG
51 Delete a tag with the name TAG. If no FILE arguments are speci‐
52 fied, the tag is deleted for ALL files. If FILE arguments are
53 specified, only those files have the TAG deleted.
54
55 -e, --description=STRING
56 This option ONLY applies when using --add and provides a
57 description to go with the tag label according to STRING.
58
59 -l, --limit=N
60 Limit search to N results. The default is 512.
61
62 -o, --offset=N
63 Offset the search results by N. For example, start at item num‐
64 ber 10 in the results. The default is 0.
65
66 -r, --and-operator
67 Use AND operator for search terms instead of OR (the default).
68 For example:
69
70 $ tracker-tag -s -t sliff sloff
71
72 Should show files in the database that have both the sliff and
73 sloff tags.
74
75
77 TRACKER_SPARQL_BACKEND
78 This option allows you to choose which backend you use for con‐
79 necting to the database. This choice can limit your functional‐
80 ity. There are three settings.
81
82 With "direct" the connection to the database is made directly to
83 the file itself on the disk, there is no intermediary daemon or
84 process. The "direct" approach is purely read-only.
85
86 With "bus" the tracker-store process is used to liase with the
87 database queuing all requests and managing the connections via
88 an IPC / D-Bus. This adds a small overhead BUT this is the only
89 approach you can use if you want to write to the database.
90
91 With "auto" the backend is decided for you, much like it would
92 be if this environment variable was undefined.
93
94
95 TRACKER_PRAGMAS_FILE
96 Tracker has a fixed set of PRAGMA settings for creating its
97 SQLite connection. With this environment variable pointing to a
98 text file you can override these settings. The file is a \n sep‐
99 arated list of SQLite queries to execute on any newly created
100 SQLite connection in tracker-store.
101
102
104 tracker-store(1), tracker-sparql(1), tracker-search(1), tracker-
105 info(1).
106
107
108
109GNU July 2009 tracker-tag(1)