|
a/src/doc/user/usermanual.sgml |
|
b/src/doc/user/usermanual.sgml |
|
... |
|
... |
| 567 |
|
567 |
|
| 568 |
</sect2>
|
568 |
</sect2>
|
| 569 |
|
569 |
|
| 570 |
|
570 |
|
| 571 |
<sect2 id="rcl.indexing.config.gui">
|
571 |
<sect2 id="rcl.indexing.config.gui">
|
| 572 |
<title>The indexing configuration GUI</title>
|
572 |
<title>The index configuration GUI</title>
|
| 573 |
|
573 |
|
| 574 |
<para>Most parameters for a given indexing configuration can
|
574 |
<para>Most parameters for a given index configuration can
|
| 575 |
be set from a <command>recoll</command> GUI running on this
|
575 |
be set from a <command>recoll</command> GUI running on this
|
| 576 |
configuration (either as default, or by setting
|
576 |
configuration (either as default, or by setting
|
| 577 |
<envar>RECOLL_CONFDIR</envar> or the <option>-c</option>
|
577 |
<envar>RECOLL_CONFDIR</envar> or the <option>-c</option>
|
| 578 |
option.)</para>
|
578 |
option.)</para>
|
| 579 |
|
579 |
|
|
... |
|
... |
| 4217 |
index (<literal>indexStripChars = 1</literal> for
|
4217 |
index (<literal>indexStripChars = 1</literal> for
|
| 4218 |
now.</para>
|
4218 |
now.</para>
|
| 4219 |
</listitem>
|
4219 |
</listitem>
|
| 4220 |
</varlistentry>
|
4220 |
</varlistentry>
|
| 4221 |
|
4221 |
|
|
|
4222 |
<varlistentry><term><varname>maxTermExpand</varname></term>
|
|
|
4223 |
<listitem><para>Maximum expansion count for a single term (e.g.:
|
|
|
4224 |
when using wildcards). The default of 10000 is reasonable and
|
|
|
4225 |
will avoid queries that appear frozen while the engine is
|
|
|
4226 |
walking the term list.</para>
|
|
|
4227 |
</listitem>
|
|
|
4228 |
</varlistentry>
|
|
|
4229 |
|
|
|
4230 |
<varlistentry><term><varname>maxXapianClauses</varname></term>
|
|
|
4231 |
<listitem><para>Maximum number of elementary clauses we can add
|
|
|
4232 |
to a single Xapian query. In some cases, the result of term
|
|
|
4233 |
expansion can be multiplicative, and we want to avoid using
|
|
|
4234 |
excessive memory. The default of 100 000 should be both
|
|
|
4235 |
high enough in most cases and compatible with current
|
|
|
4236 |
typical hardware configurations.</para>
|
|
|
4237 |
</listitem>
|
|
|
4238 |
</varlistentry>
|
|
|
4239 |
|
| 4222 |
<varlistentry><term><varname>nonumbers</varname></term>
|
4240 |
<varlistentry><term><varname>nonumbers</varname></term>
|
| 4223 |
<listitem><para>If this set to true, no terms will be generated
|
4241 |
<listitem><para>If this set to true, no terms will be generated
|
| 4224 |
for numbers. For example "123", "1.5e6", 192.168.1.4, would not
|
4242 |
for numbers. For example "123", "1.5e6", 192.168.1.4, would not
|
| 4225 |
be indexed ("value123" would still be). Numbers are often quite
|
4243 |
be indexed ("value123" would still be). Numbers are often quite
|
| 4226 |
interesting to search for, and this should probably not be set
|
4244 |
interesting to search for, and this should probably not be set
|