|
a/src/README |
|
b/src/README |
|
... |
|
... |
| 496 |
Indexing is performed either by the recollindex program, or by the
|
496 |
Indexing is performed either by the recollindex program, or by the
|
| 497 |
indexing thread inside the recoll program (use the File menu). Both
|
497 |
indexing thread inside the recoll program (use the File menu). Both
|
| 498 |
programs will use the RECOLL_CONFDIR variable or accept a -c confdir
|
498 |
programs will use the RECOLL_CONFDIR variable or accept a -c confdir
|
| 499 |
option to specify a non-default configuration directory.
|
499 |
option to specify a non-default configuration directory.
|
| 500 |
|
500 |
|
|
|
501 |
Reasons to use either the indexing thread or the recollindex command:
|
|
|
502 |
|
|
|
503 |
* Starting the indexing thread is more convenient, being just one click
|
|
|
504 |
away.
|
|
|
505 |
|
|
|
506 |
* The recollindex command has more options, especially the one to reset
|
|
|
507 |
the index (-z).
|
|
|
508 |
|
|
|
509 |
* The recollindex command will not take down your GUI if it crashes (a
|
|
|
510 |
rare occurrence, but who knows...)
|
|
|
511 |
|
|
|
512 |
* The recollindex command uses setpriority/nice to lower its priority
|
|
|
513 |
while indexing (it will also use ionice when this becomes more widely
|
|
|
514 |
available), the thread can't do it, else it would also slow down the
|
|
|
515 |
user/search interface.
|
|
|
516 |
|
|
|
517 |
I'll let the reader decide where my heart belongs...
|
|
|
518 |
|
| 501 |
If the recoll program finds no index when it starts, it will automatically
|
519 |
If the recoll program finds no index when it starts, it will automatically
|
| 502 |
start indexing (except if canceled).
|
520 |
start indexing (except if canceled).
|
| 503 |
|
521 |
|
| 504 |
The indexing process can be interrupted by sending an interrupt (^C,
|
522 |
The recollindex indexing process can be interrupted by sending an
|
| 505 |
SIGINT) or terminate (SIGTERM) signal. Some time may elapse before the
|
523 |
interrupt (^C, SIGINT) or terminate (SIGTERM) signal. Some time may elapse
|
| 506 |
process exits, because it needs to properly flush and close the index.
|
524 |
before the process exits, because it needs to properly flush and close the
|
|
|
525 |
index. The indexing thread can be equivalently stopped from the menu.
|
| 507 |
|
526 |
|
| 508 |
After such an interruption, the index will be somewhat inconsistent
|
527 |
After such an interruption, the index will be somewhat inconsistent
|
| 509 |
because some operations which are normally performed at the end of the
|
528 |
because some operations which are normally performed at the end of the
|
| 510 |
indexing pass will have been skipped (for exemple, the stemming and
|
529 |
indexing pass will have been skipped (for exemple, the stemming and
|
| 511 |
spelling databases will be inexistant or out of date). You just need to
|
530 |
spelling databases will be inexistant or out of date). You just need to
|
|
... |
|
... |
| 848 |
You can display successive or previous documents from the result list
|
867 |
You can display successive or previous documents from the result list
|
| 849 |
inside a preview tab by typing Shift+Down or Shift+Up (Down and Up are the
|
868 |
inside a preview tab by typing Shift+Down or Shift+Up (Down and Up are the
|
| 850 |
arrow keys).
|
869 |
arrow keys).
|
| 851 |
|
870 |
|
| 852 |
The preview tabs have an internal incremental search function. You
|
871 |
The preview tabs have an internal incremental search function. You
|
| 853 |
initiate the search either by typing a / (slash) inside the text area or
|
872 |
initiate the search either by typing a / (slash) or CTL-F inside the text
|
| 854 |
by clicking into the Search for: text field and entering the search
|
873 |
area or by clicking into the Search for: text field and entering the
|
| 855 |
string. You can then use the Next and Previous buttons to find the
|
874 |
search string. You can then use the Next and Previous buttons to find the
|
| 856 |
next/previous occurrence. You can also type F3 inside the text area to get
|
875 |
next/previous occurrence. You can also type F3 inside the text area to get
|
| 857 |
to the next occurrence.
|
876 |
to the next occurrence.
|
| 858 |
|
877 |
|
| 859 |
If you have a search string entered and you use ^Up/^Down to browse the
|
878 |
If you have a search string entered and you use ^Up/^Down to browse the
|
| 860 |
results, the search is initiated for each successive document. If the
|
879 |
results, the search is initiated for each successive document. If the
|