explicitely->explicitly
This commit is contained in:
@@ -69,12 +69,12 @@ filesystem paths. Must be defined at the top level of the configuration
|
||||
file, not in a subsection. Can contain files and directories. The database and
|
||||
configuration directories will automatically be added. The expressions
|
||||
are matched using 'fnmatch(3)' with the FNM_PATHNAME flag set by
|
||||
default. This means that '/' characters must be matched explicitely. You
|
||||
default. This means that '/' characters must be matched explicitly. You
|
||||
can set 'skippedPathsFnmPathname' to 0 to disable the use of FNM_PATHNAME
|
||||
(meaning that '/*/dir3' will match '/dir1/dir2/dir3'). The default value
|
||||
contains the usual mount point for removable media to remind you that it
|
||||
is a bad idea to have Recoll work on these (esp. with the monitor: media
|
||||
gets indexed on mount, all data gets erased on unmount). Explicitely
|
||||
gets indexed on mount, all data gets erased on unmount). Explicitly
|
||||
adding '/media/xxx' to the 'topdirs' variable will override
|
||||
this.</para></listitem></varlistentry>
|
||||
<varlistentry id="RCL.INSTALL.CONFIG.RECOLLCONF.SKIPPEDPATHSFNMPATHNAME">
|
||||
@@ -410,6 +410,10 @@ a directory between different configurations.</para></listitem></varlistentry>
|
||||
<term><varname>mboxcacheminmbs</varname></term>
|
||||
<listitem><para>Minimum mbox file size over which we cache the offsets. There is really no sense in caching offsets for small files. The
|
||||
default is 5 MB.</para></listitem></varlistentry>
|
||||
<varlistentry id="RCL.INSTALL.CONFIG.RECOLLCONF.MBOXMAXMSGMBS">
|
||||
<term><varname>mboxmaxmsgmbs</varname></term>
|
||||
<listitem><para>Maximum mbox member message size in megabytes. Size over which we assume that the mbox format is bad or we
|
||||
misinterpreted it, at which point we just stop processing the file.</para></listitem></varlistentry>
|
||||
<varlistentry id="RCL.INSTALL.CONFIG.RECOLLCONF.WEBCACHEDIR">
|
||||
<term><varname>webcachedir</varname></term>
|
||||
<listitem><para>Directory where we store the archived web pages. This is only used by the web history indexing code
|
||||
|
||||
@@ -1412,7 +1412,7 @@ alink="#0000FF">
|
||||
term generation</a>.</p>
|
||||
<p>Using multiple configurations implies a small level of
|
||||
command line or file manager usage. The user must
|
||||
explicitely create additional configuration directories,
|
||||
explicitly create additional configuration directories,
|
||||
the GUI will not do it. This is to avoid mistakenly
|
||||
creating additional directories when an argument is
|
||||
mistyped. Also, the GUI or the indexer must be launched
|
||||
@@ -3630,7 +3630,7 @@ fs.inotify.max_user_watches=32768
|
||||
spelling variations when no matching document were found.
|
||||
In some cases, both proper spellings and mispellings are
|
||||
present in the index, and it may be interesting to look
|
||||
for them explicitely.</p>
|
||||
for them explicitly.</p>
|
||||
<p>The term explorer tool (started from the toolbar icon
|
||||
or from the <span class="guilabel">Term explorer</span>
|
||||
entry of the <span class="guilabel">Tools</span> menu)
|
||||
@@ -4091,7 +4091,7 @@ fs.inotify.max_user_watches=32768
|
||||
history, but the amount is limited: old queries will
|
||||
eventually be forgotten. Also, important queries may be
|
||||
difficult to find among others. This is why both types of
|
||||
queries can also be explicitely saved to files, from the
|
||||
queries can also be explicitly saved to files, from the
|
||||
GUI menus: <span class="guimenu">File</span> →
|
||||
<span class="guimenuitem">Save last query / Load last
|
||||
query</span></p>
|
||||
@@ -5700,7 +5700,7 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
|
||||
<p>As in the past, capitalizing the first letter of a word
|
||||
will turn off its stem expansion and have no effect on
|
||||
case-sensitivity.</p>
|
||||
<p>You can also explicitely activate case and diacritics
|
||||
<p>You can also explicitly activate case and diacritics
|
||||
sensitivity by using modifiers with the query language.
|
||||
<code class="literal">C</code> will make the term
|
||||
case-sensitive, and <code class="literal">D</code> will
|
||||
@@ -8046,7 +8046,7 @@ for i in range(nres):
|
||||
build procedure (see above) installs the API package for
|
||||
the default system version (python) along with the main
|
||||
code. The package for other Python versions (e.g. python3
|
||||
if the system default is python2) must be explicitely
|
||||
if the system default is python2) must be explicitly
|
||||
built and installed.</p>
|
||||
<p>The <code class="filename">python/recoll/</code>
|
||||
directory contains the usual <code class=
|
||||
@@ -8479,7 +8479,7 @@ for i in range(nres):
|
||||
automatically be added. The expressions are
|
||||
matched using 'fnmatch(3)' with the FNM_PATHNAME
|
||||
flag set by default. This means that '/'
|
||||
characters must be matched explicitely. You can
|
||||
characters must be matched explicitly. You can
|
||||
set 'skippedPathsFnmPathname' to 0 to disable the
|
||||
use of FNM_PATHNAME (meaning that '/*/dir3' will
|
||||
match '/dir1/dir2/dir3'). The default value
|
||||
@@ -8487,7 +8487,7 @@ for i in range(nres):
|
||||
media to remind you that it is a bad idea to have
|
||||
Recoll work on these (esp. with the monitor:
|
||||
media gets indexed on mount, all data gets erased
|
||||
on unmount). Explicitely adding '/media/xxx' to
|
||||
on unmount). Explicitly adding '/media/xxx' to
|
||||
the 'topdirs' variable will override this.</p>
|
||||
</dd>
|
||||
<dt><a name=
|
||||
@@ -9046,6 +9046,15 @@ for i in range(nres):
|
||||
offsets for small files. The default is 5 MB.</p>
|
||||
</dd>
|
||||
<dt><a name=
|
||||
"RCL.INSTALL.CONFIG.RECOLLCONF.MBOXMAXMSGMBS" id=
|
||||
"RCL.INSTALL.CONFIG.RECOLLCONF.MBOXMAXMSGMBS"></a><span class="term"><code class="varname">mboxmaxmsgmbs</code></span></dt>
|
||||
<dd>
|
||||
<p>Maximum mbox member message size in megabytes.
|
||||
Size over which we assume that the mbox format is
|
||||
bad or we misinterpreted it, at which point we
|
||||
just stop processing the file.</p>
|
||||
</dd>
|
||||
<dt><a name=
|
||||
"RCL.INSTALL.CONFIG.RECOLLCONF.WEBCACHEDIR" id=
|
||||
"RCL.INSTALL.CONFIG.RECOLLCONF.WEBCACHEDIR"></a><span class="term"><code class="varname">webcachedir</code></span></dt>
|
||||
<dd>
|
||||
|
||||
@@ -819,7 +819,7 @@
|
||||
|
||||
<para>Using multiple configurations implies a small
|
||||
level of command line or file manager usage. The user must
|
||||
explicitely create additional configuration directories, the GUI
|
||||
explicitly create additional configuration directories, the GUI
|
||||
will not do it. This is to avoid mistakenly creating additional
|
||||
directories when an argument is mistyped. Also, the GUI or the
|
||||
indexer must be launched with a specific option or environment to
|
||||
@@ -2629,7 +2629,7 @@ fs.inotify.max_user_watches=32768
|
||||
<para>The search will only propose replacement terms with
|
||||
spelling variations when no matching document were found. In some
|
||||
cases, both proper spellings and mispellings are present in the
|
||||
index, and it may be interesting to look for them explicitely.</para>
|
||||
index, and it may be interesting to look for them explicitly.</para>
|
||||
|
||||
<para>The term explorer tool (started from the toolbar icon or
|
||||
from the <guilabel>Term explorer</guilabel> entry of the
|
||||
@@ -3050,7 +3050,7 @@ fs.inotify.max_user_watches=32768
|
||||
history, but the amount is limited: old queries will eventually
|
||||
be forgotten. Also, important queries may be difficult to find
|
||||
among others. This is why both types of queries can also be
|
||||
explicitely saved to files, from the GUI menus:
|
||||
explicitly saved to files, from the GUI menus:
|
||||
<menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save last query / Load last query</guimenuitem>
|
||||
@@ -4381,7 +4381,7 @@ text/html [file:///Users/uncrypted-dockes/projets/bateaux/ilur/factEtCie/r
|
||||
turn off its stem expansion and have no effect on
|
||||
case-sensitivity.</para>
|
||||
|
||||
<para>You can also explicitely activate case and diacritics
|
||||
<para>You can also explicitly activate case and diacritics
|
||||
sensitivity by using modifiers with the query
|
||||
language. <literal>C</literal> will make the term case-sensitive, and
|
||||
<literal>D</literal> will make it
|
||||
@@ -6204,7 +6204,7 @@ for i in range(nres):
|
||||
<para>The normal &RCL; build procedure (see above) installs the API
|
||||
package for the default system version (python) along with the main
|
||||
code. The package for other Python versions (e.g. python3 if the
|
||||
system default is python2) must be explicitely built and
|
||||
system default is python2) must be explicitly built and
|
||||
installed.</para>
|
||||
|
||||
<para>The <filename>python/recoll/</filename> directory contains
|
||||
|
||||
Reference in New Issue
Block a user