Show HN: Search code in GitHub repos using regular expressions
101–110 of 165 posts
Re: Show HN: Search code in GitHub repos using regular expressions
#102Re: Show HN: Search code in GitHub repos using regular expressions
#103I would say this needs a list of indexed repos and mainly an explanation of how it exactly works to be usable (how's the index build and how often it's refreshed, what types of files are being indexed, etc.). Otherwise, there's no much value in searching in an unknown data, is it? Anyway, to not only criticize, good job! It's definitely one of GitHub's missing features. And I can imagine it's not an easy job to build…
So you know exactly how Google's index works?
I think "best effort", whatever it is, is useful even if I don't know the specifics of what it captures or misses. As long as it returns useful results.
Re: Show HN: Search code in GitHub repos using regular expressions
#104api_key="[a-z0-9]+"
Ty
Re: Show HN: Search code in GitHub repos using regular expressions
#105Impressive! Really fast, full featured code search across a huge corpus. 1. How did you build the index? Did you use a GitHub dump of some sort? How often do you refresh it? 2. Is it Elasticsearch or similar or a completely custom engine? 3. What kind of RAM/CPU are you using to power it? 4. Any plans to open source the code or commercialize the technology? I could absolutely imagine paying for a private code search…
Re: Show HN: Search code in GitHub repos using regular expressions
#106Impressive! Really fast, full featured code search across a huge corpus. 1. How did you build the index? Did you use a GitHub dump of some sort? How often do you refresh it? 2. Is it Elasticsearch or similar or a completely custom engine? 3. What kind of RAM/CPU are you using to power it? 4. Any plans to open source the code or commercialize the technology? I could absolutely imagine paying for a private code search…
I'd be curious how you built the step from regex to ElasticSearch. My guess would be an n-gram (3-gram) index in ElasticSearch and then translating the regexes to that, but just curious if you built that custom or used something off-the-shelf. Love the site!
I'm pretty sure Elasticsearch supports regex search, it's just that it's horrendously slow and can blow up the system.
Re: Show HN: Search code in GitHub repos using regular expressions
#107Earlier quoted context omitted.
Sure you built app on multi 20 core machines with functionality to search hundreds of millions of lines of code almost instantaneously, but are you someone I'd drink a beer with?
This snide remark dismisses the fact that working on software does mean working with other humans, not just unemotional robots devoid of any kind of irrational ideas. Being able to “drink a beer with” (and reasonably substituting the drinking of beer for just about any other social interaction) is an important part of being able to work with someone. Unless of course you believe an office environment consisting of a…
Re: Show HN: Search code in GitHub repos using regular expressions
#108This is really cool. What are you using it for? Usage examples, debugging, etc.? I'm the CEO at Sourcegraph (universal code search for companies to use on their internal code). Our product is really optimized for searching a company's internal code right now, but soon we'll start working on offering much better search for public and open-source code as well. If you'd like to help out or just chat, please reach out! s…
Sorry, but his code search covers far more languages than yours the last time I tried yours :)
Re: Show HN: Search code in GitHub repos using regular expressions
#109This is really cool! Awesome work. I assume you've seen https://sourcegraph.com/ as well? This to me seems much clearer and a bit more intuitive (though I've only spent a little time in sourcegraph). Really really cool. Does it also search code comments?
last time I tried sourcegraph doesn't cover the language I use, so it's useless to me.
Re: Show HN: Search code in GitHub repos using regular expressions
#110A tangent, my biggest gripe with GitHub code search (within a repo) off the top of my head is the inability to blacklist directories or only search whitelisted directories. Often times I want to look up the implementation of a function, and bam, three pages of results from tests.