Sorry forgot to answer to these in the previous email:

David Baron writes:
 > The * problem does not explain a non-filename problem--I hope the
 > correspondent did the same tests and logfiles and sent them as I
 > suggested to him.

Excessive quoting may also affect non-filename searches, and there is also
the capital issue, if the user is not careful about it, search results will
be different (because of stemming/no stemming).

 > Ultimately, I should probably take snippets from recoll's sources and do
 > it directly to xapian rather than the fork, but this runner is meant to
 > be simple and small. Performance in such an interactive environment is
 > not an issue.

Going directly to Xapian would be quite complex. Recoll does quite a lot of
processing before asking stuff from Xapian, I would really not recommand
this (except if you want to rewrite recoll :) )

Actually I think that your approach is quite reasonable. Another
possibility would be to either use the Python API or the C++ interface
which is just below this: as it's use to implement the Python and PHP Apis
and also the recollq program, it's quite stable, and simple (take a look at
recollq). The main problem going this way would be build issues, as Recoll
is not currently structured to export a library (which is why the Python
approach would really be the most natural, except that your program is C++
I guess).

Cheers,

JF



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to