brownplt / ZZZ-captain-teach

Set sail for Learning Island! Deprecated and no longer maintained
5 stars 1 forks source link

Ctrl-up/down conflict with native OS X shortcuts #3

Closed samuela closed 11 years ago

samuela commented 11 years ago

For those of us with computers of the fruit persuasion, it's not possible to move through the interaction history with the Ctrl-up and Ctrl-down keyboard shortcuts. A slightly modified shortcut (Ctrl-Alt-up/down, for example) would work on both Macs and PCs.

jpolitz commented 11 years ago

How about Ctrl-p Ctrl-n for up/down? That matches some editors/shells, so it will pleasantly surprise some.

On Sun, Sep 8, 2013 at 1:50 PM, vhsiao notifications@github.com wrote:

For now you could try disabling your keyboard shortcuts via the control panel. Most of the newer OS X laptops have a mission control/launchpad button on the keyboard anyway.

— Reply to this email directly or view it on GitHubhttps://github.com/brownplt/captain-teach/issues/3#issuecomment-24025583 .

jpolitz commented 11 years ago

Never mind, Ctrl-N is unstoppable in Chrome, it always opens a new window ( http://stackoverflow.com/questions/7295508/javascript-capture-browser-shortcuts-ctrlt-n-w ).

I'll do Ctrl-Alt-Up and Ctrl-Alt-Down, which will amusingly conflict with some Gnome defaults in a similar way (move workspace up/down). So there should be something for everyone.

On Sun, Sep 8, 2013 at 1:59 PM, Joe Gibbs Politz joe@cs.brown.edu wrote:

How about Ctrl-p Ctrl-n for up/down? That matches some editors/shells, so it will pleasantly surprise some.

On Sun, Sep 8, 2013 at 1:50 PM, vhsiao notifications@github.com wrote:

For now you could try disabling your keyboard shortcuts via the control panel. Most of the newer OS X laptops have a mission control/launchpad button on the keyboard anyway.

— Reply to this email directly or view it on GitHubhttps://github.com/brownplt/captain-teach/issues/3#issuecomment-24025583 .

jpolitz commented 11 years ago

I pushed this to the main site. Closed by db081a3bc5ea9f2174e9a54e077886ebf2200227, sorry for the delay.

samuela commented 11 years ago

Great, thanks!