Live data from Hacker News

Introducing the Command Bar

github.com

61–70 of 101 posts

Re: Introducing the Command Bar

#61

Earlier quoted context omitted.

+1 for vim keybindings. I noticed JIRA actually has these the other day (the only thing I like about it).

I'd like to counter here that I prefer that sites don't assign vim bindings, or at least allow me to disable them. The reason being that I make extensive use of the vimium Chrome plugin (similar to pentadactyl on Firefox), which maps common vim keys to useful browser shortcuts (j/k to scroll, shift-j/k to switch tabs, f to enable a "type to click links" mode, etc). On 99% of the websites I use, I almost never need to…

I'm not trying to troll, but frankly, I don't understand why people who want to use advanced extensions like Vimium/Pentadactyl opt for Chrome and its crippling extension API.

With Pentadactyl, what you describe just isn't a problem: the extension captures the keys and prevents websites from screwing that up, unless you want to access them, in which case you just press C-z to enable 'Pass Through' mode.

Re: Introducing the Command Bar

#62
post #11

Earlier quoted context omitted.

No! Ctrl-[1-9], switches between 1-8 and last tabs in Chrome. I know that Alt-[1-9] works too, and is even more cross-browser (works in Firefox), but I still prefer Ctrl. I'm not sure why, though.

Ctrl-[1-9] is the hotkey for Firefox (not Alt-[1-9]).

Actually, it depends on the platform, it's Ctrl on Windows and Alt on Linux (and Command on Mac).

Re: Introducing the Command Bar

#63
post #2

Playing 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…

In multiple places on github, as a vim user, I occasionally instinctively hit escape. Github sometimes closes a comment box and I lose all the stuff I had been typing. It's an unfortunate UI issue for me (and probably others).

Just use VIM proper; after all, It's All Text! https://addons.mozilla.org/en-US/firefox/addon/its-all-text/

(alternatively, use Pentadactyl and press C-i when the focus is on a text box)

Re: Introducing the Command Bar

#64

Earlier quoted context omitted.

I'd like to counter here that I prefer that sites don't assign vim bindings, or at least allow me to disable them. The reason being that I make extensive use of the vimium Chrome plugin (similar to pentadactyl on Firefox), which maps common vim keys to useful browser shortcuts (j/k to scroll, shift-j/k to switch tabs, f to enable a "type to click links" mode, etc). On 99% of the websites I use, I almost never need to…

I'm not trying to troll, but frankly, I don't understand why people who want to use advanced extensions like Vimium/Pentadactyl opt for Chrome and its crippling extension API. With Pentadactyl, what you describe just isn't a problem: the extension captures the keys and prevents websites from screwing that up, unless you want to access them, in which case you just press C-z to enable 'Pass Through' mode.

Pentadactyl requires Firefox and Firefox is a memory eating pig.

Re: Introducing the Command Bar

#65
post #2

Playing 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…

Try Vimium. converts entire browser to vim bindings

http://vimium.github.com/

Re: Introducing the Command Bar

#66
post #46

Wow, 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 know for one of the games I work on, the chat-commands/command-line interface is one of the most popular user interface features for power users. And the main reason is what you suggest about navigating and clicking. Admittedly, in a game you might "/equip meat helmet" or "/use mmj" a lot more frequently than you will friend someone on github, but it's a similar concept.

For a universal search bar I've been wanting to implement a chat bot style thing for issuing actions:

   /find search term
Which is actually the same as not including "/find"... it acts like a search box when not told otherwise.

   /goto inbox
   /goto home
Navigation to common pages.

   /me is dancing
That one updates your status.

   /me slaps [user] with a trout
Is the equivalent of a Facebook poke I guess.

Re: Introducing the Command Bar

#67

Earlier quoted context omitted.

I'd like to counter here that I prefer that sites don't assign vim bindings, or at least allow me to disable them. The reason being that I make extensive use of the vimium Chrome plugin (similar to pentadactyl on Firefox), which maps common vim keys to useful browser shortcuts (j/k to scroll, shift-j/k to switch tabs, f to enable a "type to click links" mode, etc). On 99% of the websites I use, I almost never need to…

I'm not trying to troll, but frankly, I don't understand why people who want to use advanced extensions like Vimium/Pentadactyl opt for Chrome and its crippling extension API. With Pentadactyl, what you describe just isn't a problem: the extension captures the keys and prevents websites from screwing that up, unless you want to access them, in which case you just press C-z to enable 'Pass Through' mode.

I didn't take your comment as a troll -- I even considered mentioning that problem in my post. The trust and power that Firefox gives towards extension authors is certainly a strong point in its design for "power users" (letting, for example, Firefox adblockers prevent the ads from even being loaded, while Chrome adblockers can only hide the display elements). The thing is, though, no one browser is perfect; Firefox lacks Chrome's process isolation, support for the latest Flash plugin on Linux, I prefer Chrome's visual design and user interface, etc -- the point being that I prefer Chrome/Chromium for certain reasons external to extension capabilities, and I'm not willing to switch back to Firefox just to get my vim hotkeys to work on Google Reader.

I realize it's not fair to expect web app developers to adapt to my (or anyone else's) custom browser configuration, but in this particular case, they're adding vim hotkeys primarily as a convenience to fellow vim users, not as a defining feature of their site. Given that, I think they should be aware that there is a subset of those vim users who are negatively affected by their kindness.

Humorously, Chrome just completely crashed while I was writing this (running on the latest Quantal beta), prompting me to remove a bit I wrote about Chrome being more stable than Firefox due to its process isolation. I have a hunch that the fault lied in the Flash plugin, however, which doesn't seem to be terribly stable on Linux. I've never had a browser-wide crash on Chromium in the past, but not being able to watch certain Youtube videos and missing the convenience of Chrome's PDF plugin prompted me switch to it. Not sure I made the right decision.

Re: Introducing the Command Bar

#68

Earlier quoted context omitted.

I'm not trying to troll, but frankly, I don't understand why people who want to use advanced extensions like Vimium/Pentadactyl opt for Chrome and its crippling extension API. With Pentadactyl, what you describe just isn't a problem: the extension captures the keys and prevents websites from screwing that up, unless you want to access them, in which case you just press C-z to enable 'Pass Through' mode.

Pentadactyl requires Firefox and Firefox is a memory eating pig.

Thankfully, not here (it's using 300MB of Resident Memory after being open for days). On what OS are you?

Re: Introducing the Command Bar

#69

Well, 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.

That's no reason to stop imagining other UI modes. I found the idea of websites feeding browsers with completions for the omnibar and accepting direct actions as REST quite interesting.

Imagine you want to follow xyz on Twitter, you could open the full page, use the search, pop the pop-up and click follow, or you could type tw tab follow xyz enter in the omnibar.

Re: Introducing the Command Bar

#70
I want this for every website, and for most of the desktop apps I use. Typing, for me, is so much easier than finding menu items and clicking on them. Imagine Photoshop with an autocompleting command line instead of a maze of menus. I could work so much faster.
Post reply on HN