doc
This commit is contained in:
parent
c110b94738
commit
bc83e2981e
@ -10,7 +10,7 @@
|
|||||||
<link rel="stylesheet" type="text/css" href="docbook-xsl.css">
|
<link rel="stylesheet" type="text/css" href="docbook-xsl.css">
|
||||||
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
|
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
|
||||||
<meta name="description" content=
|
<meta name="description" content=
|
||||||
"Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at the following location: GNU web site. This document introduces full text search notions and describes the installation and use of the Recoll application. This version describes Recoll 1.25.">
|
"Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at the following location: GNU web site. This document introduces full text search notions and describes the installation and use of the Recoll application. This version describes Recoll 1.26.">
|
||||||
</head>
|
</head>
|
||||||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"
|
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084"
|
||||||
alink="#0000FF">
|
alink="#0000FF">
|
||||||
@ -35,7 +35,7 @@ alink="#0000FF">
|
|||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<p class="copyright">Copyright © 2005-2019 Jean-Francois
|
<p class="copyright">Copyright © 2005-2020 Jean-Francois
|
||||||
Dockes</p>
|
Dockes</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
@ -53,7 +53,7 @@ alink="#0000FF">
|
|||||||
and describes the installation and use of the
|
and describes the installation and use of the
|
||||||
<span class="application">Recoll</span> application.
|
<span class="application">Recoll</span> application.
|
||||||
This version describes <span class=
|
This version describes <span class=
|
||||||
"application">Recoll</span> 1.25.</p>
|
"application">Recoll</span> 1.26.</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -92,9 +92,9 @@ alink="#0000FF">
|
|||||||
"#RCL.INDEXING.INTRODUCTION.CONFIG">Configurations,
|
"#RCL.INDEXING.INTRODUCTION.CONFIG">Configurations,
|
||||||
multiple indexes</a></span></dt>
|
multiple indexes</a></span></dt>
|
||||||
<dt><span class="sect2">2.1.3. <a href=
|
<dt><span class="sect2">2.1.3. <a href=
|
||||||
"#idm233">Document types</a></span></dt>
|
"#idm235">Document types</a></span></dt>
|
||||||
<dt><span class="sect2">2.1.4. <a href=
|
<dt><span class="sect2">2.1.4. <a href=
|
||||||
"#idm274">Indexing failures</a></span></dt>
|
"#idm276">Indexing failures</a></span></dt>
|
||||||
<dt><span class="sect2">2.1.5. <a href=
|
<dt><span class="sect2">2.1.5. <a href=
|
||||||
"#idm286">Recovery</a></span></dt>
|
"#idm286">Recovery</a></span></dt>
|
||||||
</dl>
|
</dl>
|
||||||
@ -190,17 +190,18 @@ alink="#0000FF">
|
|||||||
"#RCL.SEARCH.GUI.SIMPLE">Simple
|
"#RCL.SEARCH.GUI.SIMPLE">Simple
|
||||||
search</a></span></dt>
|
search</a></span></dt>
|
||||||
<dt><span class="sect2">3.2.2. <a href=
|
<dt><span class="sect2">3.2.2. <a href=
|
||||||
"#RCL.SEARCH.GUI.RESLIST">The default result
|
"#RCL.SEARCH.GUI.RESLIST">The result
|
||||||
list</a></span></dt>
|
list</a></span></dt>
|
||||||
<dt><span class="sect2">3.2.3. <a href=
|
<dt><span class="sect2">3.2.3. <a href=
|
||||||
"#RCL.SEARCH.GUI.RESTABLE">The result
|
"#RCL.SEARCH.GUI.RESTABLE">The result
|
||||||
table</a></span></dt>
|
table</a></span></dt>
|
||||||
<dt><span class="sect2">3.2.4. <a href=
|
<dt><span class="sect2">3.2.4. <a href=
|
||||||
"#RCL.SEARCH.GUI.RUNSCRIPT">Running arbitrary
|
"#RCL.SEARCH.GUI.RUNSCRIPT"><span class=
|
||||||
commands on result files (1.20 and
|
"application">Unix</span>-like systems: running
|
||||||
later)</a></span></dt>
|
arbitrary commands on result files</a></span></dt>
|
||||||
<dt><span class="sect2">3.2.5. <a href=
|
<dt><span class="sect2">3.2.5. <a href=
|
||||||
"#RCL.SEARCH.GUI.THUMBNAILS">Displaying
|
"#RCL.SEARCH.GUI.THUMBNAILS"><span class=
|
||||||
|
"application">Unix</span>-like systems: displaying
|
||||||
thumbnails</a></span></dt>
|
thumbnails</a></span></dt>
|
||||||
<dt><span class="sect2">3.2.6. <a href=
|
<dt><span class="sect2">3.2.6. <a href=
|
||||||
"#RCL.SEARCH.GUI.PREVIEW">The preview
|
"#RCL.SEARCH.GUI.PREVIEW">The preview
|
||||||
@ -429,7 +430,7 @@ alink="#0000FF">
|
|||||||
<p>This document introduces full text search notions and
|
<p>This document introduces full text search notions and
|
||||||
describes the installation and use of the <span class=
|
describes the installation and use of the <span class=
|
||||||
"application">Recoll</span> application. It is updated for
|
"application">Recoll</span> application. It is updated for
|
||||||
<span class="application">Recoll</span> 1.25.</p>
|
<span class="application">Recoll</span> 1.26.</p>
|
||||||
<p><span class="application">Recoll</span> was for a long
|
<p><span class="application">Recoll</span> was for a long
|
||||||
time dedicated to Unix-like systems. It was only lately
|
time dedicated to Unix-like systems. It was only lately
|
||||||
(2015) ported to <span class="application">MS-Windows</span>.
|
(2015) ported to <span class="application">MS-Windows</span>.
|
||||||
@ -440,10 +441,13 @@ alink="#0000FF">
|
|||||||
updated. Until this happens, on <span class=
|
updated. Until this happens, on <span class=
|
||||||
"application">Windows</span>, most references to shared files
|
"application">Windows</span>, most references to shared files
|
||||||
can be translated by looking under the Recoll installation
|
can be translated by looking under the Recoll installation
|
||||||
directory (esp. the <code class="filename">Share</code>
|
directory (Typically <code class="filename">C:/Program Files
|
||||||
subdirectory). The user configuration is stored by default
|
(x86)/Recoll</code>, esp. anything referenced in <code class=
|
||||||
under <code class="filename">AppData/Local/Recoll</code>
|
"filename">/usr/share</code> in this document will be found
|
||||||
inside the user directory, along with the index itself.</p>
|
int the <code class="filename">Share</code> subdirectory).
|
||||||
|
The user configuration is stored by default under
|
||||||
|
<code class="filename">AppData/Local/Recoll</code> inside the
|
||||||
|
user directory, along with the index itself.</p>
|
||||||
<div class="sect1">
|
<div class="sect1">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
@ -652,10 +656,12 @@ alink="#0000FF">
|
|||||||
files in this directory may be overridden by values set
|
files in this directory may be overridden by values set
|
||||||
inside your personal configuration. With the default
|
inside your personal configuration. With the default
|
||||||
configuration, <span class="application">Recoll</span> will
|
configuration, <span class="application">Recoll</span> will
|
||||||
index your home directory with generic parameters. The
|
index your home directory with generic parameters. Most
|
||||||
configuration can be customized either by editing the text
|
common parameters can be set by using configuration menus
|
||||||
files or by using configuration menus in the <span class=
|
in the <span class="command"><strong>recoll</strong></span>
|
||||||
"command"><strong>recoll</strong></span> GUI.</p>
|
GUI. Some less common parameters can only be set by editing
|
||||||
|
the text files (the new values will be preserved by the
|
||||||
|
GUI).</p>
|
||||||
<p>The <a class="link" href="#RCL.INDEXING.PERIODIC.EXEC"
|
<p>The <a class="link" href="#RCL.INDEXING.PERIODIC.EXEC"
|
||||||
title="Running the indexer">indexing process</a> is started
|
title="Running the indexer">indexing process</a> is started
|
||||||
automatically (after asking permission), the first time you
|
automatically (after asking permission), the first time you
|
||||||
@ -744,11 +750,9 @@ alink="#0000FF">
|
|||||||
<p><span class=
|
<p><span class=
|
||||||
"command"><strong>recollindex</strong></span> skips files
|
"command"><strong>recollindex</strong></span> skips files
|
||||||
which caused an error during a previous pass. This is a
|
which caused an error during a previous pass. This is a
|
||||||
performance optimization, and a new behaviour in version
|
performance optimization, and the command line option
|
||||||
1.21 (failed files were always retried by previous
|
<code class="option">-k</code> can be set to retry failed
|
||||||
versions). The command line option <code class=
|
files, for example after updating an input handler.</p>
|
||||||
"option">-k</code> can be set to retry failed files, for
|
|
||||||
example after updating an input handler.</p>
|
|
||||||
<p>The following sections give an overview of different
|
<p>The following sections give an overview of different
|
||||||
aspects of the indexing processes and configuration, with
|
aspects of the indexing processes and configuration, with
|
||||||
links to detailed sections.</p>
|
links to detailed sections.</p>
|
||||||
@ -791,9 +795,10 @@ alink="#0000FF">
|
|||||||
into your <span class=
|
into your <span class=
|
||||||
"command"><strong>cron</strong></span> file. On
|
"command"><strong>cron</strong></span> file. On
|
||||||
<span class="application">Windows</span>, this is
|
<span class="application">Windows</span>, this is
|
||||||
the only mode available, and the indexer is usually
|
the only mode available, and the Windows Task
|
||||||
started from the GUI (but there is nothing to
|
Scheduler can be used to run indexing. In both
|
||||||
prevent starting it from a command script).</p>
|
cases, the GUI includes an easy interface to the
|
||||||
|
system batch scheduler.</p>
|
||||||
</li>
|
</li>
|
||||||
<li class="listitem">
|
<li class="listitem">
|
||||||
<p><b><a class="link" href="#RCL.INDEXING.MONITOR"
|
<p><b><a class="link" href="#RCL.INDEXING.MONITOR"
|
||||||
@ -816,8 +821,8 @@ alink="#0000FF">
|
|||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
<div>
|
<div>
|
||||||
<h4 class="title"><a name="idm188" id=
|
<h4 class="title"><a name="idm190" id=
|
||||||
"idm188"></a><span class=
|
"idm190"></a><span class=
|
||||||
"application">Unix</span>-like systems: choosing
|
"application">Unix</span>-like systems: choosing
|
||||||
an indexing mode</h4>
|
an indexing mode</h4>
|
||||||
</div>
|
</div>
|
||||||
@ -837,7 +842,7 @@ alink="#0000FF">
|
|||||||
configured from the <span class=
|
configured from the <span class=
|
||||||
"command"><strong>recoll</strong></span> GUI:
|
"command"><strong>recoll</strong></span> GUI:
|
||||||
<span class="guimenu">Preferences</span> → <span class=
|
<span class="guimenu">Preferences</span> → <span class=
|
||||||
"guimenuitem">Indexing schedule</span></p>
|
"guimenuitem">Indexing schedule</span> dialog.</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
@ -935,8 +940,8 @@ alink="#0000FF">
|
|||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
<div>
|
<div>
|
||||||
<h3 class="title"><a name="idm233" id=
|
<h3 class="title"><a name="idm235" id=
|
||||||
"idm233"></a>2.1.3. Document types</h3>
|
"idm235"></a>2.1.3. Document types</h3>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -1033,8 +1038,8 @@ alink="#0000FF">
|
|||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
<div>
|
<div>
|
||||||
<h3 class="title"><a name="idm274" id=
|
<h3 class="title"><a name="idm276" id=
|
||||||
"idm274"></a>2.1.4. Indexing failures</h3>
|
"idm276"></a>2.1.4. Indexing failures</h3>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -1042,20 +1047,15 @@ alink="#0000FF">
|
|||||||
reasons: a helper program may be missing, the document
|
reasons: a helper program may be missing, the document
|
||||||
may be corrupt, we may fail to uncompress a file because
|
may be corrupt, we may fail to uncompress a file because
|
||||||
no file system space is available, etc.</p>
|
no file system space is available, etc.</p>
|
||||||
<p><span class="application">Recoll</span> versions prior
|
<p>The <span class="application">Recoll</span> indexer in
|
||||||
to 1.21 always retried to index files which had
|
|
||||||
previously caused an error. This guaranteed that anything
|
|
||||||
that may have become indexable (for example because a
|
|
||||||
helper had been installed) would be indexed. However this
|
|
||||||
was bad for performance because some indexing failures
|
|
||||||
may be quite costly (for example failing to uncompress a
|
|
||||||
big file because of insufficient disk space).</p>
|
|
||||||
<p>The indexer in <span class="application">Recoll</span>
|
|
||||||
versions 1.21 and later does not retry failed files by
|
versions 1.21 and later does not retry failed files by
|
||||||
default. Retrying will only occur if an explicit option
|
default, because some indexing failures can be quite
|
||||||
(<code class="option">-k</code>) is set on the
|
costly (for example failing to uncompress a big file
|
||||||
<span class="command"><strong>recollindex</strong></span>
|
because of insufficient disk space). Retrying will only
|
||||||
command line, or if a script executed when <span class=
|
occur if an explicit option (<code class=
|
||||||
|
"option">-k</code>) is set on the <span class=
|
||||||
|
"command"><strong>recollindex</strong></span> command
|
||||||
|
line, or if a script executed when <span class=
|
||||||
"command"><strong>recollindex</strong></span> starts up
|
"command"><strong>recollindex</strong></span> starts up
|
||||||
says so. The script is defined by a configuration
|
says so. The script is defined by a configuration
|
||||||
variable (<code class=
|
variable (<code class=
|
||||||
@ -1166,8 +1166,8 @@ alink="#0000FF">
|
|||||||
files where only the tags would be indexed).</p>
|
files where only the tags would be indexed).</p>
|
||||||
<p>Of course, images, sound and video do not increase the
|
<p>Of course, images, sound and video do not increase the
|
||||||
index size, which means that in most cases, the space used
|
index size, which means that in most cases, the space used
|
||||||
by the index will be negligible against the total amount of
|
by the index will be negligible compared to the total
|
||||||
data on the computer.</p>
|
amount of data on the computer.</p>
|
||||||
<p>The index data directory (<code class=
|
<p>The index data directory (<code class=
|
||||||
"filename">xapiandb</code>) only contains data that can be
|
"filename">xapiandb</code>) only contains data that can be
|
||||||
completely rebuilt by an index run (as long as the original
|
completely rebuilt by an index run (as long as the original
|
||||||
@ -1295,13 +1295,14 @@ alink="#0000FF">
|
|||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<p>Variables set inside the <a class="link" href=
|
<p>Variables stored inside the <a class="link" href=
|
||||||
"#RCL.INSTALL.CONFIG" title=
|
"#RCL.INSTALL.CONFIG" title=
|
||||||
"5.4. Configuration overview"><span class=
|
"5.4. Configuration overview"><span class=
|
||||||
"application">Recoll</span> configuration files</a> control
|
"application">Recoll</span> configuration files</a> control
|
||||||
which areas of the file system are indexed, and how files
|
which areas of the file system are indexed, and how files
|
||||||
are processed. These variables can be set either by editing
|
are processed. The values can be set by editing the text
|
||||||
the text files or by using the <a class="link" href=
|
files. Most of the more commonly used ones can also be
|
||||||
|
adjusted by using the <a class="link" href=
|
||||||
"#RCL.INDEXING.CONFIG.GUI" title=
|
"#RCL.INDEXING.CONFIG.GUI" title=
|
||||||
"2.3.4. The index configuration GUI">dialogs in the
|
"2.3.4. The index configuration GUI">dialogs in the
|
||||||
<span class="command"><strong>recoll</strong></span>
|
<span class="command"><strong>recoll</strong></span>
|
||||||
@ -1322,7 +1323,7 @@ alink="#0000FF">
|
|||||||
"https://www.lesbonscomptes.com/recoll/manpages/recoll.conf.5.html"
|
"https://www.lesbonscomptes.com/recoll/manpages/recoll.conf.5.html"
|
||||||
target="_top"><span class="citerefentry"><span class=
|
target="_top"><span class="citerefentry"><span class=
|
||||||
"refentrytitle">recoll.conf</span>(5)</span></a> manual
|
"refentrytitle">recoll.conf</span>(5)</span></a> manual
|
||||||
page.Both documents are automatically generated from the
|
page. Both documents are automatically generated from the
|
||||||
comments inside the configuration file.</p>
|
comments inside the configuration file.</p>
|
||||||
<p>The most immediately useful variable is probably
|
<p>The most immediately useful variable is probably
|
||||||
<a class="link" href=
|
<a class="link" href=
|
||||||
@ -1335,12 +1336,13 @@ alink="#0000FF">
|
|||||||
"#RCL.INSTALL.EXTERNAL" title=
|
"#RCL.INSTALL.EXTERNAL" title=
|
||||||
"5.2. Supporting packages">external packages
|
"5.2. Supporting packages">external packages
|
||||||
section</a>.</p>
|
section</a>.</p>
|
||||||
<p>As of Recoll 1.18 there are two incompatible types of
|
<p>There are two incompatible types of Recoll indexes,
|
||||||
Recoll indexes, depending on the treatment of character
|
depending on the treatment of character case and
|
||||||
case and diacritics. A <a class="link" href=
|
diacritics. A <a class="link" href=
|
||||||
"#RCL.INDEXING.CONFIG.SENS" title=
|
"#RCL.INDEXING.CONFIG.SENS" title=
|
||||||
"2.3.2. Index case and diacritics sensitivity">further
|
"2.3.2. Index case and diacritics sensitivity">further
|
||||||
section</a> describes the two types in more detail.</p>
|
section</a> describes the two types in more detail. The
|
||||||
|
default type is appropriate in most cases.</p>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
@ -1721,12 +1723,13 @@ recoll -c <em class=
|
|||||||
<li class="listitem">
|
<li class="listitem">
|
||||||
<p>By indexing the volume in the main, fixed, index,
|
<p>By indexing the volume in the main, fixed, index,
|
||||||
and ensuring that the volume data is not purged if
|
and ensuring that the volume data is not purged if
|
||||||
the indexing runs while the volume is mounted.
|
the indexing runs while the volume is mounted. (since
|
||||||
(<span class="application">Recoll</span> 1.25.2).</p>
|
<span class="application">Recoll</span> 1.25.2).</p>
|
||||||
</li>
|
</li>
|
||||||
<li class="listitem">
|
<li class="listitem">
|
||||||
<p>By storing a volume index on the volume itself
|
<p>By storing a volume index on the volume itself
|
||||||
(<span class="application">Recoll</span> 1.24).</p>
|
(since <span class="application">Recoll</span>
|
||||||
|
1.24).</p>
|
||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
@ -2337,23 +2340,23 @@ metadatacmds = ; <em class=
|
|||||||
index when it starts, it will automatically start
|
index when it starts, it will automatically start
|
||||||
indexing (except if canceled).</p>
|
indexing (except if canceled).</p>
|
||||||
<p>The GUI <span class="guimenu">File</span> menu has
|
<p>The GUI <span class="guimenu">File</span> menu has
|
||||||
entries to start or stop the current indexing
|
entries to start or stop the current indexing operation.
|
||||||
operation.</p>
|
When indexing is not currently running, you have a choice
|
||||||
<p>When no indexing is running, you have a choice of
|
of updating the index or rebuilding it (the first choice
|
||||||
updating the index or rebuilding it (the first choice
|
|
||||||
only processes changed files, the second one zeroes the
|
only processes changed files, the second one zeroes the
|
||||||
index before starting so that all files are
|
index before starting so that all files are
|
||||||
processed).</p>
|
processed).</p>
|
||||||
|
<p>On Linux and Windows, the GUI can be used to manage
|
||||||
|
the indexing operation. Stopping the indexer can be done
|
||||||
|
from the <span class=
|
||||||
|
"command"><strong>recoll</strong></span> GUI <span class=
|
||||||
|
"guimenu">File</span> → <span class="guimenuitem">Stop
|
||||||
|
Indexing</span> menu entry.</p>
|
||||||
<p>On Linux, the <span class=
|
<p>On Linux, the <span class=
|
||||||
"command"><strong>recollindex</strong></span> indexing
|
"command"><strong>recollindex</strong></span> indexing
|
||||||
process can be interrupted by sending an interrupt
|
process can be interrupted by sending an interrupt
|
||||||
(<span class="keysym">Ctrl-C</span>, SIGINT) or terminate
|
(<span class="keysym">Ctrl-C</span>, SIGINT) or terminate
|
||||||
(SIGTERM) signal.</p>
|
(SIGTERM) signal.</p>
|
||||||
<p>On Linux and Windows, the GUI can used to manage the
|
|
||||||
indexing operation. Stopping the indexer can be done from
|
|
||||||
the <span class="command"><strong>recoll</strong></span>
|
|
||||||
GUI <span class="guimenu">File</span> → <span class=
|
|
||||||
"guimenuitem">Stop Indexing</span> menu entry.</p>
|
|
||||||
<p>When stopped, some time may elapse before <span class=
|
<p>When stopped, some time may elapse before <span class=
|
||||||
"command"><strong>recollindex</strong></span> exits,
|
"command"><strong>recollindex</strong></span> exits,
|
||||||
because it needs to properly flush and close the
|
because it needs to properly flush and close the
|
||||||
@ -2368,6 +2371,18 @@ metadatacmds = ; <em class=
|
|||||||
full file tree will be traversed, but files that were
|
full file tree will be traversed, but files that were
|
||||||
indexed up to the interruption and for which the index is
|
indexed up to the interruption and for which the index is
|
||||||
still up to date will not need to be reindexed).</p>
|
still up to date will not need to be reindexed).</p>
|
||||||
|
</div>
|
||||||
|
<div class="simplesect">
|
||||||
|
<div class="titlepage">
|
||||||
|
<div>
|
||||||
|
<div>
|
||||||
|
<h3 class="title"><a name=
|
||||||
|
"RCL.INDEXING.PERIODIC.CMDLINE" id=
|
||||||
|
"RCL.INDEXING.PERIODIC.CMDLINE"></a>recollindex
|
||||||
|
command line</h3>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
<p><span class=
|
<p><span class=
|
||||||
"command"><strong>recollindex</strong></span> has many
|
"command"><strong>recollindex</strong></span> has many
|
||||||
options which are listed in its <a class="ulink" href=
|
options which are listed in its <a class="ulink" href=
|
||||||
@ -2708,7 +2723,7 @@ fs.inotify.max_user_watches=32768
|
|||||||
is based on the <span class="application">Qt</span>
|
is based on the <span class="application">Qt</span>
|
||||||
library.</p>
|
library.</p>
|
||||||
<p><span class="command"><strong>recoll</strong></span> has
|
<p><span class="command"><strong>recoll</strong></span> has
|
||||||
two search modes:</p>
|
two search interfaces:</p>
|
||||||
<div class="itemizedlist">
|
<div class="itemizedlist">
|
||||||
<ul class="itemizedlist" style="list-style-type: disc;">
|
<ul class="itemizedlist" style="list-style-type: disc;">
|
||||||
<li class="listitem">
|
<li class="listitem">
|
||||||
@ -2804,40 +2819,6 @@ fs.inotify.max_user_watches=32768
|
|||||||
features are described in <a class="link" href=
|
features are described in <a class="link" href=
|
||||||
"#RCL.SEARCH.LANG" title="3.5. The query language">a
|
"#RCL.SEARCH.LANG" title="3.5. The query language">a
|
||||||
separate section</a>.</p>
|
separate section</a>.</p>
|
||||||
<p>The <span class="guilabel">File name</span> search
|
|
||||||
mode will specifically look for file names. The point of
|
|
||||||
having a separate file name search is that wild card
|
|
||||||
expansion can be performed more efficiently on a small
|
|
||||||
subset of the index (allowing wild cards on the left of
|
|
||||||
terms without excessive cost). Things to know:</p>
|
|
||||||
<div class="itemizedlist">
|
|
||||||
<ul class="itemizedlist" style=
|
|
||||||
"list-style-type: disc;">
|
|
||||||
<li class="listitem">
|
|
||||||
<p>White space in the entry should match white
|
|
||||||
space in the file name, and is not treated
|
|
||||||
specially.</p>
|
|
||||||
</li>
|
|
||||||
<li class="listitem">
|
|
||||||
<p>The search is insensitive to character case and
|
|
||||||
accents, independently of the type of index.</p>
|
|
||||||
</li>
|
|
||||||
<li class="listitem">
|
|
||||||
<p>An entry without any wild card character and not
|
|
||||||
capitalized will be prepended and appended with '*'
|
|
||||||
(ie: <em class="replaceable"><code>etc</code></em>
|
|
||||||
-> <em class=
|
|
||||||
"replaceable"><code>*etc*</code></em>, but
|
|
||||||
<em class="replaceable"><code>Etc</code></em> ->
|
|
||||||
<em class="replaceable"><code>etc</code></em>).</p>
|
|
||||||
</li>
|
|
||||||
<li class="listitem">
|
|
||||||
<p>If you have a big index (many files),
|
|
||||||
excessively generic fragments may result in
|
|
||||||
inefficient searches.</p>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</div>
|
|
||||||
<p>When using a stripped index (the default), character
|
<p>When using a stripped index (the default), character
|
||||||
case has no influence on search, except that you can
|
case has no influence on search, except that you can
|
||||||
disable stem expansion for any term by capitalizing it.
|
disable stem expansion for any term by capitalizing it.
|
||||||
@ -2883,6 +2864,40 @@ fs.inotify.max_user_watches=32768
|
|||||||
"guimenu">Tools</span> → <span class=
|
"guimenu">Tools</span> → <span class=
|
||||||
"guimenuitem">Advanced search</span></a> dialog for more
|
"guimenuitem">Advanced search</span></a> dialog for more
|
||||||
complex searches.</p>
|
complex searches.</p>
|
||||||
|
<p>The <span class="guilabel">File name</span> search
|
||||||
|
mode will specifically look for file names. The point of
|
||||||
|
having a separate file name search is that wild card
|
||||||
|
expansion can be performed more efficiently on a small
|
||||||
|
subset of the index (allowing wild cards on the left of
|
||||||
|
terms without excessive cost). Things to know:</p>
|
||||||
|
<div class="itemizedlist">
|
||||||
|
<ul class="itemizedlist" style=
|
||||||
|
"list-style-type: disc;">
|
||||||
|
<li class="listitem">
|
||||||
|
<p>White space in the entry should match white
|
||||||
|
space in the file name, and is not treated
|
||||||
|
specially.</p>
|
||||||
|
</li>
|
||||||
|
<li class="listitem">
|
||||||
|
<p>The search is insensitive to character case and
|
||||||
|
accents, independently of the type of index.</p>
|
||||||
|
</li>
|
||||||
|
<li class="listitem">
|
||||||
|
<p>An entry without any wild card character and not
|
||||||
|
capitalized will be prepended and appended with '*'
|
||||||
|
(ie: <em class="replaceable"><code>etc</code></em>
|
||||||
|
-> <em class=
|
||||||
|
"replaceable"><code>*etc*</code></em>, but
|
||||||
|
<em class="replaceable"><code>Etc</code></em> ->
|
||||||
|
<em class="replaceable"><code>etc</code></em>).</p>
|
||||||
|
</li>
|
||||||
|
<li class="listitem">
|
||||||
|
<p>If you have a big index (many files),
|
||||||
|
excessively generic fragments may result in
|
||||||
|
inefficient searches.</p>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
@ -2890,27 +2905,27 @@ fs.inotify.max_user_watches=32768
|
|||||||
<div>
|
<div>
|
||||||
<h3 class="title"><a name="RCL.SEARCH.GUI.RESLIST"
|
<h3 class="title"><a name="RCL.SEARCH.GUI.RESLIST"
|
||||||
id="RCL.SEARCH.GUI.RESLIST"></a>3.2.2. The
|
id="RCL.SEARCH.GUI.RESLIST"></a>3.2.2. The
|
||||||
default result list</h3>
|
result list</h3>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<p>After starting a search, a list of results will
|
<p>After starting a search, a list of results will
|
||||||
instantly be displayed in the main list window.</p>
|
instantly be displayed in the main window.</p>
|
||||||
<p>By default, the document list is presented in order of
|
<p>By default, the document list is presented in order of
|
||||||
relevance (how well the system estimates that the
|
relevance (how well the system estimates that the
|
||||||
document matches the query). You can sort the result by
|
document matches the query). You can sort the result by
|
||||||
ascending or descending date by using the vertical arrows
|
ascending or descending date by using the vertical arrows
|
||||||
in the toolbar.</p>
|
in the toolbar.</p>
|
||||||
<p>Clicking on the <code class="literal">Preview</code>
|
<p>Clicking the <code class="literal">Preview</code> link
|
||||||
link for an entry will open an internal preview window
|
for an entry will open an internal preview window for the
|
||||||
for the document. Further <code class=
|
document. Further <code class="literal">Preview</code>
|
||||||
"literal">Preview</code> clicks for the same search will
|
clicks for the same search will open tabs in the existing
|
||||||
open tabs in the existing preview window. You can use
|
preview window. You can use <span class=
|
||||||
<span class="keycap"><strong>Shift</strong></span>+Click
|
"keycap"><strong>Shift</strong></span>+Click to force the
|
||||||
to force the creation of another preview window, which
|
creation of another preview window, which may be useful
|
||||||
may be useful to view the documents side by side. (You
|
to view the documents side by side. (You can also browse
|
||||||
can also browse successive results in a single preview
|
successive results in a single preview window by typing
|
||||||
window by typing <span class=
|
<span class=
|
||||||
"keycap"><strong>Shift</strong></span>+<span class=
|
"keycap"><strong>Shift</strong></span>+<span class=
|
||||||
"keycap"><strong>ArrowUp/Down</strong></span> in the
|
"keycap"><strong>ArrowUp/Down</strong></span> in the
|
||||||
window).</p>
|
window).</p>
|
||||||
@ -2918,39 +2933,23 @@ fs.inotify.max_user_watches=32768
|
|||||||
will start an external viewer for the document. By
|
will start an external viewer for the document. By
|
||||||
default, <span class="application">Recoll</span> lets the
|
default, <span class="application">Recoll</span> lets the
|
||||||
desktop choose the appropriate application for most
|
desktop choose the appropriate application for most
|
||||||
document types (there is a short list of exceptions, see
|
document types. This currently not customisable on
|
||||||
further). If you prefer to completely customize the
|
<span class="application">Windows</span>. See <a class=
|
||||||
choice of applications, you can uncheck the <span class=
|
"link" href="#RCL.SEARCH.GUI.RESLIST.APPLICATIONS" title=
|
||||||
"guilabel">Use desktop preferences</span> option in the
|
"Unix-like systems: customising the applications">further</a>
|
||||||
GUI preferences dialog, and click the <span class=
|
for customizing the applications on <span class=
|
||||||
"guilabel">Choose editor applications</span> button to
|
"application">Unix</span>-like systems.</p>
|
||||||
adjust the predefined <span class=
|
<p>You can click on the <code class="literal">Query
|
||||||
"application">Recoll</span> choices. The tool accepts
|
details</code> link at the top of the results page to see
|
||||||
multiple selections of MIME types (e.g. to set up the
|
the query actually performed, after stem expansion and
|
||||||
editor for the dozens of office file types).</p>
|
other processing.</p>
|
||||||
<p>Even when <span class="guilabel">Use desktop
|
<p>Double-clicking on any word inside the result list or
|
||||||
preferences</span> is checked, there is a small list of
|
a preview window will insert it into the simple search
|
||||||
exceptions, for MIME types where the <span class=
|
text.</p>
|
||||||
"application">Recoll</span> choice should override the
|
<p>The result list is divided into pages (the size of
|
||||||
desktop one. These are applications which are well
|
which you can change in the preferences). Use the arrow
|
||||||
integrated with <span class="application">Recoll</span>,
|
buttons in the toolbar or the links at the bottom of the
|
||||||
especially <span class="application">evince</span> for
|
page to browse the results.</p>
|
||||||
viewing PDF and Postscript files because of its support
|
|
||||||
for opening the document at a specific page and passing a
|
|
||||||
search string as an argument. Of course, you can edit the
|
|
||||||
list (in the GUI preferences) if you would prefer to lose
|
|
||||||
the functionality and use the standard desktop tool.</p>
|
|
||||||
<p>You may also change the choice of applications by
|
|
||||||
editing the <a class="link" href=
|
|
||||||
"#RCL.INSTALL.CONFIG.MIMEVIEW" title=
|
|
||||||
"5.4.6. The mimeview file"><code class=
|
|
||||||
"filename">mimeview</code></a> configuration file if you
|
|
||||||
find this more convenient.</p>
|
|
||||||
<p>Each result entry also has a right-click menu with an
|
|
||||||
<span class="guilabel">Open With</span> entry. This lets
|
|
||||||
you choose an application from the list of those which
|
|
||||||
registered with the desktop for the document MIME
|
|
||||||
type.</p>
|
|
||||||
<p>The <code class="literal">Preview</code> and
|
<p>The <code class="literal">Preview</code> and
|
||||||
<code class="literal">Open</code> edit links may not be
|
<code class="literal">Open</code> edit links may not be
|
||||||
present for all entries, meaning that <span class=
|
present for all entries, meaning that <span class=
|
||||||
@ -2970,17 +2969,66 @@ fs.inotify.max_user_watches=32768
|
|||||||
configurable by using the preference dialog to <a class=
|
configurable by using the preference dialog to <a class=
|
||||||
"link" href="#RCL.SEARCH.GUI.CUSTOM.RESLIST" title=
|
"link" href="#RCL.SEARCH.GUI.CUSTOM.RESLIST" title=
|
||||||
"The result list format">edit an HTML fragment</a>.</p>
|
"The result list format">edit an HTML fragment</a>.</p>
|
||||||
<p>You can click on the <code class="literal">Query
|
<div class="simplesect">
|
||||||
details</code> link at the top of the results page to see
|
<div class="titlepage">
|
||||||
the query actually performed, after stem expansion and
|
<div>
|
||||||
other processing.</p>
|
<div>
|
||||||
<p>Double-clicking on any word inside the result list or
|
<h4 class="title"><a name=
|
||||||
a preview window will insert it into the simple search
|
"RCL.SEARCH.GUI.RESLIST.APPLICATIONS" id=
|
||||||
text.</p>
|
"RCL.SEARCH.GUI.RESLIST.APPLICATIONS"></a><span class="application">Unix</span>-like
|
||||||
<p>The result list is divided into pages (the size of
|
systems: customising the applications</h4>
|
||||||
which you can change in the preferences). Use the arrow
|
</div>
|
||||||
buttons in the toolbar or the links at the bottom of the
|
</div>
|
||||||
page to browse the results.</p>
|
</div>
|
||||||
|
<p>By default <span class="application">Recoll</span>
|
||||||
|
lets the desktop choose what application should be used
|
||||||
|
to open a given document, with exceptions.</p>
|
||||||
|
<p>The details of this behaviour can be customized with
|
||||||
|
the <span class="guimenu">Preferences</span> →
|
||||||
|
<span class="guimenuitem">GUI configuration</span> →
|
||||||
|
<span class="guimenuitem">User interface</span> →
|
||||||
|
<span class="guimenuitem">Choose editor
|
||||||
|
applications</span> dialog or by editing the <a class=
|
||||||
|
"link" href="#RCL.INSTALL.CONFIG.MIMEVIEW" title=
|
||||||
|
"5.4.6. The mimeview file"><code class=
|
||||||
|
"filename">mimeview</code> configuration file.</a></p>
|
||||||
|
<p>When <span class="guilabel">Use desktop
|
||||||
|
preferences</span>, at the top of the dialog, is
|
||||||
|
checked, there is a small list of exceptions, for MIME
|
||||||
|
types where the <span class="application">Recoll</span>
|
||||||
|
choice should override the desktop one. These are
|
||||||
|
applications which are well integrated with
|
||||||
|
<span class="application">Recoll</span>, for example,
|
||||||
|
on Linux, <span class="application">evince</span> for
|
||||||
|
viewing PDF and Postscript files because of its support
|
||||||
|
for opening the document at a specific page and passing
|
||||||
|
a search string as an argument. You can add or remove
|
||||||
|
document types to the exceptions by using the
|
||||||
|
dialog.</p>
|
||||||
|
<p>If you prefer to completely customize the choice of
|
||||||
|
applications, you can uncheck <span class=
|
||||||
|
"guilabel">Use desktop preferences</span>, in which
|
||||||
|
case the <span class="application">Recoll</span>
|
||||||
|
predefined applications will be used, and can be
|
||||||
|
changed for each document type. This is probably not
|
||||||
|
the most convenient approach in most cases.</p>
|
||||||
|
<p>In all cases, the applications choice dialog accepts
|
||||||
|
multiple selections of MIME types in the top section,
|
||||||
|
and lets you define how they are processed in the
|
||||||
|
bottom one.</p>
|
||||||
|
<p>You may also change the choice of applications by
|
||||||
|
editing the <a class="link" href=
|
||||||
|
"#RCL.INSTALL.CONFIG.MIMEVIEW" title=
|
||||||
|
"5.4.6. The mimeview file"><code class=
|
||||||
|
"filename">mimeview</code></a> configuration file if
|
||||||
|
you find this more convenient.</p>
|
||||||
|
<p>Under <span class="application">Unix</span>-like
|
||||||
|
systems, each result list entry also has a right-click
|
||||||
|
menu with an <span class="guilabel">Open With</span>
|
||||||
|
entry. This lets you choose an application from the
|
||||||
|
list of those which registered with the desktop for the
|
||||||
|
document MIME type, on a case by case basis.</p>
|
||||||
|
</div>
|
||||||
<div class="sect3">
|
<div class="sect3">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
<div>
|
<div>
|
||||||
@ -3063,18 +3111,20 @@ fs.inotify.max_user_watches=32768
|
|||||||
<p>The <span class="guilabel">Preview</span> and
|
<p>The <span class="guilabel">Preview</span> and
|
||||||
<span class="guilabel">Open</span> entries do the same
|
<span class="guilabel">Open</span> entries do the same
|
||||||
thing as the corresponding links.</p>
|
thing as the corresponding links.</p>
|
||||||
<p><span class="guilabel">Open With</span> lets you
|
<p><span class="guilabel">Open With</span>
|
||||||
open the document with one of the applications claiming
|
(<span class="application">Unix</span>-like systems)
|
||||||
to be able to handle its MIME type (the information
|
lets you open the document with one of the applications
|
||||||
comes from the <code class="literal">.desktop</code>
|
claiming to be able to handle its MIME type (the
|
||||||
files in <code class=
|
information comes from the <code class=
|
||||||
|
"literal">.desktop</code> files in <code class=
|
||||||
"filename">/usr/share/applications</code>).</p>
|
"filename">/usr/share/applications</code>).</p>
|
||||||
<p><span class="guilabel">Run Script</span> allows
|
<p><span class="guilabel">Run Script</span>
|
||||||
starting an arbitrary command on the result file. It
|
(<span class="application">Unix</span>-like systems)
|
||||||
will only appear for results which are top-level files.
|
allows starting an arbitrary command on the result
|
||||||
See <a class="link" href="#RCL.SEARCH.GUI.RUNSCRIPT"
|
file. It will only appear for results which are
|
||||||
title=
|
top-level files. See <a class="link" href=
|
||||||
"3.2.4. Running arbitrary commands on result files (1.20 and later)">
|
"#RCL.SEARCH.GUI.RUNSCRIPT" title=
|
||||||
|
"3.2.4. Unix-like systems: running arbitrary commands on result files">
|
||||||
further</a> for a more detailed description.</p>
|
further</a> for a more detailed description.</p>
|
||||||
<p>The <span class="guilabel">Copy File Name</span> and
|
<p>The <span class="guilabel">Copy File Name</span> and
|
||||||
<span class="guilabel">Copy Url</span> copy the
|
<span class="guilabel">Copy Url</span> copy the
|
||||||
@ -3129,11 +3179,11 @@ fs.inotify.max_user_watches=32768
|
|||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<p>In <span class="application">Recoll</span> 1.15 and
|
<p>As an alternative to the result list, the results can
|
||||||
newer, the results can be displayed in spreadsheet-like
|
also be displayed in spreadsheet-like fashion. You can
|
||||||
fashion. You can switch to this presentation by clicking
|
switch to this presentation by clicking the table-like
|
||||||
the table-like icon in the toolbar (this is a toggle,
|
icon in the toolbar (this is a toggle, click again to
|
||||||
click again to restore the list).</p>
|
restore the list).</p>
|
||||||
<p>Clicking on the column headers will allow sorting by
|
<p>Clicking on the column headers will allow sorting by
|
||||||
the values in the column. You can click again to invert
|
the values in the column. You can click again to invert
|
||||||
the order, and use the header right-click menu to reset
|
the order, and use the header right-click menu to reset
|
||||||
@ -3164,9 +3214,9 @@ fs.inotify.max_user_watches=32768
|
|||||||
<div>
|
<div>
|
||||||
<h3 class="title"><a name=
|
<h3 class="title"><a name=
|
||||||
"RCL.SEARCH.GUI.RUNSCRIPT" id=
|
"RCL.SEARCH.GUI.RUNSCRIPT" id=
|
||||||
"RCL.SEARCH.GUI.RUNSCRIPT"></a>3.2.4. Running
|
"RCL.SEARCH.GUI.RUNSCRIPT"></a>3.2.4. <span class="application">Unix</span>-like
|
||||||
arbitrary commands on result files (1.20 and
|
systems: running arbitrary commands on result
|
||||||
later)</h3>
|
files</h3>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -3217,8 +3267,8 @@ fs.inotify.max_user_watches=32768
|
|||||||
<div>
|
<div>
|
||||||
<h3 class="title"><a name=
|
<h3 class="title"><a name=
|
||||||
"RCL.SEARCH.GUI.THUMBNAILS" id=
|
"RCL.SEARCH.GUI.THUMBNAILS" id=
|
||||||
"RCL.SEARCH.GUI.THUMBNAILS"></a>3.2.5. Displaying
|
"RCL.SEARCH.GUI.THUMBNAILS"></a>3.2.5. <span class="application">Unix</span>-like
|
||||||
thumbnails</h3>
|
systems: displaying thumbnails</h3>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@ -3239,10 +3289,10 @@ fs.inotify.max_user_watches=32768
|
|||||||
settings). Restarting the search should then display the
|
settings). Restarting the search should then display the
|
||||||
thumbnails.</p>
|
thumbnails.</p>
|
||||||
<p>There are also <a class="ulink" href=
|
<p>There are also <a class="ulink" href=
|
||||||
"https://www.lesbonscomptes.com/recoll/faqsandhowtos/ResultsThumbnails.wiki"
|
"https://www.lesbonscomptes.com/recoll/faqsandhowtos/ResultsThumbnails.html"
|
||||||
target="_top">some pointers about thumbnail
|
target="_top">some pointers about thumbnail
|
||||||
generation</a> on the <span class=
|
generation</a> in the <span class=
|
||||||
"application">Recoll</span> wiki.</p>
|
"application">Recoll</span> FAQ.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
@ -3269,10 +3319,8 @@ fs.inotify.max_user_watches=32768
|
|||||||
"keycap"><strong>Ctrl-W</strong></span> (<span class=
|
"keycap"><strong>Ctrl-W</strong></span> (<span class=
|
||||||
"keycap"><strong>Ctrl</strong></span> + <span class=
|
"keycap"><strong>Ctrl</strong></span> + <span class=
|
||||||
"keycap"><strong>W</strong></span>) in the window.
|
"keycap"><strong>W</strong></span>) in the window.
|
||||||
Closing the last tab for a window will also close the
|
Closing the last tab, or using the window manager button
|
||||||
window.</p>
|
in the top of the frame will also close the window.</p>
|
||||||
<p>Of course you can also close a preview window by using
|
|
||||||
the window manager button in the top of the frame.</p>
|
|
||||||
<p>You can display successive or previous documents from
|
<p>You can display successive or previous documents from
|
||||||
the result list inside a preview tab by typing
|
the result list inside a preview tab by typing
|
||||||
<span class=
|
<span class=
|
||||||
@ -3443,9 +3491,6 @@ fs.inotify.max_user_watches=32768
|
|||||||
defines the label for a button, and the Query Language
|
defines the label for a button, and the Query Language
|
||||||
fragment which will be added (as an AND filter) before
|
fragment which will be added (as an AND filter) before
|
||||||
performing the query if the button is active.</p>
|
performing the query if the button is active.</p>
|
||||||
<p>This feature is new in <span class=
|
|
||||||
"application">Recoll</span> 1.20, and will probably be
|
|
||||||
refined depending on user feedback.</p>
|
|
||||||
</div>
|
</div>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
@ -3879,11 +3924,11 @@ fs.inotify.max_user_watches=32768
|
|||||||
Duplicates hiding is controlled by an entry in the
|
Duplicates hiding is controlled by an entry in the
|
||||||
<span class="guilabel">GUI configuration</span> dialog,
|
<span class="guilabel">GUI configuration</span> dialog,
|
||||||
and is off by default.</p>
|
and is off by default.</p>
|
||||||
<p>As of release 1.19, when a result document does have
|
<p>When a result document does have undisplayed
|
||||||
undisplayed duplicates, a <code class=
|
duplicates, a <code class="literal">Dups</code> link will
|
||||||
"literal">Dups</code> link will be shown with the result
|
be shown with the result list entry. Clicking the link
|
||||||
list entry. Clicking the link will display the paths
|
will display the paths (URLs + ipaths) for the duplicate
|
||||||
(URLs + ipaths) for the duplicate entries.</p>
|
entries.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="sect2">
|
<div class="sect2">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
@ -3994,27 +4039,23 @@ fs.inotify.max_user_watches=32768
|
|||||||
"literal">reality</code> or both appear, but those
|
"literal">reality</code> or both appear, but those
|
||||||
which contain <code class="literal">virtual
|
which contain <code class="literal">virtual
|
||||||
reality</code> should appear sooner in the list.</p>
|
reality</code> should appear sooner in the list.</p>
|
||||||
<p>Phrase searches can strongly slow down a query if
|
<p>Phrase searches can slow down a query if most of the
|
||||||
most of the terms in the phrase are common. This is why
|
terms in the phrase are common. If the <code class=
|
||||||
the <code class="varname">autophrase</code> option is
|
"varname">autophrase</code> option is on, very common
|
||||||
off by default for <span class=
|
terms will be removed from the automatically
|
||||||
"application">Recoll</span> versions before 1.17. As of
|
constructed phrase. The removal threshold can be
|
||||||
version 1.17, <code class="varname">autophrase</code>
|
adjusted from the search preferences.</p>
|
||||||
is on by default, but very common terms will be removed
|
<p><b>Phrases and abbreviations. </b>Dotted
|
||||||
from the constructed phrase. The removal threshold can
|
abbreviations like <code class="literal">I.B.M.</code>
|
||||||
be adjusted from the search preferences.</p>
|
are also automatically indexed as a word without the
|
||||||
<p><b>Phrases and abbreviations. </b>As of
|
dots: <code class="literal">IBM</code>. Searching for
|
||||||
<span class="application">Recoll</span> version 1.17,
|
the word inside a phrase (ie: <code class=
|
||||||
dotted abbreviations like <code class=
|
"literal">"the IBM company"</code>) will only match the
|
||||||
"literal">I.B.M.</code> are also automatically indexed
|
dotted abrreviation if you increase the phrase slack
|
||||||
as a word without the dots: <code class=
|
(using the advanced search panel control, or the
|
||||||
"literal">IBM</code>. Searching for the word inside a
|
<code class="literal">o</code> query language
|
||||||
phrase (ie: <code class="literal">"the IBM
|
modifier). Literal occurences of the word will be
|
||||||
company"</code>) will only match the dotted
|
matched normally.</p>
|
||||||
abrreviation if you increase the phrase slack (using
|
|
||||||
the advanced search panel control, or the <code class=
|
|
||||||
"literal">o</code> query language modifier). Literal
|
|
||||||
occurences of the word will be matched normally.</p>
|
|
||||||
</div>
|
</div>
|
||||||
<div class="sect3">
|
<div class="sect3">
|
||||||
<div class="titlepage">
|
<div class="titlepage">
|
||||||
@ -4476,18 +4517,24 @@ fs.inotify.max_user_watches=32768
|
|||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<p>Newer versions of Recoll (from 1.17) normally use
|
<p>Recoll normally uses a full function HTML processor
|
||||||
WebKit HTML widgets for the result list and the
|
to display the result list and the <a class="link"
|
||||||
<a class="link" href=
|
href="#RCL.SEARCH.GUI.RESULTLIST.MENU.SNIPPETS">snippets
|
||||||
"#RCL.SEARCH.GUI.RESULTLIST.MENU.SNIPPETS">snippets
|
window</a>. Depending on the version, this may be based
|
||||||
window</a> (this may be disabled at build time). Total
|
on either Qt WebKit or Qt WebEngine. It is then
|
||||||
customisation is possible with full support for CSS and
|
possible to completely customise the result list with
|
||||||
Javascript. Conversely, there are limits to what you
|
full support for CSS and Javascript.</p>
|
||||||
can do with the older Qt QTextBrowser, but still, it is
|
<p>It is also possible to build <span class=
|
||||||
possible to decide what data each result will contain,
|
"application">Recoll</span> to use a simpler Qt
|
||||||
and how it will be displayed.</p>
|
QTextBrowser widget to display the HTML, which may be
|
||||||
<p>The result list presentation can be exhaustively
|
necessary if the ones above are not ported on the
|
||||||
customized by adjusting two elements:</p>
|
system, or to reduce the application size and
|
||||||
|
dependancies. There are limits to what you can do in
|
||||||
|
this case, but it is still possible to decide what data
|
||||||
|
each result will contain, and how it will be
|
||||||
|
displayed.</p>
|
||||||
|
<p>The result list presentation can be customized by
|
||||||
|
adjusting two elements:</p>
|
||||||
<div class="itemizedlist">
|
<div class="itemizedlist">
|
||||||
<ul class="itemizedlist" style=
|
<ul class="itemizedlist" style=
|
||||||
"list-style-type: disc;">
|
"list-style-type: disc;">
|
||||||
@ -4617,7 +4664,7 @@ fs.inotify.max_user_watches=32768
|
|||||||
(if the document is embedded, the script will be
|
(if the document is embedded, the script will be
|
||||||
started on the top-level parent). See the <a class=
|
started on the top-level parent). See the <a class=
|
||||||
"link" href="#RCL.SEARCH.GUI.RUNSCRIPT" title=
|
"link" href="#RCL.SEARCH.GUI.RUNSCRIPT" title=
|
||||||
"3.2.4. Running arbitrary commands on result files (1.20 and later)">
|
"3.2.4. Unix-like systems: running arbitrary commands on result files">
|
||||||
section about defining scripts</a>.</p>
|
section about defining scripts</a>.</p>
|
||||||
<p>In addition to the predefined values above, all
|
<p>In addition to the predefined values above, all
|
||||||
strings like <code class=
|
strings like <code class=
|
||||||
|
|||||||
@ -5,7 +5,7 @@
|
|||||||
|
|
||||||
<!ENTITY RCL "<application>Recoll</application>">
|
<!ENTITY RCL "<application>Recoll</application>">
|
||||||
<!ENTITY RCLAPPS "<ulink url='http://www.recoll.org/features.html#doctypes'>http://www.recoll.org/features.html</ulink>">
|
<!ENTITY RCLAPPS "<ulink url='http://www.recoll.org/features.html#doctypes'>http://www.recoll.org/features.html</ulink>">
|
||||||
<!ENTITY RCLVERSION "1.25">
|
<!ENTITY RCLVERSION "1.26">
|
||||||
<!ENTITY XAP "<application>Xapian</application>">
|
<!ENTITY XAP "<application>Xapian</application>">
|
||||||
<!ENTITY WIN "<application>Windows</application>">
|
<!ENTITY WIN "<application>Windows</application>">
|
||||||
<!ENTITY LIN "<application>Unix</application>-like systems">
|
<!ENTITY LIN "<application>Unix</application>-like systems">
|
||||||
@ -32,7 +32,7 @@
|
|||||||
</author>
|
</author>
|
||||||
|
|
||||||
<copyright>
|
<copyright>
|
||||||
<year>2005-2019</year>
|
<year>2005-2020</year>
|
||||||
<holder role="mailto:jfd@recoll.org">Jean-Francois Dockes</holder>
|
<holder role="mailto:jfd@recoll.org">Jean-Francois Dockes</holder>
|
||||||
</copyright>
|
</copyright>
|
||||||
|
|
||||||
@ -62,16 +62,18 @@
|
|||||||
application. It is updated for &RCL; &RCLVERSION;.</para>
|
application. It is updated for &RCL; &RCLVERSION;.</para>
|
||||||
|
|
||||||
<para>&RCL; was for a long time dedicated to Unix-like systems. It
|
<para>&RCL; was for a long time dedicated to Unix-like systems. It
|
||||||
was only lately (2015) ported to
|
was only lately (2015) ported to
|
||||||
<application>MS-Windows</application>. Many references in this
|
<application>MS-Windows</application>. Many references in this
|
||||||
manual, especially file locations, are specific to Unix, and not
|
manual, especially file locations, are specific to Unix, and not
|
||||||
valid on &WIN;, where some described features are also not available.
|
valid on &WIN;, where some described features are also not available.
|
||||||
The manual will be progressively updated. Until this happens, on
|
The manual will be progressively updated. Until this happens, on
|
||||||
&WIN;, most references to shared files can be translated by looking
|
&WIN;, most references to shared files can be translated by looking
|
||||||
under the Recoll installation directory (esp. the
|
under the Recoll installation directory (Typically <filename>C:/Program
|
||||||
<filename>Share</filename> subdirectory). The user configuration is
|
Files (x86)/Recoll</filename>, esp. anything referenced
|
||||||
stored by default under <filename>AppData/Local/Recoll</filename>
|
in <filename>/usr/share</filename> in this document will be found int
|
||||||
inside the user directory, along with the index itself.</para>
|
the <filename>Share</filename> subdirectory). The user configuration is
|
||||||
|
stored by default under <filename>AppData/Local/Recoll</filename>
|
||||||
|
inside the user directory, along with the index itself.</para>
|
||||||
|
|
||||||
<sect1 id="RCL.INTRODUCTION.TRYIT">
|
<sect1 id="RCL.INTRODUCTION.TRYIT">
|
||||||
<title>Giving it a try</title>
|
<title>Giving it a try</title>
|
||||||
@ -238,16 +240,18 @@
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>&RCL; uses many parameters to define exactly what to index,
|
<para>&RCL; uses many parameters to define exactly what to index,
|
||||||
and how to classify and decode the source documents. These are kept
|
and how to classify and decode the source documents. These are kept
|
||||||
in <link linkend="RCL.INDEXING.CONFIG">configuration files</link>. A
|
in <link linkend="RCL.INDEXING.CONFIG">configuration files</link>. A
|
||||||
default configuration is copied into a standard location (usually
|
default configuration is copied into a standard location (usually
|
||||||
something like <filename>/usr/share/recoll/examples</filename>)
|
something like <filename>/usr/share/recoll/examples</filename>)
|
||||||
during installation. The default values set by the configuration
|
during installation. The default values set by the configuration
|
||||||
files in this directory may be overridden by values set inside your
|
files in this directory may be overridden by values set inside your
|
||||||
personal configuration. With the default configuration, &RCL; will
|
personal configuration. With the default configuration, &RCL; will
|
||||||
index your home directory with generic parameters. The configuration
|
index your home directory with generic parameters. Most common
|
||||||
can be customized either by editing the text files or by using
|
parameters can be set by using
|
||||||
configuration menus in the <command>recoll</command> GUI.</para>
|
configuration menus in the <command>recoll</command> GUI. Some less
|
||||||
|
common parameters can only be set by editing the text files (the
|
||||||
|
new values will be preserved by the GUI).</para>
|
||||||
|
|
||||||
<para>The <link linkend="RCL.INDEXING.PERIODIC.EXEC">indexing process</link>
|
<para>The <link linkend="RCL.INDEXING.PERIODIC.EXEC">indexing process</link>
|
||||||
is started automatically (after asking permission), the
|
is started automatically (after asking permission), the
|
||||||
@ -303,11 +307,9 @@
|
|||||||
<option>-z</option> or <option>-Z</option>).</para>
|
<option>-z</option> or <option>-Z</option>).</para>
|
||||||
|
|
||||||
<para><command>recollindex</command> skips files which caused an
|
<para><command>recollindex</command> skips files which caused an
|
||||||
error during a previous pass. This is a performance
|
error during a previous pass. This is a performance optimization, and
|
||||||
optimization, and a new behaviour in version 1.21 (failed files
|
the command line option <option>-k</option> can be set to retry
|
||||||
were always retried by previous versions). The command line
|
failed files, for example after updating an input handler.</para>
|
||||||
option <option>-k</option> can be set to retry failed files, for
|
|
||||||
example after updating an input handler.</para>
|
|
||||||
|
|
||||||
<para>The following sections give an overview of different
|
<para>The following sections give an overview of different
|
||||||
aspects of the indexing processes and configuration, with links
|
aspects of the indexing processes and configuration, with links
|
||||||
@ -329,15 +331,15 @@
|
|||||||
<listitem>
|
<listitem>
|
||||||
<formalpara><title>
|
<formalpara><title>
|
||||||
<link linkend="RCL.INDEXING.PERIODIC">Periodic (or batch) indexing</link>
|
<link linkend="RCL.INDEXING.PERIODIC">Periodic (or batch) indexing</link>
|
||||||
</title>
|
</title> <para><command>recollindex</command> is executed at
|
||||||
<para><command>recollindex</command> is executed
|
discrete times. On &LIN;, the typical usage is to have a
|
||||||
at discrete times. On &LIN;, the typical usage is to have a
|
nightly run
|
||||||
nightly run
|
<link linkend="RCL.INDEXING.PERIODIC.AUTOMAT">
|
||||||
<link linkend="RCL.INDEXING.PERIODIC.AUTOMAT">programmed</link>
|
programmed</link>
|
||||||
into your <command>cron</command> file. On &WIN;, this is
|
into your <command>cron</command> file. On &WIN;, this is
|
||||||
the only mode available, and the indexer is usually started
|
the only mode available, and the Windows Task Scheduler can
|
||||||
from the GUI (but there is nothing to prevent starting it
|
be used to run indexing. In both cases, the GUI includes an
|
||||||
from a command script).</para>
|
easy interface to the system batch scheduler.</para>
|
||||||
</formalpara>
|
</formalpara>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
@ -367,7 +369,7 @@
|
|||||||
<menuchoice>
|
<menuchoice>
|
||||||
<guimenu>Preferences</guimenu>
|
<guimenu>Preferences</guimenu>
|
||||||
<guimenuitem>Indexing schedule</guimenuitem>
|
<guimenuitem>Indexing schedule</guimenuitem>
|
||||||
</menuchoice>
|
</menuchoice> dialog.
|
||||||
</para>
|
</para>
|
||||||
</simplesect>
|
</simplesect>
|
||||||
|
|
||||||
@ -540,24 +542,19 @@
|
|||||||
corrupt, we may fail to uncompress a file because no file
|
corrupt, we may fail to uncompress a file because no file
|
||||||
system space is available, etc.</para>
|
system space is available, etc.</para>
|
||||||
|
|
||||||
<para>&RCL; versions prior to 1.21 always retried to index
|
<para>The &RCL; indexer in versions 1.21 and later does not
|
||||||
files which had previously caused an error. This guaranteed
|
retry failed files by default, because some indexing failures
|
||||||
that anything that may have become indexable (for example
|
can be quite costly (for example failing to uncompress a big
|
||||||
because a helper had been installed) would be indexed. However
|
file because of insufficient disk space).
|
||||||
this was bad for performance because some indexing failures
|
Retrying will only occur if an explicit option
|
||||||
may be quite costly (for example failing to uncompress a big
|
(<option>-k</option>) is set on
|
||||||
file because of insufficient disk space).</para>
|
the <command>recollindex</command> command line, or if a script
|
||||||
|
executed when <command>recollindex</command> starts up says
|
||||||
<para>The indexer in &RCL; versions 1.21 and later does not
|
so. The script is defined by a configuration variable
|
||||||
retry failed files by default. Retrying will only occur if an
|
(<literal>checkneedretryindexscript</literal>), and makes a
|
||||||
explicit option (<option>-k</option>) is set on the
|
rather lame attempt at deciding if a helper command may have been
|
||||||
<command>recollindex</command> command line, or if a script
|
installed, by checking if any of the
|
||||||
executed when <command>recollindex</command> starts up says
|
common <filename>bin</filename> directories have changed.</para>
|
||||||
so. The script is defined by a configuration variable
|
|
||||||
(<literal>checkneedretryindexscript</literal>), and makes a
|
|
||||||
rather lame attempt at deciding if a helper command may have
|
|
||||||
been installed, by checking if any of the common
|
|
||||||
<filename>bin</filename> directories have changed.</para>
|
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
@ -638,7 +635,7 @@
|
|||||||
|
|
||||||
<para>Of course, images, sound and video do not increase the index
|
<para>Of course, images, sound and video do not increase the index
|
||||||
size, which means that in most cases, the space used by the index
|
size, which means that in most cases, the space used by the index
|
||||||
will be negligible against the total amount of data on the
|
will be negligible compared to the total amount of data on the
|
||||||
computer.</para>
|
computer.</para>
|
||||||
|
|
||||||
<para>The index data directory (<filename>xapiandb</filename>)
|
<para>The index data directory (<filename>xapiandb</filename>)
|
||||||
@ -727,13 +724,13 @@
|
|||||||
<sect1 id="RCL.INDEXING.CONFIG">
|
<sect1 id="RCL.INDEXING.CONFIG">
|
||||||
<title>Index configuration</title>
|
<title>Index configuration</title>
|
||||||
|
|
||||||
<para>Variables set inside the
|
<para>Variables stored inside the
|
||||||
<link linkend="RCL.INSTALL.CONFIG">&RCL; configuration files</link>
|
<link linkend="RCL.INSTALL.CONFIG">&RCL; configuration files</link>
|
||||||
control which areas of the file system are indexed, and how
|
control which areas of the file system are indexed, and how files
|
||||||
files are processed. These variables can be set either by
|
are processed. The values can be set by editing the text
|
||||||
editing the text files or by using the
|
files. Most of the more commonly used ones can also be adjusted by
|
||||||
<link linkend="RCL.INDEXING.CONFIG.GUI">dialogs in the <command>recoll</command> GUI</link>.
|
using the <link linkend="RCL.INDEXING.CONFIG.GUI">
|
||||||
</para>
|
dialogs in the <command>recoll</command> GUI</link>.</para>
|
||||||
|
|
||||||
<para>The first time you start <command>recoll</command>, you will be
|
<para>The first time you start <command>recoll</command>, you will be
|
||||||
asked whether or not you would like it to build the index. If you
|
asked whether or not you would like it to build the index. If you
|
||||||
@ -748,7 +745,7 @@
|
|||||||
<link linkend="RCL.INSTALL.CONFIG">installation chapter</link>
|
<link linkend="RCL.INSTALL.CONFIG">installation chapter</link>
|
||||||
of this document, or in the
|
of this document, or in the
|
||||||
<ulink url="https://www.lesbonscomptes.com/recoll/manpages/recoll.conf.5.html"><citerefentry><refentrytitle>recoll.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></ulink>
|
<ulink url="https://www.lesbonscomptes.com/recoll/manpages/recoll.conf.5.html"><citerefentry><refentrytitle>recoll.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></ulink>
|
||||||
manual page.Both documents are automatically generated from
|
manual page. Both documents are automatically generated from
|
||||||
the comments inside the configuration file.</para>
|
the comments inside the configuration file.</para>
|
||||||
|
|
||||||
<para>The most immediately useful variable
|
<para>The most immediately useful variable
|
||||||
@ -761,11 +758,11 @@
|
|||||||
described in the <link linkend="RCL.INSTALL.EXTERNAL">external packages section</link>.
|
described in the <link linkend="RCL.INSTALL.EXTERNAL">external packages section</link>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>As of Recoll 1.18 there are two incompatible types of Recoll
|
<para>There are two incompatible types of Recoll
|
||||||
indexes, depending on the treatment of character case and
|
indexes, depending on the treatment of character case and
|
||||||
diacritics. A
|
diacritics. A <link linkend="RCL.INDEXING.CONFIG.SENS">further
|
||||||
<link linkend="RCL.INDEXING.CONFIG.SENS">further section</link>
|
section</link> describes the two types in more detail. The default
|
||||||
describes the two types in more detail.</para>
|
type is appropriate in most cases.</para>
|
||||||
|
|
||||||
<sect2 id="RCL.INDEXING.CONFIG.MULTIPLE">
|
<sect2 id="RCL.INDEXING.CONFIG.MULTIPLE">
|
||||||
<title>Multiple indexes</title>
|
<title>Multiple indexes</title>
|
||||||
@ -1088,9 +1085,9 @@ recoll -c <replaceable>/path/to/my/new/config</replaceable></programlisting>
|
|||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>By indexing the volume in the main, fixed, index, and
|
<listitem><para>By indexing the volume in the main, fixed, index, and
|
||||||
ensuring that the volume data is not purged if the indexing runs
|
ensuring that the volume data is not purged if the indexing runs
|
||||||
while the volume is mounted. (&RCL; 1.25.2).</para></listitem>
|
while the volume is mounted. (since &RCL; 1.25.2).</para></listitem>
|
||||||
<listitem><para>By storing a volume index on the volume
|
<listitem><para>By storing a volume index on the volume
|
||||||
itself (&RCL; 1.24).</para></listitem>
|
itself (since &RCL; 1.24).</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<simplesect id="RCL.INDEXING.REMOVABLE.MAIN">
|
<simplesect id="RCL.INDEXING.REMOVABLE.MAIN">
|
||||||
@ -1402,27 +1399,27 @@ metadatacmds = ; <replaceable>tags</replaceable> = tmsu tags %f
|
|||||||
<title>The PDF input handler</title>
|
<title>The PDF input handler</title>
|
||||||
|
|
||||||
<para>The PDF format is very important for scientific and technical
|
<para>The PDF format is very important for scientific and technical
|
||||||
documentation, and document archival. It has extensive
|
documentation, and document archival. It has extensive
|
||||||
facilities for storing metadata along with the document, and these
|
facilities for storing metadata along with the document, and these
|
||||||
facilities are actually used in the real world.</para>
|
facilities are actually used in the real world.</para>
|
||||||
|
|
||||||
<para>In consequence, the <command>rclpdf.py</command> PDF input
|
<para>In consequence, the <command>rclpdf.py</command> PDF input
|
||||||
handler has more complex capabilities than most others, and it is
|
handler has more complex capabilities than most others, and it is
|
||||||
also more configurable. Specifically, <command>rclpdf.py</command>
|
also more configurable. Specifically, <command>rclpdf.py</command>
|
||||||
has the following features:
|
has the following features:
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>It can be configured to extract
|
<listitem><para>It can be configured to extract
|
||||||
specific metadata tags from an XMP packet.</para></listitem>
|
specific metadata tags from an XMP packet.</para></listitem>
|
||||||
<listitem><para>It can extract PDF
|
<listitem><para>It can extract PDF
|
||||||
attachments.</para></listitem>
|
attachments.</para></listitem>
|
||||||
<listitem><para>It can automatically perform
|
<listitem><para>It can automatically perform
|
||||||
OCR if the document text is empty. This is done by
|
OCR if the document text is empty. This is done by
|
||||||
executing an external program and is now described in a
|
executing an external program and is now described in a
|
||||||
<link linkend="RCL.INDEXING.OCR">separate
|
<link linkend="RCL.INDEXING.OCR">separate
|
||||||
section</link>, because the OCR framework can also be used
|
section</link>, because the OCR framework can also be used
|
||||||
with non-PDF image files.</para></listitem>
|
with non-PDF image files.</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<sect2 id="RCL.INDEXING.PDF.XMP">
|
<sect2 id="RCL.INDEXING.PDF.XMP">
|
||||||
<title>XMP fields extraction</title>
|
<title>XMP fields extraction</title>
|
||||||
@ -1496,48 +1493,48 @@ metadatacmds = ; <replaceable>tags</replaceable> = tmsu tags %f
|
|||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
|
||||||
<sect1 id="RCL.INDEXING.OCR">
|
<sect1 id="RCL.INDEXING.OCR">
|
||||||
<title>Recoll and OCR</title>
|
<title>Recoll and OCR</title>
|
||||||
|
|
||||||
<para>This is new in &RCL; 1.26.5. Older versions had a more limited,
|
<para>This is new in &RCL; 1.26.5. Older versions had a more limited,
|
||||||
non-caching capability to execute an external OCR program in the PDF
|
non-caching capability to execute an external OCR program in the PDF
|
||||||
handler. The new function has the following features:
|
handler. The new function has the following features:
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>The OCR output is cached, stored as separate
|
<listitem><para>The OCR output is cached, stored as separate
|
||||||
files. The caching is ultimately based on a hash value of the
|
files. The caching is ultimately based on a hash value of the
|
||||||
original file contents, so that it is immune to file renames. A
|
original file contents, so that it is immune to file renames. A
|
||||||
first path-based layer ensures fast operation for unchanged
|
first path-based layer ensures fast operation for unchanged
|
||||||
(unmoved files), and the data hash (which is still orders of
|
(unmoved files), and the data hash (which is still orders of
|
||||||
magnitude faster than OCR) is only re-computed if the file has
|
magnitude faster than OCR) is only re-computed if the file has
|
||||||
moved. OCR is only performed if the file was not previously
|
moved. OCR is only performed if the file was not previously
|
||||||
processed or if it changed.</para></listitem>
|
processed or if it changed.</para></listitem>
|
||||||
<listitem><para>The support for a specific program is implemented
|
<listitem><para>The support for a specific program is implemented
|
||||||
in a simple Python module. It should be straightforward to add
|
in a simple Python module. It should be straightforward to add
|
||||||
support for any OCR engine with a capability to run from the
|
support for any OCR engine with a capability to run from the
|
||||||
command line.</para></listitem>
|
command line.</para></listitem>
|
||||||
<listitem><para>Modules initially exist for
|
<listitem><para>Modules initially exist for
|
||||||
<application>tesseract</application> (Linux and Windows), and
|
<application>tesseract</application> (Linux and Windows), and
|
||||||
<application>ABBYY FineReader</application> (Linux, tested with
|
<application>ABBYY FineReader</application> (Linux, tested with
|
||||||
version 11). ABBYY FineReader is a commercial closed source
|
version 11). ABBYY FineReader is a commercial closed source
|
||||||
program, but it sometimes perform better than
|
program, but it sometimes perform better than
|
||||||
tesseract.</para></listitem>
|
tesseract.</para></listitem>
|
||||||
<listitem><para>The OCR is currently only called from the PDF
|
<listitem><para>The OCR is currently only called from the PDF
|
||||||
handler, but there should be no problem using it for other image
|
handler, but there should be no problem using it for other image
|
||||||
types.</para></listitem>
|
types.</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>To enable this feature, you need to install one of
|
<para>To enable this feature, you need to install one of
|
||||||
the supported OCR applications
|
the supported OCR applications
|
||||||
(<application>tesseract</application>
|
(<application>tesseract</application>
|
||||||
or <application>ABBYY</application>), enable OCR in the PDF
|
or <application>ABBYY</application>), enable OCR in the PDF
|
||||||
handler, and tell &RCL; where the appropriate command resides. The
|
handler, and tell &RCL; where the appropriate command resides. The
|
||||||
last parts are done by setting configuration variables. See the
|
last parts are done by setting configuration variables. See the
|
||||||
<link linkend="RCL.INSTALL.CONFIG.RECOLLCONF.OCR">
|
<link linkend="RCL.INSTALL.CONFIG.RECOLLCONF.OCR">
|
||||||
relevant section</link>. All parameters can be localized in
|
relevant section</link>. All parameters can be localized in
|
||||||
subdirectories through the usual main configuration mechanism (path
|
subdirectories through the usual main configuration mechanism (path
|
||||||
sections).</para>
|
sections).</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
@ -1564,20 +1561,12 @@ metadatacmds = ; <replaceable>tags</replaceable> = tmsu tags %f
|
|||||||
|
|
||||||
<para>The GUI <menuchoice><guimenu>File</guimenu> </menuchoice>
|
<para>The GUI <menuchoice><guimenu>File</guimenu> </menuchoice>
|
||||||
menu has entries to start or stop the current indexing
|
menu has entries to start or stop the current indexing
|
||||||
operation.</para>
|
operation. When indexing is not currently running, you have a
|
||||||
|
choice of updating the index or rebuilding it (the first choice
|
||||||
|
only processes changed files, the second one zeroes the index
|
||||||
|
before starting so that all files are processed).</para>
|
||||||
|
|
||||||
<para>When no indexing is running, you have a choice of updating the
|
<para>On Linux and Windows, the GUI can be used to manage the indexing
|
||||||
index or rebuilding it (the first choice only processes changed
|
|
||||||
files, the second one zeroes the index before starting so that all
|
|
||||||
files are processed).</para>
|
|
||||||
|
|
||||||
<para>On Linux, the <command>recollindex</command> indexing process
|
|
||||||
can be interrupted by sending an interrupt
|
|
||||||
(<keysym>Ctrl-C</keysym>, SIGINT) or terminate (SIGTERM)
|
|
||||||
signal.
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>On Linux and Windows, the GUI can used to manage the indexing
|
|
||||||
operation. Stopping the indexer can be done
|
operation. Stopping the indexer can be done
|
||||||
from the <command>recoll</command> GUI
|
from the <command>recoll</command> GUI
|
||||||
<menuchoice>
|
<menuchoice>
|
||||||
@ -1587,6 +1576,12 @@ metadatacmds = ; <replaceable>tags</replaceable> = tmsu tags %f
|
|||||||
menu entry.
|
menu entry.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>On Linux, the <command>recollindex</command> indexing process
|
||||||
|
can be interrupted by sending an interrupt
|
||||||
|
(<keysym>Ctrl-C</keysym>, SIGINT) or terminate (SIGTERM)
|
||||||
|
signal.
|
||||||
|
</para>
|
||||||
|
|
||||||
<para>When stopped, some time may elapse before
|
<para>When stopped, some time may elapse before
|
||||||
<command>recollindex</command> exits, because it needs to properly
|
<command>recollindex</command> exits, because it needs to properly
|
||||||
flush and close the index.</para>
|
flush and close the index.</para>
|
||||||
@ -1601,6 +1596,10 @@ metadatacmds = ; <replaceable>tags</replaceable> = tmsu tags %f
|
|||||||
file tree will be traversed, but files that were indexed up
|
file tree will be traversed, but files that were indexed up
|
||||||
to the interruption and for which the index is still up to
|
to the interruption and for which the index is still up to
|
||||||
date will not need to be reindexed).</para>
|
date will not need to be reindexed).</para>
|
||||||
|
</simplesect>
|
||||||
|
|
||||||
|
<simplesect id="RCL.INDEXING.PERIODIC.CMDLINE">
|
||||||
|
<title>recollindex command line</title>
|
||||||
|
|
||||||
<para><command>recollindex</command> has many options
|
<para><command>recollindex</command> has many options
|
||||||
which are listed in its
|
which are listed in its
|
||||||
@ -1879,19 +1878,19 @@ fs.inotify.max_user_watches=32768
|
|||||||
<title>Searching with the Qt graphical user interface</title>
|
<title>Searching with the Qt graphical user interface</title>
|
||||||
|
|
||||||
<para>The <command>recoll</command> program provides the main user
|
<para>The <command>recoll</command> program provides the main user
|
||||||
interface for searching. It is based on the
|
interface for searching. It is based on the
|
||||||
<application>Qt</application> library.</para>
|
<application>Qt</application> library.</para>
|
||||||
|
|
||||||
<para><command>recoll</command> has two search modes:</para>
|
<para><command>recoll</command> has two search interfaces:</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>Simple search (the default, on the main screen) has
|
<listitem><para>Simple search (the default, on the main screen) has
|
||||||
a single entry field where you can enter multiple words.</para>
|
a single entry field where you can enter multiple words.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem><para>Advanced search (a panel accessed through the
|
<listitem><para>Advanced search (a panel accessed through the
|
||||||
<guilabel>Tools</guilabel> menu or the toolbox bar icon) has
|
<guilabel>Tools</guilabel> menu or the toolbox bar icon) has
|
||||||
multiple entry fields, which you may use to build a logical
|
multiple entry fields, which you may use to build a logical
|
||||||
condition, with additional filtering on file type, location
|
condition, with additional filtering on file type, location
|
||||||
in the file system, modification date, and size.</para>
|
in the file system, modification date, and size.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
@ -1956,32 +1955,6 @@ fs.inotify.max_user_watches=32768
|
|||||||
<link linkend="RCL.SEARCH.LANG">a separate section</link>.
|
<link linkend="RCL.SEARCH.LANG">a separate section</link>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>The <guilabel>File name</guilabel> search mode will
|
|
||||||
specifically look for file names. The point of having a separate
|
|
||||||
file name search is that wild card expansion can be performed more
|
|
||||||
efficiently on a small subset of the index (allowing wild cards on
|
|
||||||
the left of terms without excessive cost). Things to know:
|
|
||||||
<itemizedlist>
|
|
||||||
<listitem><para>White space in the entry should match white
|
|
||||||
space in the file name, and is not treated specially.</para>
|
|
||||||
</listitem>
|
|
||||||
<listitem><para>The search is insensitive to character case and
|
|
||||||
accents, independently of the type of index.</para>
|
|
||||||
</listitem>
|
|
||||||
<listitem><para>An entry without any wild card
|
|
||||||
character and not capitalized will be prepended and appended
|
|
||||||
with '*' (ie: <replaceable>etc</replaceable> ->
|
|
||||||
<replaceable>*etc*</replaceable>, but
|
|
||||||
<replaceable>Etc</replaceable> ->
|
|
||||||
<replaceable>etc</replaceable>).</para>
|
|
||||||
</listitem>
|
|
||||||
<listitem><para>If you have a big index (many files),
|
|
||||||
excessively generic fragments may result in inefficient
|
|
||||||
searches.</para>
|
|
||||||
</listitem>
|
|
||||||
</itemizedlist>
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>When using a stripped index (the default), character case has
|
<para>When using a stripped index (the default), character case has
|
||||||
no influence on search, except that you can disable stem expansion
|
no influence on search, except that you can disable stem expansion
|
||||||
for any term by capitalizing it. Ie: a search for
|
for any term by capitalizing it. Ie: a search for
|
||||||
@ -2018,75 +1991,62 @@ fs.inotify.max_user_watches=32768
|
|||||||
<para>You can use the <link linkend="RCL.SEARCH.GUI.COMPLEX"><menuchoice><guimenu>Tools</guimenu><guimenuitem>Advanced search</guimenuitem></menuchoice></link>
|
<para>You can use the <link linkend="RCL.SEARCH.GUI.COMPLEX"><menuchoice><guimenu>Tools</guimenu><guimenuitem>Advanced search</guimenuitem></menuchoice></link>
|
||||||
dialog for more complex searches.</para>
|
dialog for more complex searches.</para>
|
||||||
|
|
||||||
|
<para>The <guilabel>File name</guilabel> search mode will
|
||||||
|
specifically look for file names. The point of having a separate
|
||||||
|
file name search is that wild card expansion can be performed more
|
||||||
|
efficiently on a small subset of the index (allowing wild cards on
|
||||||
|
the left of terms without excessive cost). Things to know:
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem><para>White space in the entry should match white
|
||||||
|
space in the file name, and is not treated specially.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem><para>The search is insensitive to character case and
|
||||||
|
accents, independently of the type of index.</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem><para>An entry without any wild card
|
||||||
|
character and not capitalized will be prepended and appended
|
||||||
|
with '*' (ie: <replaceable>etc</replaceable> ->
|
||||||
|
<replaceable>*etc*</replaceable>, but
|
||||||
|
<replaceable>Etc</replaceable> ->
|
||||||
|
<replaceable>etc</replaceable>).</para>
|
||||||
|
</listitem>
|
||||||
|
<listitem><para>If you have a big index (many files),
|
||||||
|
excessively generic fragments may result in inefficient
|
||||||
|
searches.</para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="RCL.SEARCH.GUI.RESLIST">
|
<sect2 id="RCL.SEARCH.GUI.RESLIST">
|
||||||
<title>The default result list</title>
|
<title>The result list</title>
|
||||||
|
|
||||||
<para>After starting a search, a list of results will instantly
|
<para>After starting a search, a list of results will instantly
|
||||||
be displayed in the main list window.</para>
|
be displayed in the main window.</para>
|
||||||
|
|
||||||
<para>By default, the document list is presented in order of
|
<para>By default, the document list is presented in order of
|
||||||
relevance (how well the system estimates that the document
|
relevance (how well the system estimates that the document
|
||||||
matches the query). You can sort the result by ascending or
|
matches the query). You can sort the result by ascending or
|
||||||
descending date by using the vertical arrows in the toolbar.</para>
|
descending date by using the vertical arrows in the toolbar.</para>
|
||||||
|
|
||||||
<para>Clicking on the
|
<para>Clicking the <literal>Preview</literal> link for an entry
|
||||||
<literal>Preview</literal> link for an entry will open an
|
will open an internal preview window for the document. Further
|
||||||
internal preview window for the document. Further
|
<literal>Preview</literal> clicks for the same search will open
|
||||||
<literal>Preview</literal> clicks for the same search will open
|
tabs in the existing preview window. You can use
|
||||||
tabs in the existing preview window. You can use
|
<keycap>Shift</keycap>+Click to force the creation of another
|
||||||
<keycap>Shift</keycap>+Click to force the creation of another
|
preview window, which may be useful to view the documents side
|
||||||
preview window, which may be useful to view the documents side
|
by side. (You can also browse successive results in a single
|
||||||
by side. (You can also browse successive results in a single
|
preview window by typing
|
||||||
preview window by typing
|
<keycap>Shift</keycap>+<keycap>ArrowUp/Down</keycap> in the
|
||||||
<keycap>Shift</keycap>+<keycap>ArrowUp/Down</keycap> in the
|
window).</para>
|
||||||
window).</para>
|
|
||||||
|
|
||||||
<para>Clicking the <literal>Open</literal> link will
|
<para>Clicking the <literal>Open</literal> link will
|
||||||
start an external viewer for the document. By default, &RCL; lets
|
start an external viewer for the document. By default, &RCL; lets
|
||||||
the desktop choose the appropriate application for most document
|
the desktop choose the appropriate application for most document
|
||||||
types (there is a short list of exceptions, see further). If you
|
types. This currently not customisable on &WIN;. See
|
||||||
prefer to completely customize the choice of applications, you can
|
<link linkend="RCL.SEARCH.GUI.RESLIST.APPLICATIONS">further</link>
|
||||||
uncheck the <guilabel>Use desktop preferences</guilabel> option in
|
for customizing the applications on &LIN;.</para>
|
||||||
the GUI preferences dialog, and click the <guilabel>Choose editor
|
|
||||||
applications</guilabel> button to adjust the predefined &RCL;
|
|
||||||
choices. The tool accepts multiple selections of MIME types (e.g. to
|
|
||||||
set up the editor for the dozens of office file types).</para>
|
|
||||||
|
|
||||||
<para>Even when <guilabel>Use desktop preferences</guilabel> is
|
|
||||||
checked, there is a small list of exceptions, for MIME types where
|
|
||||||
the &RCL; choice should override the desktop one. These are
|
|
||||||
applications which are well integrated with &RCL;, especially
|
|
||||||
<application>evince</application> for viewing PDF and Postscript
|
|
||||||
files because of its support for opening the document at a specific
|
|
||||||
page and passing a search string as an argument. Of course, you can
|
|
||||||
edit the list (in the GUI preferences) if you would prefer to lose
|
|
||||||
the functionality and use the standard desktop tool.</para>
|
|
||||||
|
|
||||||
<para>You may also change the choice of applications by editing the
|
|
||||||
<link linkend="RCL.INSTALL.CONFIG.MIMEVIEW"><filename>mimeview</filename></link>
|
|
||||||
configuration file if you find this more convenient.</para>
|
|
||||||
|
|
||||||
<para>Each result entry also has a right-click menu with an
|
|
||||||
<guilabel>Open With</guilabel> entry. This lets you choose an
|
|
||||||
application from the list of those which registered with the desktop
|
|
||||||
for the document MIME type.</para>
|
|
||||||
|
|
||||||
<para>The <literal>Preview</literal> and <literal>Open</literal>
|
|
||||||
edit links may not be present for all entries, meaning that
|
|
||||||
&RCL; has no configured way to preview a given file type (which
|
|
||||||
was indexed by name only), or no configured external editor for
|
|
||||||
the file type. This can sometimes be adjusted simply by tweaking
|
|
||||||
the <link linkend="RCL.INSTALL.CONFIG.MIMEMAP"><filename>mimemap</filename></link>
|
|
||||||
and <link linkend="RCL.INSTALL.CONFIG.MIMEVIEW"><filename>mimeview</filename></link>
|
|
||||||
configuration files (the latter can be modified with the user
|
|
||||||
preferences dialog).</para>
|
|
||||||
|
|
||||||
<para>The format of the result list entries is entirely
|
|
||||||
configurable by using the preference dialog to
|
|
||||||
<link linkend="RCL.SEARCH.GUI.CUSTOM.RESLIST">edit an HTML fragment</link>.
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>You can click on the <literal>Query details</literal> link
|
<para>You can click on the <literal>Query details</literal> link
|
||||||
at the top of the results page to see the query actually
|
at the top of the results page to see the query actually
|
||||||
@ -2100,6 +2060,76 @@ fs.inotify.max_user_watches=32768
|
|||||||
toolbar or the links at the bottom of the page to browse the
|
toolbar or the links at the bottom of the page to browse the
|
||||||
results.</para>
|
results.</para>
|
||||||
|
|
||||||
|
<para>The <literal>Preview</literal> and <literal>Open</literal>
|
||||||
|
edit links may not be present for all entries, meaning that
|
||||||
|
&RCL; has no configured way to preview a given file type (which
|
||||||
|
was indexed by name only), or no configured external editor for
|
||||||
|
the file type. This can sometimes be adjusted simply by tweaking
|
||||||
|
the <link linkend="RCL.INSTALL.CONFIG.MIMEMAP">
|
||||||
|
<filename>mimemap</filename></link>
|
||||||
|
and <link linkend="RCL.INSTALL.CONFIG.MIMEVIEW">
|
||||||
|
<filename>mimeview</filename></link>
|
||||||
|
configuration files (the latter can be modified with the user
|
||||||
|
preferences dialog).</para>
|
||||||
|
|
||||||
|
<para>The format of the result list entries is entirely
|
||||||
|
configurable by using the preference dialog to
|
||||||
|
<link linkend="RCL.SEARCH.GUI.CUSTOM.RESLIST">
|
||||||
|
edit an HTML fragment</link>.</para>
|
||||||
|
|
||||||
|
<simplesect id="RCL.SEARCH.GUI.RESLIST.APPLICATIONS">
|
||||||
|
<title>&LIN;: customising the applications</title>
|
||||||
|
|
||||||
|
<para>By default &RCL; lets the desktop choose what
|
||||||
|
application should be used to open a given document, with
|
||||||
|
exceptions.</para>
|
||||||
|
|
||||||
|
<para>The details of this behaviour can be customized with the
|
||||||
|
<menuchoice>
|
||||||
|
<guimenu>Preferences</guimenu>
|
||||||
|
<guimenuitem>GUI configuration</guimenuitem>
|
||||||
|
<guimenuitem>User interface</guimenuitem>
|
||||||
|
<guimenuitem>Choose editor applications</guimenuitem>
|
||||||
|
</menuchoice> dialog or by editing
|
||||||
|
the <link linkend="RCL.INSTALL.CONFIG.MIMEVIEW">
|
||||||
|
<filename>mimeview</filename> configuration file.</link></para>
|
||||||
|
|
||||||
|
<para>When <guilabel>Use desktop preferences</guilabel>, at the
|
||||||
|
top of the dialog, is checked, there is a small list of
|
||||||
|
exceptions, for MIME types where the &RCL; choice should
|
||||||
|
override the desktop one. These are applications which are well
|
||||||
|
integrated with &RCL;, for example, on
|
||||||
|
Linux, <application>evince</application> for viewing PDF and
|
||||||
|
Postscript files because of its support for opening the
|
||||||
|
document at a specific page and passing a search string as an
|
||||||
|
argument. You can add or remove document types to the
|
||||||
|
exceptions by using the dialog.</para>
|
||||||
|
|
||||||
|
<para>If you prefer to completely customize the choice of
|
||||||
|
applications, you can uncheck <guilabel>Use desktop
|
||||||
|
preferences</guilabel>, in which case the &RCL; predefined
|
||||||
|
applications will be used, and can be changed for each document
|
||||||
|
type. This is probably not the most convenient approach in most
|
||||||
|
cases.</para>
|
||||||
|
|
||||||
|
<para>In all cases, the applications choice dialog accepts
|
||||||
|
multiple selections of MIME types in the top section, and lets
|
||||||
|
you define how they are processed in the bottom one.</para>
|
||||||
|
|
||||||
|
<para>You may also change the choice of applications by editing
|
||||||
|
the
|
||||||
|
<link linkend="RCL.INSTALL.CONFIG.MIMEVIEW">
|
||||||
|
<filename>mimeview</filename></link>
|
||||||
|
configuration file if you find this more convenient.</para>
|
||||||
|
|
||||||
|
<para>Under &LIN;, each result list entry also has a right-click
|
||||||
|
menu with an
|
||||||
|
<guilabel>Open With</guilabel> entry. This lets you choose an
|
||||||
|
application from the list of those which registered with the desktop
|
||||||
|
for the document MIME type, on a case by case basis.</para>
|
||||||
|
</simplesect>
|
||||||
|
|
||||||
|
|
||||||
<sect3 id="RCL.SEARCH.GUI.RESLIST.SUGGS">
|
<sect3 id="RCL.SEARCH.GUI.RESLIST.SUGGS">
|
||||||
<title>No results: the spelling suggestions</title>
|
<title>No results: the spelling suggestions</title>
|
||||||
|
|
||||||
@ -2143,17 +2173,17 @@ fs.inotify.max_user_watches=32768
|
|||||||
<guilabel>Open</guilabel> entries do the same thing as the
|
<guilabel>Open</guilabel> entries do the same thing as the
|
||||||
corresponding links.</para>
|
corresponding links.</para>
|
||||||
|
|
||||||
<para><guilabel>Open With</guilabel> lets you open the document
|
<para><guilabel>Open With</guilabel> (&LIN;) lets you open the
|
||||||
with one of the applications claiming to be able to handle its MIME
|
document with one of the applications claiming to be able to
|
||||||
type (the information comes from the <literal>.desktop</literal>
|
handle its MIME type (the information comes from
|
||||||
files in
|
the <literal>.desktop</literal> files
|
||||||
<filename>/usr/share/applications</filename>).</para>
|
in <filename>/usr/share/applications</filename>).</para>
|
||||||
|
|
||||||
<para><guilabel>Run Script</guilabel> allows starting an arbitrary
|
<para><guilabel>Run Script</guilabel> (&LIN;) allows starting an
|
||||||
command on the result file. It will only appear for results which
|
arbitrary command on the result file. It will only appear for
|
||||||
are top-level files. See
|
results which are top-level
|
||||||
<link linkend="RCL.SEARCH.GUI.RUNSCRIPT">further</link> for a more
|
files. See <link linkend="RCL.SEARCH.GUI.RUNSCRIPT">further</link>
|
||||||
detailed description.</para>
|
for a more detailed description.</para>
|
||||||
|
|
||||||
<para>The <guilabel>Copy File Name</guilabel> and
|
<para>The <guilabel>Copy File Name</guilabel> and
|
||||||
<guilabel>Copy Url</guilabel> copy the relevant data to the
|
<guilabel>Copy Url</guilabel> copy the relevant data to the
|
||||||
@ -2203,10 +2233,10 @@ fs.inotify.max_user_watches=32768
|
|||||||
<sect2 id="RCL.SEARCH.GUI.RESTABLE">
|
<sect2 id="RCL.SEARCH.GUI.RESTABLE">
|
||||||
<title>The result table</title>
|
<title>The result table</title>
|
||||||
|
|
||||||
<para>In &RCL; 1.15 and newer, the results can be displayed in
|
<para>As an alternative to the result list, the results can also be
|
||||||
spreadsheet-like fashion. You can switch to this presentation by
|
displayed in spreadsheet-like fashion. You can switch to this
|
||||||
clicking the table-like icon in the toolbar (this is a toggle,
|
presentation by clicking the table-like icon in the toolbar (this
|
||||||
click again to restore the list).</para>
|
is a toggle, click again to restore the list).</para>
|
||||||
|
|
||||||
<para>Clicking on the column headers will allow sorting by the
|
<para>Clicking on the column headers will allow sorting by the
|
||||||
values in the column. You can click again to invert the order, and
|
values in the column. You can click again to invert the order, and
|
||||||
@ -2235,7 +2265,7 @@ fs.inotify.max_user_watches=32768
|
|||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="RCL.SEARCH.GUI.RUNSCRIPT">
|
<sect2 id="RCL.SEARCH.GUI.RUNSCRIPT">
|
||||||
<title>Running arbitrary commands on result files (1.20 and later)</title>
|
<title>&LIN;: running arbitrary commands on result files</title>
|
||||||
|
|
||||||
<para>Apart from the <guilabel>Open</guilabel> and <guilabel>Open
|
<para>Apart from the <guilabel>Open</guilabel> and <guilabel>Open
|
||||||
With</guilabel> operations, which allow starting an application on a
|
With</guilabel> operations, which allow starting an application on a
|
||||||
@ -2280,7 +2310,7 @@ fs.inotify.max_user_watches=32768
|
|||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="RCL.SEARCH.GUI.THUMBNAILS">
|
<sect2 id="RCL.SEARCH.GUI.THUMBNAILS">
|
||||||
<title>Displaying thumbnails</title>
|
<title>&LIN;: displaying thumbnails</title>
|
||||||
|
|
||||||
<para>The default format for the result list entries and the
|
<para>The default format for the result list entries and the
|
||||||
detail area of the result table display an icon for each result
|
detail area of the result table display an icon for each result
|
||||||
@ -2298,9 +2328,9 @@ fs.inotify.max_user_watches=32768
|
|||||||
your settings). Restarting the search should then display the
|
your settings). Restarting the search should then display the
|
||||||
thumbnails.</para>
|
thumbnails.</para>
|
||||||
|
|
||||||
<para>There are also <ulink url="&FAQS;ResultsThumbnails.wiki">some
|
<para>There are also <ulink url="&FAQS;ResultsThumbnails.html">some
|
||||||
pointers about thumbnail generation</ulink> on the &RCL; wiki.
|
pointers about thumbnail generation</ulink> in the &RCL;
|
||||||
</para>
|
FAQ.</para>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
@ -2320,12 +2350,9 @@ fs.inotify.max_user_watches=32768
|
|||||||
close it.</para>
|
close it.</para>
|
||||||
|
|
||||||
<para>You can close a preview tab by typing <keycap>Ctrl-W</keycap>
|
<para>You can close a preview tab by typing <keycap>Ctrl-W</keycap>
|
||||||
(<keycap>Ctrl</keycap> + <keycap>W</keycap>) in the
|
(<keycap>Ctrl</keycap> + <keycap>W</keycap>) in the window. Closing
|
||||||
window. Closing the last tab for a window will also close the
|
the last tab, or using the window manager button in the top of the
|
||||||
window.</para>
|
frame will also close the window.</para>
|
||||||
|
|
||||||
<para>Of course you can also close a preview window by using the
|
|
||||||
window manager button in the top of the frame.</para>
|
|
||||||
|
|
||||||
<para>You can display successive or previous documents from the
|
<para>You can display successive or previous documents from the
|
||||||
result list inside a preview tab by typing
|
result list inside a preview tab by typing
|
||||||
@ -2477,9 +2504,6 @@ fs.inotify.max_user_watches=32768
|
|||||||
added (as an AND filter) before performing the query if the
|
added (as an AND filter) before performing the query if the
|
||||||
button is active.</para>
|
button is active.</para>
|
||||||
|
|
||||||
<para>This feature is new in &RCL; 1.20, and will probably be
|
|
||||||
refined depending on user feedback.</para>
|
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
|
||||||
@ -2839,11 +2863,10 @@ fs.inotify.max_user_watches=32768
|
|||||||
by an entry in the <guilabel>GUI configuration</guilabel>
|
by an entry in the <guilabel>GUI configuration</guilabel>
|
||||||
dialog, and is off by default.</para>
|
dialog, and is off by default.</para>
|
||||||
|
|
||||||
<para>As of release 1.19, when a result document does have
|
<para>When a result document does have undisplayed duplicates,
|
||||||
undisplayed duplicates, a <literal>Dups</literal>
|
a <literal>Dups</literal> link will be shown with the result list
|
||||||
link will be shown with the result list entry. Clicking the
|
entry. Clicking the link will display the paths (URLs + ipaths)
|
||||||
link will display the paths (URLs + ipaths) for the duplicate
|
for the duplicate entries.</para>
|
||||||
entries.</para>
|
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
@ -2942,24 +2965,24 @@ fs.inotify.max_user_watches=32768
|
|||||||
list.</para>
|
list.</para>
|
||||||
</formalpara>
|
</formalpara>
|
||||||
|
|
||||||
<para>Phrase searches can strongly slow down a query if most of the
|
<para>Phrase searches can slow down a query if most of the
|
||||||
terms in the phrase are common. This is why the
|
terms in the phrase are common. If
|
||||||
<varname>autophrase</varname> option is off by default for &RCL;
|
the <varname>autophrase</varname> option is on, very common
|
||||||
versions before 1.17. As of version 1.17,
|
terms will be removed from the automatically constructed
|
||||||
<varname>autophrase</varname> is on by default, but very common
|
phrase. The removal threshold can be adjusted from the search
|
||||||
terms will be removed from the constructed phrase. The removal
|
preferences.</para>
|
||||||
threshold can be adjusted from the search preferences.</para>
|
|
||||||
|
|
||||||
<formalpara><title>Phrases and abbreviations</title> <para>As of
|
|
||||||
&RCL; version 1.17, dotted abbreviations like
|
|
||||||
<literal>I.B.M.</literal> are also automatically indexed as a word
|
|
||||||
without the dots: <literal>IBM</literal>. Searching for the word
|
|
||||||
inside a phrase (ie: <literal>"the IBM company"</literal>) will only
|
|
||||||
match the dotted abrreviation if you increase the phrase slack (using the
|
|
||||||
advanced search panel control, or the <literal>o</literal> query
|
|
||||||
language modifier). Literal occurences of the word will be matched
|
|
||||||
normally.</para></formalpara>
|
|
||||||
|
|
||||||
|
<formalpara><title>Phrases and abbreviations</title>
|
||||||
|
<para>Dotted abbreviations like
|
||||||
|
<literal>I.B.M.</literal> are also automatically indexed as a
|
||||||
|
word without the dots: <literal>IBM</literal>. Searching for
|
||||||
|
the word inside a phrase (ie: <literal>"the IBM
|
||||||
|
company"</literal>) will only match the dotted abrreviation
|
||||||
|
if you increase the phrase slack (using the advanced search
|
||||||
|
panel control, or the <literal>o</literal> query language
|
||||||
|
modifier). Literal occurences of the word will be matched
|
||||||
|
normally.</para>
|
||||||
|
</formalpara>
|
||||||
|
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
@ -3377,18 +3400,24 @@ fs.inotify.max_user_watches=32768
|
|||||||
<sect3 id="RCL.SEARCH.GUI.CUSTOM.RESLIST">
|
<sect3 id="RCL.SEARCH.GUI.CUSTOM.RESLIST">
|
||||||
<title>The result list format</title>
|
<title>The result list format</title>
|
||||||
|
|
||||||
<para>Newer versions of Recoll (from 1.17) normally use WebKit HTML
|
<para>Recoll normally uses a full function HTML processor to
|
||||||
widgets for the result list and the
|
display the result list and the
|
||||||
<link linkend="RCL.SEARCH.GUI.RESULTLIST.MENU.SNIPPETS">snippets window</link>
|
<link linkend="RCL.SEARCH.GUI.RESULTLIST.MENU.SNIPPETS">
|
||||||
(this may be disabled at build time).
|
snippets window</link>. Depending on the version, this may be
|
||||||
Total customisation is possible with full support for CSS and
|
based on either Qt WebKit or Qt WebEngine.
|
||||||
Javascript. Conversely, there are limits to what you can do with
|
It is then possible to completely customise the result list with full
|
||||||
the older Qt QTextBrowser, but still, it is possible to decide
|
support for CSS and Javascript.</para>
|
||||||
what data each result will contain, and how it will be
|
|
||||||
displayed.</para>
|
|
||||||
|
|
||||||
<para>The result list presentation can be exhaustively customized
|
<para>It is also possible to build &RCL; to use a simpler Qt
|
||||||
by adjusting two elements:
|
QTextBrowser widget to display the HTML, which may be necessary
|
||||||
|
if the ones above are not ported on the system, or to reduce
|
||||||
|
the application size and dependancies. There are limits to what
|
||||||
|
you can do in this case, but it is still possible to decide
|
||||||
|
what data each result will contain, and how it will be
|
||||||
|
displayed.</para>
|
||||||
|
|
||||||
|
<para>The result list presentation can be customized
|
||||||
|
by adjusting two elements:
|
||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>The paragraph format</para></listitem>
|
<listitem><para>The paragraph format</para></listitem>
|
||||||
|
|||||||
@ -35,7 +35,7 @@ text/html|epub = rclstartw %F;ignoreipath=1
|
|||||||
application/x-fsdirectory|parentopen = rclstartw %f
|
application/x-fsdirectory|parentopen = rclstartw %f
|
||||||
inode/directory|parentopen = rclstartw %f
|
inode/directory|parentopen = rclstartw %f
|
||||||
|
|
||||||
###### The following are not used at all on windows, but the types need to
|
###### THE FOLLOWING ARE NOT USED AT ALL ON WINDOWS, but the types need to
|
||||||
###### be listed for an "Open" link to appear in the result list
|
###### be listed for an "Open" link to appear in the result list
|
||||||
application/epub+zip = ebook-viewer %f
|
application/epub+zip = ebook-viewer %f
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user