Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Quick tip for developers who use OS X

news.ycombinator.com

Post reply on HN
Print view View original

221–230 of 406 posts

Re: Quick tip for developers who use OS X

#221

Post by electrum »

comex wrote: post #190
randomsearch wrote: post #186

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

System Preferences -> Keyboard -> Use all F1, ... as standard function keys

Re: Quick tip for developers who use OS X

#222

Post by jakobe »

RBerenguel wrote: post #214
pavanky wrote: post #113

Earlier quoted context omitted.

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…

Also, most emacs keybindings (C-u and C-w don't, but C-k, e, a and y do, at the very least) work in all Cocoa text fields. This (in general) means you have two copy buffers: the normal, system wide Cmd-C (or X), Cmd-V and the "Cocoa wide" C-k C-y buffer

My favorite undocumented keybinding: C-t (transpose) for sloppy typers like me.

Re: Quick tip for developers who use OS X

#223

Post by IgorPartola »

Doesn't work on iTerm2, which y'all should be using anyways. Besides being infinitely more configurable, and getting tabs right, it's also much faster when you are printing a bunch of text. No idea why OS X Terminal is so slow when it comes to this, but it's actually painful to `cat` a file of more than a thousand lines.

Re: Quick tip for developers who use OS X

#224

Post by nu2ycombinator »

WildUtah wrote: post #194
tekacs wrote: post #143

Earlier quoted context omitted.

After switching to OS X after spending years using Windows and then Linux, I found it patently the case that the keyboard shortcuts in OS X are much better in both ease of use and consistency across applications. The use of the Command key and a bunch of standard shortcuts using it are particularly notable. #notsoobjective

After switching to OS X after spending years using Windows and then Linux, I found it patently the case that the keyboard shortcuts in OS X are much better than Windows and much worse than Linux in both ease of use and consistency across applications.

I agree. I like in same order Linux > OSX > windows

Re: Quick tip for developers who use OS X

#225

Post by lr »

eddieh wrote: post #116
lr wrote: post #26

Earlier quoted context omitted.

The basic Emacs key-bindings should work in all Cocoa apps. For instance, the URL bar of your web browser, while text editing in just about any editor (maybe even in Office, but I have not tired in a while), etc. Basically, anywhere you have a cursor, the basic line-editing key bindings should work. So, in practical terms, this means you have 1 + n clipboards[1]. The main global GUI clipboard (using the command key),…

defaults write -g NSTextKillRingSize -string 4

Can you shed some light on how to access those other three from the GUI (whether using the command key or some other means)?

Re: Quick tip for developers who use OS X

#226

Post by 91bananas »

rsynnott wrote: post #196
randomsearch wrote: post #186

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

IntelliJ actually provides two sets of MacOS keyboard shortcuts, for some reason. The non-default (MacOS 10.5+) is generally far better.

And the IntelliJ family of products has one of the most configurable sets of keyboard shortcut sets I've ever seen. You can literally set any feature available to any keyboard shortcut you want to, if you want paste to be 5 keys go for it, so complaining about this is senseless.

Re: Quick tip for developers who use OS X

#227

Post by bluthru »

oneeyedpigeon wrote: post #158
guelo wrote: post #118

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.

Not just keyboard shortcuts, but straight out keys (e.g. Page up / Page down)

Cmd + Arrow keys. Simple.

Re: Quick tip for developers who use OS X

#228

Post by bluthru »

petercooper wrote: post #27

A new one for me I accidentally found the other day.. If you use Spotlight to find something and then want to see the file in Finder, Cmd+click the item in the Spotlight dropdown. Edited from Cmd+shift+click due to note in child comment :-)

Cmd + R is universally "Reveal in Finder".

Re: Quick tip for developers who use OS X

#230

Post by ebzlo »

IgorPartola wrote: post #223

Doesn't work on iTerm2, which y'all should be using anyways. Besides being infinitely more configurable, and getting tabs right, it's also much faster when you are printing a bunch of text. No idea why OS X Terminal is so slow when it comes to this, but it's actually painful to `cat` a file of more than a thousand lines.

I don't cat files too often in my workflow so I guess I don't have that pain point, but I find find iTerm2 has this minor annoying latency (kind of like typing on a wireless keyboard on low battery) that ultimately drove me away from it.
Post reply on HN