After making the switch to OS X in the last couple years after living in Linux and Windows before that, I think it's objective to say that keyboard shortcuts in OS X are much worse in both ease of use and consistency across applications.
Quick tip for developers who use OS X
201–210 of 406 posts
Re: Quick tip for developers who use OS X
#202Lovely, thanks. Also, is it common knowledge that CMD+click on a URL opens that URL in your default browser? Useful for the "Running on http://127.0.0.1:5000/" messages.
Re: Quick tip for developers who use OS X
#203This is amazing. You have saved me countless seconds of frustration :-)
Re: Quick tip for developers who use OS X
#204After making the switch to OS X in the last couple years after living in Linux and Windows before that, I think it's objective to say that keyboard shortcuts in OS X are much worse in both ease of use and consistency across applications.
Re: Quick tip for developers who use OS X
#205Ctrl-x, Ctrl-e will pop open your EDITOR so you can edit the command. Saving and closing the editor brings the command back in your terminal and automatically executes it.
fc will bring up your EDITOR with the last typed command. (You can use fc -l to see a list of commands)
Re: Quick tip for developers who use OS X
#206Earlier quoted context omitted.
> Sorry, but this is laughable. Keyboard shortcuts are far more useful and consistent across applications in OS X. I don't agree with this at all. I find it baffling that a company of great designers made such bad decisions about keyboard shortcuts. Perhaps they are consistent, but they are consistently bad. Paste and match style (incredibly useful) is "alt-shift-command-v" i.e. four keys. There are plenty of other s…
> Using shortcuts in IDEs is a nightmare on most apple keyboard. e.g. Intellij, to run your program: alt-shift-f10. This is daft in itself, but it actually translates to function-alt-shift-f10 on many keyboards. Yes, you can change your settings, but then you could remap all your keys in any O/S. Miss the function key and you've just muted your volume. I really find that hard to see as anything but the IDE's fault, p…
That's fine, but the IDE is an application running on the OS X platform. OS X has these problems just as much as any platform, but the situation is made worse by their use of the function keys and by poor choices for other shortcuts.
Re: Quick tip for developers who use OS X
#207No one uses Terminal. iTerm ftw ;)
Re: Quick tip for developers who use OS X
#208Earlier quoted context omitted.
C-a : beginning line, C-e end line, alt+f forward word (unless system shortcut for file menu), alt+b back word, C-k kill line, C-b back char, C-f forward char. At least in my current setup, C-w yank and C-y paste works as well. Immensely helpful. Sometimes at+left/right does forward/ back word depending on the terminal emu. Note most of these keystrokes are valid in nano as well.
More: - C-u to kill (cut) from current location to beginning of the line - C-k to kill (cut) from current location to end of line - C-w to kill (cut) from current location to beginning of word - C-y to paste (copied / cut) lines - C-l to clear screen (I use the shit out of this) - Ctrl + shift + '-' (holding ctrl, shift, minus at the same time), for undo. That is it. EDIT: Damn it, I didn't realize I was saying a bun…
Re: Quick tip for developers who use OS X
#209Earlier quoted context omitted.
Thanks! fixed. I never noticed C-u was from cursor. I tend to use it mostly from the end of the line.
And that's why C-e C-u is burned into my hands :^)
I guess lots of people leave C-a as the default escape key for screen.
Re: Quick tip for developers who use OS X
#210After making the switch to OS X in the last couple years after living in Linux and Windows before that, I think it's objective to say that keyboard shortcuts in OS X are much worse in both ease of use and consistency across applications.
Not just keyboard shortcuts, but straight out keys (e.g. Page up / Page down)