Earlier quoted context omitted.
The fact that you can’t search for file names is the funniest part to me.
You can but only in the repo itself not on a site wide scale.
Show HN: Search code in GitHub repos using regular expressions
81–90 of 165 posts
Re: Show HN: Search code in GitHub repos using regular expressions
#82I do not have a great example to try on my phone, but are results deduplicated? That's my big peeve with GitHub search is getting 5 pages of the same forked repo.
Re: Show HN: Search code in GitHub repos using regular expressions
#83Do you index the default branch of every repo? Or do you just index the master branch?
Re: Show HN: Search code in GitHub repos using regular expressions
#84^(. )'(. )'(. )$ I got a tooltip say: Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data Update:: Oh ^(. )"(. )"(. )$ works and fast.
Re: Show HN: Search code in GitHub repos using regular expressions
#85Re: Show HN: Search code in GitHub repos using regular expressions
#86Earlier quoted context omitted.
You can but only in the repo itself not on a site wide scale.
Really? I searched for `filename:home.nix` (which brought me to https://github.com/search?utf8=%E2%9C%93&q=filename%3Ahome.n... ). That seems site-wide to me, unless I'm misunderstanding you.
Re: Show HN: Search code in GitHub repos using regular expressions
#87Re: Show HN: Search code in GitHub repos using regular expressions
#88Next post from danfox - “how to get 3 job offers in 3 hours”. Already has been publicly contacted by: - GitHub CTO - SerpApi CEO - SourceGraph CEO Search is hot right now!
Actually, It would more be like: "How I failed at 3 interviews, despite being directly contacted by execs."
Re: Show HN: Search code in GitHub repos using regular expressions
#89Why regex still exists? It is unintuitive, requires mastering an obscure syntax, it is very hard to debug, and very difficult to explain to others how it works. It feels like we are trying to write intermediate code by ourselves, while we should have a human readable language that generates regex.
However, Eggexes are a thin, mostly-syntactic layer over regexes. You still have to understand the regex engine to use them. If this sounds useless to you because you don’t currently understand any flavor of regex or parsing, I encourage you not to give up on learning regexes. (https://www.regular-expressions.info/ was how I learned; it’s a great tutorial.) Text-parsing engines, including regex engines, are a powerful concept that can be used in many situations, and I think it’s worth spending the effort learning them until, to paraphrase another commenter, regexes become the human-readable language you were searching for. Or Eggexes, at least.
Re: Show HN: Search code in GitHub repos using regular expressions
#90Earlier quoted context omitted.
Actually, It would more be like: "How I failed at 3 interviews, despite being directly contacted by execs."
Couldn't whiteboard a solution without the temp variable.