|
a/src/README |
|
b/src/README |
|
... |
|
... |
56 |
|
56 |
|
57 |
3.1. Searching with the Qt graphical user interface
|
57 |
3.1. Searching with the Qt graphical user interface
|
58 |
|
58 |
|
59 |
3.1.1. Simple search
|
59 |
3.1.1. Simple search
|
60 |
|
60 |
|
61 |
3.1.2. The result list
|
61 |
3.1.2. The default result list
|
62 |
|
62 |
|
|
|
63 |
3.1.3. The alternate result table
|
|
|
64 |
|
63 |
3.1.3. The preview window
|
65 |
3.1.4. The preview window
|
64 |
|
66 |
|
65 |
3.1.4. Complex/advanced search
|
67 |
3.1.5. Complex/advanced search
|
66 |
|
68 |
|
67 |
3.1.5. The term explorer tool
|
69 |
3.1.6. The term explorer tool
|
68 |
|
70 |
|
69 |
3.1.6. Multiple databases
|
71 |
3.1.7. Multiple databases
|
70 |
|
72 |
|
71 |
3.1.7. Document history
|
73 |
3.1.8. Document history
|
72 |
|
74 |
|
73 |
3.1.8. Sorting search results and collapsing
|
75 |
3.1.9. Sorting search results and collapsing
|
74 |
duplicates
|
76 |
duplicates
|
75 |
|
77 |
|
76 |
3.1.9. Search tips, shortcuts
|
78 |
3.1.10. Search tips, shortcuts
|
77 |
|
79 |
|
78 |
3.1.10. Customizing the search interface
|
80 |
3.1.11. Customizing the search interface
|
79 |
|
81 |
|
80 |
3.2. Searching with the KDE KIO slave
|
82 |
3.2. Searching with the KDE KIO slave
|
81 |
|
83 |
|
82 |
3.2.1. What's this
|
84 |
3.2.1. What's this
|
83 |
|
85 |
|
|
... |
|
... |
175 |
You do not need to remember in what file or email message you stored a
|
177 |
You do not need to remember in what file or email message you stored a
|
176 |
given piece of information. You just ask for related terms, and the tool
|
178 |
given piece of information. You just ask for related terms, and the tool
|
177 |
will return a list of documents where those terms are prominent, in a
|
179 |
will return a list of documents where those terms are prominent, in a
|
178 |
similar way to Internet search engines.
|
180 |
similar way to Internet search engines.
|
179 |
|
181 |
|
180 |
Recoll tries to determine which documents are most relevant to the search
|
182 |
A search application tries to determine which documents are most relevant
|
181 |
terms you provide. Computer algorithms for determining relevance can be
|
183 |
to the search terms you provide. Computer algorithms for determining
|
182 |
very complex, and in general are inferior to the power of the human mind
|
184 |
relevance can be very complex, and in general are inferior to the power of
|
183 |
to rapidly determine relevance. The quality of relevance guessing by the
|
185 |
the human mind to rapidly determine relevance. The quality of relevance
|
184 |
search tool is probably the most important element for a search
|
186 |
guessing is probably the most important aspect when evaluating a search
|
185 |
application.
|
187 |
application.
|
186 |
|
188 |
|
187 |
In many cases, you are looking for all the forms of a word, not for a
|
189 |
In many cases, you are looking for all the forms of a word, not for a
|
188 |
specific form or spelling. These different forms may include plurals,
|
190 |
specific form or spelling. These different forms may include plurals,
|
189 |
different tenses for a verb, or terms derived from the same root or stem
|
191 |
different tenses for a verb, or terms derived from the same root or stem
|
190 |
(example: floor, floors, floored, flooring...). Recoll will by default
|
192 |
(example: floor, floors, floored, flooring...). Search applications
|
191 |
expand queries to all such related terms (words that reduce to the same
|
193 |
usually expand queries to all such related terms (words that reduce to the
|
192 |
stem). This expansion can be disabled at search time.
|
194 |
same stem) and also provide a way to disable this expansion if you are
|
|
|
195 |
actually searching for a specific form.
|
193 |
|
196 |
|
194 |
Stemming, by itself, does not accommodate for misspellings or phonetic
|
197 |
Stemming, by itself, does not accommodate for misspellings or phonetic
|
195 |
searches. Recoll supports these features through a specific tool (the term
|
198 |
searches. Recoll supports these features through a specific tool (the term
|
196 |
explorer) which will let you explore the set of index terms along
|
199 |
explorer) which will let you explore the set of index terms along
|
197 |
different modes.
|
200 |
different modes.
|
|
... |
|
... |
200 |
|
203 |
|
201 |
1.3. Recoll overview
|
204 |
1.3. Recoll overview
|
202 |
|
205 |
|
203 |
Recoll uses the Xapian information retrieval library as its storage and
|
206 |
Recoll uses the Xapian information retrieval library as its storage and
|
204 |
retrieval engine. Xapian is a very mature package using a sophisticated
|
207 |
retrieval engine. Xapian is a very mature package using a sophisticated
|
205 |
probabilistic ranking model. Recoll provides the interface to get data
|
208 |
probabilistic ranking model. Recoll provides the mechanisms and interface
|
206 |
into (indexing) and out (searching) of the system.
|
209 |
to get data into and out of the system.
|
207 |
|
210 |
|
208 |
In practice, Xapian works by remembering where terms appear in your
|
211 |
In practice, Xapian works by remembering where terms appear in your
|
209 |
document files. The acquisition process is called indexing.
|
212 |
document files. The acquisition process is called indexing.
|
210 |
|
213 |
|
211 |
The resulting index can be big (roughly the size of the original document
|
214 |
The resulting index can be big (roughly the size of the original document
|
|
... |
|
... |
237 |
giving Recoll a try, but you may want to adjust it later.
|
240 |
giving Recoll a try, but you may want to adjust it later.
|
238 |
|
241 |
|
239 |
Indexing is started automatically the first time you execute the recoll
|
242 |
Indexing is started automatically the first time you execute the recoll
|
240 |
search graphical user interface, or by executing the recollindex command.
|
243 |
search graphical user interface, or by executing the recollindex command.
|
241 |
|
244 |
|
242 |
Searches are performed inside the recoll program, which has many options
|
245 |
Searches are usually performed inside the recoll graphical user interface
|
243 |
to help you find what you are looking for.
|
246 |
(GUI) program, which has many options to help you find what you are
|
|
|
247 |
looking for. However, there are other ways to perform Recoll searches:
|
|
|
248 |
mostly a command line tool, a Python programming interface, and a KDE KIO
|
|
|
249 |
slave module.
|
244 |
|
250 |
|
245 |
----------------------------------------------------------------------
|
251 |
----------------------------------------------------------------------
|
246 |
|
252 |
|
247 |
Chapter 2. Indexing
|
253 |
Chapter 2. Indexing
|
248 |
|
254 |
|
|
... |
|
... |
261 |
executing the recollindex command. The typical usage is to have a
|
267 |
executing the recollindex command. The typical usage is to have a
|
262 |
nightly indexing run programmed into your cron file.
|
268 |
nightly indexing run programmed into your cron file.
|
263 |
|
269 |
|
264 |
* Real time indexing: indexing takes place as soon as a file is created
|
270 |
* Real time indexing: indexing takes place as soon as a file is created
|
265 |
or changed. recollindex runs as a daemon and uses a file system
|
271 |
or changed. recollindex runs as a daemon and uses a file system
|
266 |
alteration monitor such as Fam, Gamin or inotify do detect file
|
272 |
alteration monitor such as inotify, Fam or Gamin to detect file
|
267 |
changes. Monitoring a big directory tree can consume significant
|
273 |
changes.
|
268 |
system resources.
|
|
|
269 |
|
274 |
|
270 |
The choice between the two methods is mostly a matter of preference, and
|
275 |
The choice between the two methods is mostly a matter of preference, and
|
271 |
they can be combined by setting up multiple indexes (ie: use periodic
|
276 |
they can be combined by setting up multiple indexes (ie: use periodic
|
272 |
indexing on a big documentation directory, and real time indexing on a
|
277 |
indexing on a big documentation directory, and real time indexing on a
|
273 |
small home directory). Monitoring a big file system tree can consume
|
278 |
small home directory). Monitoring a big file system tree can consume
|
274 |
significant system resources, for dubious gains.
|
279 |
significant system resources.
|
275 |
|
280 |
|
276 |
|
281 |
|
277 |
|
282 |
|
278 |
Recoll knows about quite a few different document types. The parameters
|
283 |
Recoll knows about quite a few different document types. The parameters
|
279 |
for document types recognition and processing are set in configuration
|
284 |
for document types recognition and processing are set in configuration
|
|
|
285 |
files.
|
|
|
286 |
|
280 |
files Most file types, like HTML or word processing files, only hold one
|
287 |
Most file types, like HTML or word processing files, only hold one
|
281 |
document. Some file types, like mail folder files, can hold many
|
288 |
document. Some file types, like mail folder files or zip archives, can
|
282 |
individually indexed documents.
|
289 |
hold many individually indexed documents, which may in turn be themselves
|
|
|
290 |
compound ones. Such hierarchies can go quite deep, and Recoll has no
|
|
|
291 |
problem processing, for example, an ms-word document which would be an
|
|
|
292 |
attachment to an email message part of a folder file archived inside a zip
|
|
|
293 |
file...
|
283 |
|
294 |
|
284 |
Recoll indexing processes plain text, HTML, openoffice and e-mail files
|
295 |
Recoll indexing processes plain text, HTML, openoffice and e-mail files
|
285 |
internally (a few more actually).
|
296 |
internally (a few more actually).
|
286 |
|
297 |
|
287 |
Other file types (ie: postscript, pdf, ms-word, rtf ...) need external
|
298 |
Other file types (ie: postscript, pdf, ms-word, rtf ...) need external
|
|
... |
|
... |
490 |
If the recoll program finds no index when it starts, it will automatically
|
501 |
If the recoll program finds no index when it starts, it will automatically
|
491 |
start indexing (except if canceled).
|
502 |
start indexing (except if canceled).
|
492 |
|
503 |
|
493 |
The indexing process can be interrupted by sending an interrupt (^C,
|
504 |
The indexing process can be interrupted by sending an interrupt (^C,
|
494 |
SIGINT) or terminate (SIGTERM) signal. Some time may elapse before the
|
505 |
SIGINT) or terminate (SIGTERM) signal. Some time may elapse before the
|
495 |
process exits, because it needs to properly flush and close the index. The
|
506 |
process exits, because it needs to properly flush and close the index.
|
496 |
indexing will restart at the interruption point the next time (the full
|
|
|
497 |
file tree will still be traversed, but files that were indexed up to the
|
|
|
498 |
interruption and are still up to date will not need to be reindexed).
|
|
|
499 |
|
507 |
|
500 |
After such an interruption, the index will be somewhat inconsistent
|
508 |
After such an interruption, the index will be somewhat inconsistent
|
501 |
because some operations which are normally performed at the end of the
|
509 |
because some operations which are normally performed at the end of the
|
502 |
indexing pass will have been skipped (for exemple, the stemming and
|
510 |
indexing pass will have been skipped (for exemple, the stemming and
|
503 |
spelling databases will be inexistant or out of date). You just need to
|
511 |
spelling databases will be inexistant or out of date). You just need to
|
504 |
restart indexing at a later time to restore consistency.
|
512 |
restart indexing at a later time to restore consistency. The indexing will
|
|
|
513 |
restart at the interruption point (the full file tree will be traversed,
|
|
|
514 |
but files that were indexed up to the interruption and are still up to
|
|
|
515 |
date will not need to be reindexed).
|
|
|
516 |
|
|
|
517 |
recollindex has a number of other options which are described in its man
|
|
|
518 |
page.
|
505 |
|
519 |
|
506 |
----------------------------------------------------------------------
|
520 |
----------------------------------------------------------------------
|
507 |
|
521 |
|
508 |
2.5.2. Using cron to automate indexing
|
522 |
2.5.2. Using cron to automate indexing
|
509 |
|
523 |
|
|
... |
|
... |
588 |
|
602 |
|
589 |
* Simple search (the default, on the main screen) has a single entry
|
603 |
* Simple search (the default, on the main screen) has a single entry
|
590 |
field where you can enter multiple words.
|
604 |
field where you can enter multiple words.
|
591 |
|
605 |
|
592 |
* Advanced search (a panel accessed through the Tools menu or the
|
606 |
* Advanced search (a panel accessed through the Tools menu or the
|
593 |
toolbox bar icon) shas multiple entry fields, which you may use to
|
607 |
toolbox bar icon) has multiple entry fields, which you may use to
|
594 |
build a logical condition, with additional filtering on file type and
|
608 |
build a logical condition, with additional filtering on file type and
|
595 |
location in the file system.
|
609 |
location in the file system.
|
596 |
|
610 |
|
597 |
In most cases, you can enter the terms as you think them, even if they
|
611 |
In most cases, you can enter the terms as you think them, even if they
|
598 |
contain embedded punctuation or other non-textual characters. For exemple,
|
612 |
contain embedded punctuation or other non-textual characters. For exemple,
|
|
... |
|
... |
616 |
|
630 |
|
617 |
3. Enter search term(s) in the text field at the top of the window.
|
631 |
3. Enter search term(s) in the text field at the top of the window.
|
618 |
|
632 |
|
619 |
4. Click the Search button or hit the Enter key to start the search.
|
633 |
4. Click the Search button or hit the Enter key to start the search.
|
620 |
|
634 |
|
621 |
The initial default search mode is All terms. This will look for documents
|
635 |
The initial default search mode is Query language. Without special
|
622 |
containing all of the search terms (the ones with more terms will get
|
636 |
directives, this will look for documents containing all of the search
|
623 |
better scores). Any term will search for documents where at least one of
|
637 |
terms (the ones with more terms will get better scores), just like the All
|
624 |
the terms appear.
|
638 |
terms mode which will ignore such directives. Any term will search for
|
|
|
639 |
documents where at least one of the terms appear.
|
|
|
640 |
|
|
|
641 |
The Query Language features are described in a separate section.
|
625 |
|
642 |
|
626 |
File name will specifically look for file names. The entry will be split
|
643 |
File name will specifically look for file names. The entry will be split
|
627 |
at white space characters, and each pattern will be separately expanded.
|
644 |
at white space characters, and each fragment will be separately expanded,
|
|
|
645 |
then the search will be for file names matching all fragments (this is new
|
|
|
646 |
in 1.15, older releases did an OR of the whole thing which did not make
|
|
|
647 |
sense). Things to know:
|
|
|
648 |
|
|
|
649 |
* The search is case- and accent-insensitive.
|
|
|
650 |
|
|
|
651 |
* Fragments without any wild card character and not capitalized will be
|
|
|
652 |
prepended and appended with '*' (ie: etc -> *etc*, but Etc -> etc). Of
|
|
|
653 |
course it does not make sense to have multiple fragments if one of
|
|
|
654 |
them is capitalized (as this one will require an exact match).
|
|
|
655 |
|
628 |
If you want to search for a pattern including white space, use double
|
656 |
* If you want to search for a pattern including white space, use double
|
|
|
657 |
quotes (ie: "admin note*").
|
|
|
658 |
|
|
|
659 |
* If you have a big index (many files), excessively generic fragments
|
|
|
660 |
may result in inefficient searches.
|
|
|
661 |
|
|
|
662 |
* As an example, inst recoll would match recollinstall.in (and quite a
|
|
|
663 |
few others...).
|
|
|
664 |
|
629 |
quotes. The point of having a separate file name search is that wild card
|
665 |
The point of having a separate file name search is that wild card
|
630 |
expansion can be performed more efficiently on a relatively small subset
|
666 |
expansion can be performed more efficiently on a relatively small subset
|
631 |
of the index.
|
667 |
of the index (allowing wild cards on the left of terms without excessive
|
632 |
|
668 |
penality).
|
633 |
The fourth entry (Query Language) is described in its own section.
|
|
|
634 |
|
669 |
|
635 |
All search modes allow wildcards inside terms (*, ?, []). You may want to
|
670 |
All search modes allow wildcards inside terms (*, ?, []). You may want to
|
636 |
have a look at the section about wildcards for more information about
|
671 |
have a look at the section about wildcards for more information about
|
637 |
this.
|
672 |
this.
|
638 |
|
673 |
|
|
... |
|
... |
665 |
|
700 |
|
666 |
You can use the Tools / Advanced search dialog for more complex searches.
|
701 |
You can use the Tools / Advanced search dialog for more complex searches.
|
667 |
|
702 |
|
668 |
----------------------------------------------------------------------
|
703 |
----------------------------------------------------------------------
|
669 |
|
704 |
|
670 |
3.1.2. The result list
|
705 |
3.1.2. The default result list
|
671 |
|
706 |
|
672 |
After starting a search, a list of results will instantly be displayed in
|
707 |
After starting a search, a list of results will instantly be displayed in
|
673 |
the main list window.
|
708 |
the main list window.
|
674 |
|
709 |
|
675 |
By default, the document list is presented in order of relevance (how well
|
710 |
By default, the document list is presented in order of relevance (how well
|
676 |
the system estimates that the document matches the query). You can specify
|
711 |
the system estimates that the document matches the query). You can sort
|
677 |
a different ordering by using the Tools / Sort parameters dialog.
|
712 |
the result by ascending or descending date by using the vertical arrows in
|
|
|
713 |
the toolbar (the old sort tool is gone after release 1.15, because the new
|
|
|
714 |
result table has much better capability).
|
678 |
|
715 |
|
679 |
Clicking on the Preview link for an entry will open an internal preview
|
716 |
Clicking on the Preview link for an entry will open an internal preview
|
680 |
window for the document. Further Preview clicks for the same search will
|
717 |
window for the document. Further Preview clicks for the same search will
|
681 |
open tabs in the existing preview window. You can use Shift+Click to force
|
718 |
open tabs in the existing preview window. You can use Shift+Click to force
|
682 |
the creation of another preview window, which may be useful to view the
|
719 |
the creation of another preview window, which may be useful to view the
|
|
... |
|
... |
761 |
this case. In other cases, the Open option makes sense, for exemple to
|
798 |
this case. In other cases, the Open option makes sense, for exemple to
|
762 |
start a chm viewer on the parent document for a help page.
|
799 |
start a chm viewer on the parent document for a help page.
|
763 |
|
800 |
|
764 |
----------------------------------------------------------------------
|
801 |
----------------------------------------------------------------------
|
765 |
|
802 |
|
|
|
803 |
3.1.3. The alternate result table
|
|
|
804 |
|
|
|
805 |
In Recoll 1.15 and newer, the results can now be shown in a
|
|
|
806 |
spreadsheet-like display. You can switch to this presentation by clicking
|
|
|
807 |
the table-like icon in the toolbar (this is a toggle, click again to
|
|
|
808 |
restore the list).
|
|
|
809 |
|
|
|
810 |
Clicking on the column headers will allow sorting by the values in the
|
|
|
811 |
column. You can click again to invert the order, and use the header
|
|
|
812 |
right-click menu to reset sorting to the default relevance order.
|
|
|
813 |
|
|
|
814 |
Both the list and the table display the same underlying results. The sort
|
|
|
815 |
order set from the table is still active if you switch back to the list
|
|
|
816 |
mode. You can click twice on a date sort arrow to reset it from there.
|
|
|
817 |
|
|
|
818 |
The header right-click menu allows adding or deleting columns. The columns
|
|
|
819 |
can be resized, and their order can be changed (by dragging). All the
|
|
|
820 |
changes are recorded when you quit recoll
|
|
|
821 |
|
|
|
822 |
Hovering over a table row will update the detail area at the bottom of the
|
|
|
823 |
window with the corresponding values. You can click the row to freeze the
|
|
|
824 |
display. The bottom area is equivalent to a classical result list
|
|
|
825 |
paragraph, with links for starting a preview or a native application, and
|
|
|
826 |
an equivalent right-click menu.
|
|
|
827 |
|
|
|
828 |
----------------------------------------------------------------------
|
|
|
829 |
|
766 |
3.1.3. The preview window
|
830 |
3.1.4. The preview window
|
767 |
|
831 |
|
768 |
The preview window opens when you first click a Preview link inside the
|
832 |
The preview window opens when you first click a Preview link inside the
|
769 |
result list.
|
833 |
result list.
|
770 |
|
834 |
|
771 |
Subsequent preview requests for a given search open new tabs in the
|
835 |
Subsequent preview requests for a given search open new tabs in the
|
|
... |
|
... |
805 |
You can print the current preview window contents by typing ^P (Ctrl + P)
|
869 |
You can print the current preview window contents by typing ^P (Ctrl + P)
|
806 |
in the window text.
|
870 |
in the window text.
|
807 |
|
871 |
|
808 |
----------------------------------------------------------------------
|
872 |
----------------------------------------------------------------------
|
809 |
|
873 |
|
810 |
3.1.4. Complex/advanced search
|
874 |
3.1.5. Complex/advanced search
|
811 |
|
875 |
|
812 |
The advanced search dialog helps you build more complex queries without
|
876 |
The advanced search dialog helps you build more complex queries without
|
813 |
memorizing the search language constructs. It can be opened through the
|
877 |
memorizing the search language constructs. It can be opened through the
|
814 |
Tools menu or through the main toolbar.
|
878 |
Tools menu or through the main toolbar.
|
815 |
|
879 |
|
|
... |
|
... |
872 |
Click on the Show query details link at the top of the result page to see
|
936 |
Click on the Show query details link at the top of the result page to see
|
873 |
the query expansion.
|
937 |
the query expansion.
|
874 |
|
938 |
|
875 |
----------------------------------------------------------------------
|
939 |
----------------------------------------------------------------------
|
876 |
|
940 |
|
877 |
3.1.5. The term explorer tool
|
941 |
3.1.6. The term explorer tool
|
878 |
|
942 |
|
879 |
Recoll automatically manages the expansion of search terms to their
|
943 |
Recoll automatically manages the expansion of search terms to their
|
880 |
derivatives (ie: plural/singular, verb inflections). But there are other
|
944 |
derivatives (ie: plural/singular, verb inflections). But there are other
|
881 |
cases where the exact search term is not known. For example, you may not
|
945 |
cases where the exact search term is not known. For example, you may not
|
882 |
remember the exact spelling, or only know the beginning of the name.
|
946 |
remember the exact spelling, or only know the beginning of the name.
|
|
... |
|
... |
927 |
simple search entry field. You can also cut/paste between the result list
|
991 |
simple search entry field. You can also cut/paste between the result list
|
928 |
and any entry field (the end of lines will be taken care of).
|
992 |
and any entry field (the end of lines will be taken care of).
|
929 |
|
993 |
|
930 |
----------------------------------------------------------------------
|
994 |
----------------------------------------------------------------------
|
931 |
|
995 |
|
932 |
3.1.6. Multiple databases
|
996 |
3.1.7. Multiple databases
|
933 |
|
997 |
|
934 |
Multiple Recoll databases or indexes can be created by using several
|
998 |
Multiple Recoll databases or indexes can be created by using several
|
935 |
configuration directories which are usually set to index different areas
|
999 |
configuration directories which are usually set to index different areas
|
936 |
of the file system. A specific index can be selected for updating or
|
1000 |
of the file system. A specific index can be selected for updating or
|
937 |
searching, using the RECOLL_CONFDIR environment variable or the -c option
|
1001 |
searching, using the RECOLL_CONFDIR environment variable or the -c option
|
|
... |
|
... |
972 |
with the directory filter in advanced search, but multiple indexes will
|
1036 |
with the directory filter in advanced search, but multiple indexes will
|
973 |
have much better performance and may be worth the trouble.
|
1037 |
have much better performance and may be worth the trouble.
|
974 |
|
1038 |
|
975 |
----------------------------------------------------------------------
|
1039 |
----------------------------------------------------------------------
|
976 |
|
1040 |
|
977 |
3.1.7. Document history
|
1041 |
3.1.8. Document history
|
978 |
|
1042 |
|
979 |
Documents that you actually view (with the internal preview or an external
|
1043 |
Documents that you actually view (with the internal preview or an external
|
980 |
tool) are entered into the document history, which is remembered.
|
1044 |
tool) are entered into the document history, which is remembered.
|
981 |
|
1045 |
|
982 |
You can display the history list by using the Tools/Doc History menu
|
1046 |
You can display the history list by using the Tools/Doc History menu
|
|
... |
|
... |
985 |
You can erase the document history by using the Erase document history
|
1049 |
You can erase the document history by using the Erase document history
|
986 |
entry in the File menu.
|
1050 |
entry in the File menu.
|
987 |
|
1051 |
|
988 |
----------------------------------------------------------------------
|
1052 |
----------------------------------------------------------------------
|
989 |
|
1053 |
|
990 |
3.1.8. Sorting search results and collapsing duplicates
|
1054 |
3.1.9. Sorting search results and collapsing duplicates
|
991 |
|
1055 |
|
992 |
The documents in a result list are normally sorted in order of relevance.
|
1056 |
The documents in a result list are normally sorted in order of relevance.
|
993 |
It is possible to specify different sort parameters by using the Sort
|
1057 |
It is possible to specify different sort parameters by using the Sort
|
994 |
parameters dialog (located in the Tools menu).
|
1058 |
parameters dialog (located in the Tools menu).
|
995 |
|
1059 |
|
|
... |
|
... |
1012 |
not be a duplicate of the text only). Duplicates hiding is controlled by
|
1076 |
not be a duplicate of the text only). Duplicates hiding is controlled by
|
1013 |
an entry in the Query configuration dialog, and is off by default.
|
1077 |
an entry in the Query configuration dialog, and is off by default.
|
1014 |
|
1078 |
|
1015 |
----------------------------------------------------------------------
|
1079 |
----------------------------------------------------------------------
|
1016 |
|
1080 |
|
1017 |
3.1.9. Search tips, shortcuts
|
1081 |
3.1.10. Search tips, shortcuts
|
1018 |
|
1082 |
|
1019 |
3.1.9.1. Terms and search expansion
|
1083 |
3.1.10.1. Terms and search expansion
|
1020 |
|
1084 |
|
1021 |
Term completion. Typing Esc Space in the simple search entry field while
|
1085 |
Term completion. Typing Esc Space in the simple search entry field while
|
1022 |
entering a word will either complete the current word if its beginning
|
1086 |
entering a word will either complete the current word if its beginning
|
1023 |
matches a unique term in the index, or open a window to propose a list of
|
1087 |
matches a unique term in the index, or open a window to propose a list of
|
1024 |
completions.
|
1088 |
completions.
|
|
... |
|
... |
1053 |
file name search which will only look for file names, and may be faster
|
1117 |
file name search which will only look for file names, and may be faster
|
1054 |
than the generic search especially when using wildcards.
|
1118 |
than the generic search especially when using wildcards.
|
1055 |
|
1119 |
|
1056 |
----------------------------------------------------------------------
|
1120 |
----------------------------------------------------------------------
|
1057 |
|
1121 |
|
1058 |
3.1.9.2. Working with phrases and proximity
|
1122 |
3.1.10.2. Working with phrases and proximity
|
1059 |
|
1123 |
|
1060 |
Phrases and Proximity searches. A phrase can be looked for by enclosing it
|
1124 |
Phrases and Proximity searches. A phrase can be looked for by enclosing it
|
1061 |
in double quotes. Example: "user manual" will look only for occurrences of
|
1125 |
in double quotes. Example: "user manual" will look only for occurrences of
|
1062 |
user immediately followed by manual. You can use the This phrase field of
|
1126 |
user immediately followed by manual. You can use the This phrase field of
|
1063 |
the advanced search dialog to the same effect. Phrases can be entered
|
1127 |
the advanced search dialog to the same effect. Phrases can be entered
|
|
... |
|
... |
1072 |
documents where either virtual or reality or both appear, but those which
|
1136 |
documents where either virtual or reality or both appear, but those which
|
1073 |
contain virtual reality should appear sooner in the list.
|
1137 |
contain virtual reality should appear sooner in the list.
|
1074 |
|
1138 |
|
1075 |
----------------------------------------------------------------------
|
1139 |
----------------------------------------------------------------------
|
1076 |
|
1140 |
|
1077 |
3.1.9.3. Others
|
1141 |
3.1.10.3. Others
|
1078 |
|
1142 |
|
1079 |
Using fields. You can use the query language and field specifications to
|
1143 |
Using fields. You can use the query language and field specifications to
|
1080 |
only search certain parts of documents. This can be especially helpful
|
1144 |
only search certain parts of documents. This can be especially helpful
|
1081 |
with email, for example only searching emails from a specific originator:
|
1145 |
with email, for example only searching emails from a specific originator:
|
1082 |
search tips from:helpfulgui
|
1146 |
search tips from:helpfulgui
|
|
... |
|
... |
1107 |
|
1171 |
|
1108 |
Quitting. Entering ^Q almost anywhere will close the application.
|
1172 |
Quitting. Entering ^Q almost anywhere will close the application.
|
1109 |
|
1173 |
|
1110 |
----------------------------------------------------------------------
|
1174 |
----------------------------------------------------------------------
|
1111 |
|
1175 |
|
1112 |
3.1.10. Customizing the search interface
|
1176 |
3.1.11. Customizing the search interface
|
1113 |
|
1177 |
|
1114 |
You can customize some aspects of the search interface by using the Query
|
1178 |
You can customize some aspects of the search interface by using the Query
|
1115 |
configuration entry in the Preferences menu.
|
1179 |
configuration entry in the Preferences menu.
|
1116 |
|
1180 |
|
1117 |
There are several tabs in the dialog, dealing with the interface itself,
|
1181 |
There are several tabs in the dialog, dealing with the interface itself,
|
|
... |
|
... |
1224 |
alternative indexer may also need to implement a way of purging the index
|
1288 |
alternative indexer may also need to implement a way of purging the index
|
1225 |
from stale data,
|
1289 |
from stale data,
|
1226 |
|
1290 |
|
1227 |
----------------------------------------------------------------------
|
1291 |
----------------------------------------------------------------------
|
1228 |
|
1292 |
|
1229 |
3.1.10.1. The result list paragraph format
|
1293 |
3.1.11.1. The result list paragraph format
|
1230 |
|
1294 |
|
1231 |
The presentation of each result inside the result list can be customized
|
1295 |
The presentation of each result inside the result list can be customized
|
1232 |
by setting the result list paragraph format inside the User Interface tab
|
1296 |
by setting the result list paragraph format inside the User Interface tab
|
1233 |
of the Query configuration.
|
1297 |
of the Query configuration.
|
1234 |
|
1298 |
|
|
... |
|
... |
1576 |
----------------------------------------------------------------------
|
1640 |
----------------------------------------------------------------------
|
1577 |
|
1641 |
|
1578 |
3.5.1. Hotkeying recoll
|
1642 |
3.5.1. Hotkeying recoll
|
1579 |
|
1643 |
|
1580 |
It is surprisingly convenient to be able to show or hide the Recoll GUI
|
1644 |
It is surprisingly convenient to be able to show or hide the Recoll GUI
|
1581 |
with a single keystroke. Recoll comes with a small python script, based on
|
1645 |
with a single keystroke. Recoll comes with a small Python script, based on
|
1582 |
the libwnck window manager interface library, which will allow you to do
|
1646 |
the libwnck window manager interface library, which will allow you to do
|
1583 |
just this. The detailed instructions are on this wiki page.
|
1647 |
just this. The detailed instructions are on this wiki page.
|
1584 |
|
1648 |
|
1585 |
----------------------------------------------------------------------
|
1649 |
----------------------------------------------------------------------
|
1586 |
|
1650 |
|
|
... |
|
... |
2188 |
module. icalendar is not needed for newer versions, which use internal
|
2252 |
module. icalendar is not needed for newer versions, which use internal
|
2189 |
code.
|
2253 |
code.
|
2190 |
|
2254 |
|
2191 |
* Zip archives need Python (and the standard zipfile module).
|
2255 |
* Zip archives need Python (and the standard zipfile module).
|
2192 |
|
2256 |
|
|
|
2257 |
* Midi karaoke files need Python and the Midi module
|
|
|
2258 |
|
2193 |
Text, HTML, mail folders, and Scribus files are processed internally. Lyx
|
2259 |
Text, HTML, mail folders, and Scribus files are processed internally. Lyx
|
2194 |
is used to index Lyx files. Many filters need iconv and the standard sed
|
2260 |
is used to index Lyx files. Many filters need iconv and the standard sed
|
2195 |
and awk.
|
2261 |
and awk.
|
2196 |
|
2262 |
|
2197 |
----------------------------------------------------------------------
|
2263 |
----------------------------------------------------------------------
|