Quite a few releases have gone out up until now and I've had some feedback through the issues links but I'd be interested to recieve general reviews of how crgrep rates in terms of usefulness, quality and features? Or just post me your suggestions or comments - good, bad or otherwise.
I'm craving some feedback guys, help me out!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does it works with regex (not only wildcards)? For example if I want to find two words foo|bar
maybe you plan to give a posibility to <search-pattern> add input from file?
what if I need to search in multiple files?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks gymit (very annoying I didn't see auto-notification you had posted a question, not ignoring you!). Yes I've got more elaborate patterns on my list such as multiple patterns 'a|b', and from a file, and also --exclude / --include for resource filtering.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Craig,
Would it be possible to have deb package for crgrep ? I have installed Tesseract but im quite confused on what should be done next to install on ubuntu.
Regards,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Culverine, it's not meant to be bundled or packaged with standalone external tools included. The idea is that all these third party packages I make use of (NLP, OCR etc) need to be installed independently of crgrep because their datasets and software are typically quite large while the default crgrep distro is small given that it's a simple CLI tool and users can decide what extra tools they wish to install and use with it.
I've made every attempt to provide complete documentation, have you tried following details in both docs/FILE_GREP.txt and INSTALL.txt for installing OCR support? If you post the exact problem you're having I might suggest a solution. Better to edit 'bin/crgrep' shell script and add 'set -x' at the top and include it's output so I can see exactly what's its doing (check for senstive data in your output first).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Quite a few releases have gone out up until now and I've had some feedback through the issues links but I'd be interested to recieve general reviews of how crgrep rates in terms of usefulness, quality and features? Or just post me your suggestions or comments - good, bad or otherwise.
I'm craving some feedback guys, help me out!!
hi,
very good tool.
Does it works with regex (not only wildcards)? For example if I want to find two words foo|bar
maybe you plan to give a posibility to <search-pattern> add input from file?
what if I need to search in multiple files?
Thanks gymit (very annoying I didn't see auto-notification you had posted a question, not ignoring you!). Yes I've got more elaborate patterns on my list such as multiple patterns 'a|b', and from a file, and also --exclude / --include for resource filtering.
Hello Craig,
Would it be possible to have deb package for crgrep ? I have installed Tesseract but im quite confused on what should be done next to install on ubuntu.
Regards,
Hi Culverine, it's not meant to be bundled or packaged with standalone external tools included. The idea is that all these third party packages I make use of (NLP, OCR etc) need to be installed independently of crgrep because their datasets and software are typically quite large while the default crgrep distro is small given that it's a simple CLI tool and users can decide what extra tools they wish to install and use with it.
I've made every attempt to provide complete documentation, have you tried following details in both docs/FILE_GREP.txt and INSTALL.txt for installing OCR support? If you post the exact problem you're having I might suggest a solution. Better to edit 'bin/crgrep' shell script and add 'set -x' at the top and include it's output so I can see exactly what's its doing (check for senstive data in your output first).