Cool toy, but how about letting users just search for code in a repo properly?
Introducing the Command Bar
51–60 of 101 posts
Re: Introducing the Command Bar
#52Playing with this for a few minutes: * I wish it had vim keybindings (ie, hit esc, then use hjkl to navigate) * It gives me the option to follow myself. (Bug?) * I like how I can learn commands via the autocomplete bar (issue, branch, graph, etc) * I like how the autocomplete bar refreshes after I have control-tabbed away and back. Too many autocompletes lose this behavior * Searching in a repository username/repo do…
Re vim bindings, this tweet[1] by John Nunemaker makes it seem unlikely. (Not actually sure how serious he is, but it's a funny tweet - and I say that as a Vim user.) [1] http://twitter.com/jnunemaker/status/247800799625887744
Perhaps a satisfactory solution for everyone would be to make "esc" defocus the input field? Github already has a "command mode" by default, and focus on the textbox can serve as the mode switching mechanism. The "s" key would then replace "i" in vim.
Re: Introducing the Command Bar
#53I put together a little admin command line that you could bring up with the ~ key that looks like this: http://i.imgur.com/mq7ko.png?1
It is built for asp.net but you could easily apply the same concept somewhere else. More info if anyone is interested: http://lukencode.com/2011/12/11/netbashan-alternative-to-end...
Re: Introducing the Command Bar
#54Cool toy, but how about letting users just search for code in a repo properly?
+1. The search results for this could merge in commits and be a really valuable way to figure out whats going on in a well factored, modular codebase where things can be spread out in many different tangled folders. Something like 'ack for github' would be fantastic.
Re: Introducing the Command Bar
#55Wow, a command-line interface to a website is something I never thought I'd see. My first reaction was that it's a step backwards because the usual benefits of a command line aren't present here (you're usually already using your mouse, commands can't be piped, no shell scripts to run things in sequence)... But I'm intigued -- maybe it's a possible step forwards? The implementation is very well done. I suppose maybe…
i'm not trying to be a jerk, i swear, but Google (especially since the autocompletion and nigh-instant results) would count, i think.
Re: Introducing the Command Bar
#56Note, Chrome junkies, the Firefox awesome bar already does most of these :)
Re: Introducing the Command Bar
#57Cool toy, but how about letting users just search for code in a repo properly?
For a site like GitHub, I would imagine this is a huge engineering effort to do right. For instance, in a plain vanilla code search facility, how would you expire results efficiently when the text can change from minute to minute (to seconds, to even less)?
Re: Introducing the Command Bar
#58Well, we already have a command bar at the top of the window. What about these commands?
http://github.com/username
http://github.com/username/follow
http://github.com/username/unfollow
http://github.com/me/dashboard
http://github.com/me/notifications
http://github.com/username/reponame/search/term
http://github.com/username/reponame/branchnameRe: Introducing the Command Bar
#59Cool toy, but how about letting users just search for code in a repo properly?
For a site like GitHub, I would imagine this is a huge engineering effort to do right. For instance, in a plain vanilla code search facility, how would you expire results efficiently when the text can change from minute to minute (to seconds, to even less)?
Super efficient search would be great and idea, but slightly delayed searching is perfectly acceptable imo. Especially because I am not necessarily looking for extremely up-to-date changes.
Re: Introducing the Command Bar
#60Well, we already have a command bar at the top of the window. What about these commands? http://github.com/username http://github.com/username/follow http://github.com/username/unfollow http://github.com/me/dashboard http://github.com/me/notifications http://github.com/username/reponame/search/term http://github.com/username/reponame/branchname
What is your point? REST is meant to make it easy for machines to talk to each other.