5 ms·

Really? On Mac I've found it very consistent that alt+left/right jumps forward/back one word, alt+up/down jumps to start/end of paragraph, cmd+left/right jumps

by m12k 9y ago

Really? On Mac I've found it very consistent that alt+left/right jumps forward/back one word, alt+up/down jumps to start/end of paragraph, cmd+left/right jumps to end of line, cmd+up/down goes to beginning or end of all text (like Home/End). This is the case for me in Sublime, RubyMine, Xcode, Firefox, Chrome and any other app I've used in recent years - which apps are you using that don't follow these conventions?

colanderman 9y ago
In Chrome on OS X it differs whether I'm casting my screen or not, whether Ctrl+←/→ move me to the start/end of a line or document. (I can't figure out how to move to the end of a line while Chromecasting. It is beyond frustrating.)
- tlb 9y ago
  ^e for end-of-line, ^a for beginning-of-line. ^p for previous-line, ^n for next-line. All far more ergonomic than arrow keys.
  - seanp2k2 9y ago
    http://www.bigsmoke.us/readline/shortcuts http://www.bigsmoke.us/readline/shortcuts they're just GNU Readline shortcuts of copies of those :)
  - seanp2k2 9y ago
    Esp when you remap caps lock to control as the Lord intended it to be.
EricLemieux 9y ago
iterm2, at least that's what it defaulted to for me, uses ctrl + direction instead of alt + direction.
afarrell 9y ago
iTerm2 doesn't EDIT: Unless you do this: https://apple.stackexchange.com/questions/136928/using-alt-cmd-right-left-arrow-in-iterm https://apple.stackexchange.com/questions/136928/using-alt-c...
- egwynn 9y ago
  Terminals are, generally, expected to behave like terminals, which brings along a host of legacy compatibility things about how keyboards used to work over the past 40 years. Not saying that’s an excuse, or that they shouldn’t try to, but balancing “sane modern defaults” vs “sane-ish defaults from the 70s that everyone’s used to now” is hard. EDIT: To elaborate a little… Terminals pre-date arrow keys, which is partly why there are lots of default “movement” keybindings that don’t use them (ctrl-a, ctrl-e, ctrl-b, ctrl-f, ctrl-n, ctrl-p, etc.).

by m12k 9y ago

colanderman 9y ago

In Chrome on OS X it differs whether I'm casting my screen or not, whether Ctrl+←/→ move me to the start/end of a line or document. (I can't figure out how to move to the end of a line while Chromecasting. It is beyond frustrating.)

tlb 9y ago
^e for end-of-line, ^a for beginning-of-line. ^p for previous-line, ^n for next-line. All far more ergonomic than arrow keys.
- seanp2k2 9y ago
  http://www.bigsmoke.us/readline/shortcuts http://www.bigsmoke.us/readline/shortcuts they're just GNU Readline shortcuts of copies of those :)
- seanp2k2 9y ago
  Esp when you remap caps lock to control as the Lord intended it to be.

EricLemieux 9y ago

iterm2, at least that's what it defaulted to for me, uses ctrl + direction instead of alt + direction.

afarrell 9y ago

iTerm2 doesn't EDIT: Unless you do this: https://apple.stackexchange.com/questions/136928/using-alt-cmd-right-left-arrow-in-iterm https://apple.stackexchange.com/questions/136928/using-alt-c...

egwynn 9y ago
Terminals are, generally, expected to behave like terminals, which brings along a host of legacy compatibility things about how keyboards used to work over the past 40 years. Not saying that’s an excuse, or that they shouldn’t try to, but balancing “sane modern defaults” vs “sane-ish defaults from the 70s that everyone’s used to now” is hard. EDIT: To elaborate a little… Terminals pre-date arrow keys, which is partly why there are lots of default “movement” keybindings that don’t use them (ctrl-a, ctrl-e, ctrl-b, ctrl-f, ctrl-n, ctrl-p, etc.).