tris/recoll
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: query language

Browse Source
This commit is contained in:
Jean-Francois Dockes 2012-03-07 08:35:02 +01:00
parent 7b5a891ee3
commit 1e28525e5a
1 changed files with 21 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
src/doc/user/usermanual.sgml
View File

@ -2015,8 +2015,8 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
capabilities as the complex search interface in the capabilities as the complex search interface in the
GUI.</para> GUI.</para>
<para>The language is roughly based on the <ulink <para>The language is roughly based on the (seemingly defunct)
url="http://www.xesam.org/main/XesamUserSearchLanguage95"> <ulink url="http://www.xesam.org/main/XesamUserSearchLanguage95">
Xesam</ulink> user search language specification.</para> Xesam</ulink> user search language specification.</para>
<para>If the results of a query language search puzzle you and you <para>If the results of a query language search puzzle you and you
@ -2079,10 +2079,11 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
<replaceable>title:"prejudice pride"</replaceable> is not the same as <replaceable>title:"prejudice pride"</replaceable> is not the same as
<replaceable>title:prejudice title:pride</replaceable>, and is <replaceable>title:prejudice title:pride</replaceable>, and is
unlikely to find a result.</para> unlikely to find a result.</para>
<para>Most Xesam phrase modifiers are unsupported, except for
<literal>l</literal> (small ell) to disable stemming, and <para>Modifiers can be set on a phrase clause, for exemple to specify
<literal>p</literal> to turn a phrase into a NEAR (unordered proximity) a proximity search (unordered). See
search. Exemple: <replaceable>"prejudice pride"p</replaceable></para> <link linkend="rcl.search.lang.modifiers">the modifier
section</link>.</para>
<para>&RCL; currently manages the following default fields:</para> <para>&RCL; currently manages the following default fields:</para>
<itemizedlist> <itemizedlist>
@ -2114,7 +2115,14 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
results on file location (Ex: results on file location (Ex:
<literal>dir:/home/me/somedir</literal>). <literal>-dir</literal> <literal>dir:/home/me/somedir</literal>). <literal>-dir</literal>
also works to find results out of the specified directory, only also works to find results out of the specified directory, only
after release 1.15.8.</para> after release 1.15.8. A tilde inside the value will be expanded to
the home directory. <literal>dir</literal> is not a regular field
and only one value makes sense in a query (you can't use
<literal>dir:dir1 OR dir:dir2</literal>). Relative paths make
sense, for example,
<literal>dir:share/doc</literal> would match either
<filename>/usr/share/doc</filename> or
<filename>/usr/local/share/doc</filename> </para>
</listitem> </listitem>
<listitem><para><literal>date</literal> for searching or filtering <listitem><para><literal>date</literal> for searching or filtering
@ -2198,7 +2206,7 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
field search possibilities may be different for you if someone field search possibilities may be different for you if someone
took care of the customisation.</para> took care of the customisation.</para>
<sect2> <sect2 id="rcl.search.lang.modifiers">
<title>Modifiers</title> <title>Modifiers</title>
<para>Some characters are recognized as search modifiers when found <para>Some characters are recognized as search modifiers when found