|
a/src/doc/user/usermanual.sgml |
|
b/src/doc/user/usermanual.sgml |
|
... |
|
... |
| 2487 |
<itemizedlist>
|
2487 |
<itemizedlist>
|
| 2488 |
|
2488 |
|
| 2489 |
<listitem><para><literal>dir</literal> for filtering the
|
2489 |
<listitem><para><literal>dir</literal> for filtering the
|
| 2490 |
results on file location (Ex:
|
2490 |
results on file location (Ex:
|
| 2491 |
<literal>dir:/home/me/somedir</literal>). <literal>-dir</literal>
|
2491 |
<literal>dir:/home/me/somedir</literal>). <literal>-dir</literal>
|
| 2492 |
also works to find results out of the specified directory, only
|
2492 |
also works to find results not in the specified directory
|
| 2493 |
after release 1.15.8. A tilde inside the value will be expanded to
|
2493 |
(release >= 1.15.8). A tilde inside the value will be expanded
|
| 2494 |
the home directory. <literal>dir</literal> is not a regular field
|
2494 |
to the home directory. Wildcards will <emphasis>not</emphasis>
|
| 2495 |
and only one value makes sense in a query (you can't use
|
2495 |
be expanded. You cannot use <literal>OR</literal> with
|
| 2496 |
<literal>dir:dir1 OR dir:dir2</literal>). Relative paths make
|
2496 |
<literal>dir</literal> clauses (this restriction may go away in
|
| 2497 |
sense, for example,
|
2497 |
the future).</para>
|
|
|
2498 |
|
|
|
2499 |
<para>Relative paths also make sense, for example,
|
| 2498 |
<literal>dir:share/doc</literal> would match either
|
2500 |
<literal>dir:share/doc</literal> would match either
|
| 2499 |
<filename>/usr/share/doc</filename> or
|
2501 |
<filename>/usr/share/doc</filename> or
|
| 2500 |
<filename>/usr/local/share/doc</filename> </para>
|
2502 |
<filename>/usr/local/share/doc</filename> </para>
|
|
|
2503 |
|
|
|
2504 |
<para>Several <literal>dir</literal> clauses can be specified,
|
|
|
2505 |
both positive and negative. For example the following makes sense:
|
|
|
2506 |
<programlisting>
|
|
|
2507 |
dir:recoll dir:src -dir:utils -dir:common
|
|
|
2508 |
</programlisting> This would select results which have both
|
|
|
2509 |
<filename>recoll</filename> and <filename>src</filename> in the
|
|
|
2510 |
path (in any order), and which have not either
|
|
|
2511 |
<filename>utils</filename> or
|
|
|
2512 |
<filename>common</filename>.</para>
|
|
|
2513 |
|
|
|
2514 |
<para>Another special aspect of <literal>dir</literal> clauses is
|
|
|
2515 |
that the values in the index are not transcoded to UTF-8, and
|
|
|
2516 |
never lower-cased or unaccented, but stored as binary. This means
|
|
|
2517 |
that you need to enter the values in the exact lower or upper
|
|
|
2518 |
case, and that searches for names with diacritics may sometimes
|
|
|
2519 |
be impossible because of character set conversion
|
|
|
2520 |
issues. Non-ASCII UNIX file paths are an unending source of
|
|
|
2521 |
trouble and are best avoided.</para>
|
|
|
2522 |
|
|
|
2523 |
<para>You need to use double-quotes around the path value if it
|
|
|
2524 |
contains space characters.</para>
|
|
|
2525 |
|
| 2501 |
</listitem>
|
2526 |
</listitem>
|
| 2502 |
|
2527 |
|
| 2503 |
<listitem><para><literal>size</literal> for filtering the
|
2528 |
<listitem><para><literal>size</literal> for filtering the
|
| 2504 |
results on file size. Example:
|
2529 |
results on file size. Example:
|
| 2505 |
<literal>size<10000</literal>. You can use
|
2530 |
<literal>size<10000</literal>. You can use
|