This solves one of my largest annoyances when using Github as a Rails developer, namely, "Oh yay, time to walk five levels up and four levels down to find the place in the code of this gem where the function caused in the line causing the problem is actually defined."<p>Previously if I had to do it more than once I would copy the gem to disk, import to Netbeans, and then use Netbean's equivalent function. (Which I use so frequently during development I should really map it to, I dunno, tab.)
So, a lot of small files create inconvenience and then one need a tool to navigate the mess?<p>You don't need that if you put everything in OneBigFile. Mine is 24KLOC. <a href="http://simplijs.com/OneBigFileFormat" rel="nofollow">http://simplijs.com/OneBigFileFormat</a><p>Modern editors can handle big files.<p>BTW: I'm still looking for an editor that could open multiple files in a single buffer/window.
Awesome.<p>It's speedy too. I fired up Chrome Inspector and it looks like it works by Ajaxing in a full list of files in your repo the first time you hit "t", then doing the actual searching in the browser. Here's the URL it loaded for one of my projects:<p><a href="https://github.com/simonw/bugle_project/tree-list/1c7793bf60a1652c3f35eb547b2d03e14188dc36" rel="nofollow">https://github.com/simonw/bugle_project/tree-list/1c7793bf60...</a>
Perhaps I'm special but I've never wanted to search for a filename in a github repository. Fulltext search on the other hand, that's a feature I have missed often.
For emacs, I use the following:<p>1. I create a TAGS file with exuberant <i>ctags</i> (not the default etags - note that both have a file called etags, to find out which one you have, issue `etags -v`.).<p>2. Use the <i>ido-find-file-in-tag-files</i> mentioned here: <a href="http://www.emacswiki.org/emacs/TextMate" rel="nofollow">http://www.emacswiki.org/emacs/TextMate</a> Answer 3, mapped to `C-x C-g`.<p>This might be a bad choice due to C-g, but it's close to C-x C-f, so I prefer that.
That's a great feature for bigger projects.<p>I would love to see a similar grep-type feature, where I can quickly search through the files in a repository for text. (Yes, I know there's advanced search, but that's so disruptive to my code reading.)
Wow, really well implemented! Normally I git clone, open the repo in vim, then use ack.<p>Github also has very good keyboard shortcuts in the Issues section. Gmail shortcut users will feel right at home.