Live data from Hacker News

Quick tip for developers who use OS X

news.ycombinator.com

281–290 of 406 posts

Re: Quick tip for developers who use OS X

#281

Earlier quoted context omitted.

OK here's one. I press command-option esc to Force Quit an app. But how do I then close the Force Quit window (which stays on top of all other windows) without the mouse? Thanks to anyone who's figured this out.

Command-W

Or Esc.

Re: Quick tip for developers who use OS X

#282
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.

Sorry, but this is laughable. Keyboard shortcuts are far more useful and consistent across applications in OS X. I'm failing to understand how you could form this opinion...which shortcuts / programs don't meet your expectations? I guess I can sum this up by saying OS X has an additional modifier key than Windows, so you basically have 33% more power right out of the gate. The "Windows Key" is nearly useless.

I mostly agree with you, with the exception of Final Cut Pro... Its keyboard layout to OSX's is like Finnish to Samoan.

Re: Quick tip for developers who use OS X

#283
post #201
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.

I wouldn't call it objective, but I've been using osx exclusively for 3 years now and shortcuts still come slower than windows, primarily because on windows I can press control and any key using just one hand by using my pinky for the control key.

Remap capslock to control.

Re: Quick tip for developers who use OS X

#285
post #234

Earlier quoted context omitted.

Did you try Powershell?

I've tried powershell, but it still seems to launch in that same ancient command window they've used for years with the exceptionally strange copy & paste characteristics (seriously, why can't it copy wrapped multi-line wrapped commands without inserting newlines when I paste?). Also why does it want to scroll past the end of the buffer? Ugh. Plus why are all the built-in commands like 20 characters long and camel ca…

The built-in commands are aliased, which is probably the most infuriating part; clearly they thought it necessary to name the listing functionality 'Get-ChildItem' and refer to it by that in all the documentation so as not to blow our pretty little sysadmin minds when we discover ls/dir could list more than directories now. Who knew Microsoft was fractal in nature?

Anyway, if you have to suffer PowerShell at least do it in the ISE.

Re: Quick tip for developers who use OS X

#286

Sucks that it doesn't work in iTerm2.

For some reason when I try this in iTerm2, it jumps to a different command in my history. No idea what's going on there...

I saw this too... It looks like when you opt-click above the current line, it jumps back in your history by... the same number of lines as your cursor is above the current line? Sort of an unusual feature. Nevertheless, when I'm careful to actually click on the current line, it works as described.

Re: Quick tip for developers who use OS X

#287
post #52

Bash, running in your terminal, understands both the Emacs and the Vi commands. By default is Emacs, so you can C-a (control-a) for beginning of line, C-p to go back in command line history, or C-r to search it. I prefer the Vi mode, though. Add to your .bashrc set -o vi Then you can press escape to go from input mode to normal mode; there k will take you to the previous line in command line history, j to the next li…

To get

  [NORMAL]
on the right side of the terminal like in Vim, I put this in my .zshrc file:

  function zle-line-init zle-keymap-select {
      VIM_PROMPT="%{$fg_bold[yellow]%} [% %{$reset_color%}NORMAL%{$fg_bold[yellow]%}]%  %{$reset_color%}"
      RPS1="${${KEYMAP/vicmd/$VIM_PROMPT}/(main|viins)/} $EPS1"
      zle reset-prompt
  }

Re: Quick tip for developers who use OS X

#288

Earlier quoted context omitted.

> "Paste and match formatting" shouldn't be necessary for most programs, and isn't a platform standard. If I copy and paste from a web browser, sometimes I want the formatting and sometimes I don't. It's not an usual case. Places where I use this shortcut include Word, Evernote and Mail. It's just not a sensible key combination.

>If I copy and paste from a web browser, sometimes I want the formatting The default SHOULD be to lose the formatting of the original and to use the font/style that is in Word. I would think that 99% of time anyone is copying and pasting into Word this is their intended result. I agree with the other post, it is incredibly stupid to have it keep formatting from the original by default.

Yes. This is a feature where you wonder if whoever though of that shortcut ever used a word processor. Such a bad design choice for such a common action.

Re: Quick tip for developers who use OS X

#289
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.

Besides totally disagreeing with you; are you aware that you can always bind you own shortcuts to any menu item via System Preferences -> Keyboard -> Shortcuts ?
Post reply on HN