Custom search issues #43
Comments
oh and
|
maybe the second issue could be solved by changing lines in
and then search tools need to be modified to return the whole path. This works for me, but might break native search (and some others). |
I almost removed this feature cause felt too dangerous. May you share your custom search? Why do you need one? |
I'm using recoll as my search tool. Basically I'm using your tool to show a bunch of PDFs, and recoll can search the content of the PDFs. Recoll can search inside tons of documents - it just happens to be mostly PDF in my case. The external search tool is a major reason I'm using your project. There is a recoll web ui but its gone a little stale - and frankly it's not as pretty. I have this all as a docker image. Its working but still needs some work. https://github.com/bkanuka/recoll-explorer-docker |
That's a nice tool! Can you give me an example of how:
Thanks! |
recoll comes with a cli tool My
Then my custom search command is just:
Output is the full path from
That said, I wrote |
BTW this is working with the changes I noted above and my PR. You may have a better way though. Let me know what you're thinking! edit: nope, something not working perfectly. I think it has to do with whitespace. I'm getting an error from explorer: |
First part of this I figured out on my own. In
lib/searc/index.js
line 55 needs to be:because
options
isconfig.search
and sooptions.search
is undefined and you never get to use a custom command!Second part I can't figure out. I have a dummy search program that prints "./output.pdf" to console rigth now but I can't get it to work. Error is:
Path must be a string. Received [ '/output.pdf' ]
. Full output belowSorry if the line numbers don't up - I added some debug lines on my own trying to figure this out. I'm new to node.js so...thanks for being helpful and patient with me!
Side note: I'm working on a docker image that integrates your explorer with recoll search so that I can search inside files. I'll put it up on github soon.
The text was updated successfully, but these errors were encountered: