-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unite CodeSearch #3
Comments
I'm sorry for late reply. I had never heard it and I tried it. It seems indexed code search tool and the behavior is similar to grep or ctags. I think it is better to use with Unite-grep. |
I would like to integrate Google Code Search into my Unite workflow. Like :Unite file file_rec everything and Google Code Search. With Grep that's not possible. |
I looked again. It gives you the output from a binary, and in same way Everything does the same (filtering the contents). So could it be possible to wrap Csearch.exe into your plugin, I guess? |
Everything is based on a NTFS feature (USN journal) which basically acts like and index on inode changes (knows every file touched created on system) so is not possible to extend it. |
Thanks for sharing this awesome plugin with us! Great job.
I saw that Google Code Search works the same way as Everything, it uses an index too. But for inline code, not for file name. You can check out it on here. The manual is included in the download, and it offers a cmd path.
I was wondering if it's possible to wrap the functionality into a Unite source, same as Unite Everything?
The text was updated successfully, but these errors were encountered: