I've been using helm-projectile's helm-projectile-ag in emacs (on prelude) a lot lately. It's very nice to have live filtering while you type a query, and the ability to search for symbol at point.
rking's ag.vim provides a UI to Silver Searcher in vim, it is effectively similar to this, plus it's right in your next editor! https://github.com/rking/ag.vim
That said Hound looks like a nice tool. I'm giving it a try.
This has basically replaced ack for me. I was dubious of a web -based search tool when Kelly first sent an email about it, but after trying it a couple of times, I abandoned ack. It being linkable is extra icing on the cake for me.
If you're experimenting, use `git config --global credential.helper 'store'` to set git to store your credentials in a plain-text file. Then (if you're on GitHub), generate a personal access token (https://help.github.com/articles/creating-an-access-token-fo...), and then use that as the password - once you've entered it once, it should be stored and not prompted for again.
Do you mean outside of an IDE, because as the sibling comment notes: both IntelliJ and other inferior editors do this.
If you mean from the command-line, then, yes, it likely take some use of mvn dependency:tree and javap invocations (or unzip for the deps that ship -sources.jar artifacts)
It is a pity this didn't get much traction when it was posted! I was loosing some hair trying to deploy OpenGrok and I think I am going to give Hound a try instead.
Well, as far as J2EE apps go, OpenGrok is a breeze to deploy, but it's still a PITA.
OpenGrok indexing is very very slow. It used to take 10+ minutes on my codebase and my machine. When I switched to Russ Cox' codesearch, indexing was so fast that I just put it in my .profile. And I didn't have to run Tomcat on my laptop.
I haven't tried this tool yet, but if it works by the same principles as codesearch I'd expect it to be very fast.
The biggest difference is that Hound uses an inverted index to support regular expression searches. This is a technique borrowed from the original Google Code Search. The details are discussed on Russ Cox's site (http://swtch.com/~rsc/regexp/regexp4.html). With this technique, you can generally avoid even opening the vast majority of the files you are "grepping" (the number obviously depends on the pattern). To give you a sense, I just searched for a particular method name in several repositories totally several 100k of files and the search only had to open and search 9 files.
Looks like there isn't any. But after a bit of code spelunking I found this: https://github.com/etsy/Hound/blob/master/src/hound/api/api.... (it basically tells the service how to interact with the outside world using mux - which, as a small aside, one of the more popular http routing packages in Go. But I wander...)
So it looks like wiring the default backend onto a custom frontend shouldn't be that difficult. Unless you want extra features ofcourse, because then it seems you need to learn a bit of Go ;)
I use cscope extensively, but it serves a quite different purpose from grep. It's good at jumping to definitions and references for a specific symbol (although C++ support is miserable; AFAIK the other tools you listed are similar), but grep's required if you need more structure/context, if you're searching comments or don't know exactly what something is called, etc.
I've gotten used to GLOBAL. Basically a nicer version of cscope, from my memories of it. Some of that could just be a better emacs mode, though.
It is funny, because I can not deny that there are more powerful ways of doing searches on source code. However, I think there is a beautiful thing about code that is easily greppable.
Dang, is there any design reason for not listing only a single news for submissions with both http:// and https:// in the URL? I basically posted that again because IMHO the original post didn't get attention that Hound deserved (since it was posted in a shitty hour of the day), but this is a cheap trick to bypass the submit form I know.
The duplicate detector is left weak like that on purpose to allow for reposts of good stories that didn't get significant attention the first time they were posted. This is described in the FAQ: https://news.ycombinator.com/newsfaq.html.
We treated this one as a dupe because it's pretty hard to argue that the previous post didn't get significant attention at 46 points. On the other hand, the interest in this project (including the repost) looks organic and genuine, so as an experiment, we've unburied it and merged yesterday's comments into this thread.
[0] https://github.com/ggreer/the_silver_searcher