Live data from Hacker News

A Whole New Code Search

github.com

21–30 of 113 posts

Re: A Whole New Code Search

#22
This is awesome, but I'm a little confused about the treatment of underscores. If you search for something like "secret_key" (teehee) it will return results for just 'secret' and just 'key' seemingly :-\ Not what I expect out of code search, but easy enough to fix if it's deemed a bug.

Re: A Whole New Code Search

#24

Is it me or does is seem like every day either Github or Stripe shipping some sweet new feature? I need to read less and code more.

It's probably the fact that they ship a lot and HN is non-platonically in love with both so new features get a lot of attention.

Re: A Whole New Code Search

#25
post #22

This is awesome, but I'm a little confused about the treatment of underscores. If you search for something like "secret_key" (teehee) it will return results for just 'secret' and just 'key' seemingly :-\ Not what I expect out of code search, but easy enough to fix if it's deemed a bug.

Surround in quotes and it won't split on the underscore.

Re: A Whole New Code Search

#26
post #18

Being able to filter by stars is great...One other filter that would be nice is days-since-lsat-commit. I guess number of stars is rough estimate of how active a repo is, but as the years go on, there will probably be more and more projects that are basically dead, yet still have a high number of stars.

Filters and sorting are definitely next on our priority. We will do another blog post when that happens.

Re: A Whole New Code Search

#27
post #22

This is awesome, but I'm a little confused about the treatment of underscores. If you search for something like "secret_key" (teehee) it will return results for just 'secret' and just 'key' seemingly :-\ Not what I expect out of code search, but easy enough to fix if it's deemed a bug.

It looks like I jumped the gun. The search itself seems fine, but the highlighter is a bit overzealous

Re: A Whole New Code Search

#29
> To ensure better relevancy, we're being conservative in what we add to the search index. Repository forks will not be searchable unless the fork has more stars than the parent repository, for example.

This has a grandfathering problem when the maintainers switch. The new active branch of development is overshadowed by the previous branch. I've had someone takeover my project, but I still have 2 years of accumulated stars from when the project was fresh. The new development has less than 1/10 the number of stars as my branch. But I guess fixing this is kind corner case might be left for v2.

Post reply on HN