No one uses Terminal. iTerm ftw ;)
I use iTerm as well but besides from splitting panes and broadcasting I don't see the benefits. Why do you use it?
Quick tip for developers who use OS X
211–220 of 406 posts
Re: Quick tip for developers who use OS X
#212Earlier 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…
Pressing ESC and then _ will insert the last argument of the last line. Repeat to go up in the history. If you go through the command history and press CTRL-o on a line it will be executed and the command on the commandline will be replaced by the next line in the history.
With a numeric prefix argument N, it grabs the Nth-from-the-end argument of the previous command, so M-3 M-. grabs the 3rd-from-last argument from the previous command.
Re: Quick tip for developers who use OS X
#213Another really useful command is the open $ open filename.png $ open . $ open -e filename.txt $ open -a Pixen filename.png The first command will open the file with the default application. Open . will open the current directory in finder, which I find very helpful. The -e flag will open the file in textedit. The -a will open the file in the given application name.
Also very useful for similar use cases is qlmanage. $ qlmanage -p
Re: Quick tip for developers who use OS X
#214Earlier 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
#215Earlier quoted context omitted.
or gnome-open. On Windows the equivalent is start (e.g. start C:\ )
I use start all the time, but also frequently curse at its stupid argument grammar and its interaction with auto-quoting on auto-completion. For example, type start C:\Doc Next, hit tab to get start "C:\Documents and Settings" Now, hit return, and watch a new command window open with title "C:\Documents and Settings". Reason? If the first argument is a quoted string, it is used as the title of the window being opened…
explorer "C:\Documents and Settings"
does what you'd expect.Re: Quick tip for developers who use OS X
#216Earlier quoted context omitted.
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.
And OS X doesn't steal Control for menu shortcuts. Control-V (literal) is not the same as Command-V (paste), Control-Z (suspend) is not the same as Command-Z (undo), and so on. X Window software used to get this right, too; Unix workstations generally had another modifier (e.g. Meta, diamond on Suns) since they knew better than to hijack keys people would type in a terminal. It's only the this-is-finally-the-year…
The blame lies with "desktop environments", not X.
X has plenty of its own problems without getting Gnome's problems heaped on top.
Edit:
> It's only the this-is-finally-the-year-of-Linux-on-the-desktop crowd slavishly imitating Microsoft's mistakes that screwed it up.
Most of the recent garbage they've cargo-culted from Apple (and common software for OS X), not Microsoft. Witness the really shitty reimplementation of Growl, the really shitty (and shamefully unmandated) window menu bar -> system menu bar consolidation.
Re: Quick tip for developers who use OS X
#217Re: Quick tip for developers who use OS X
#218Re: Quick tip for developers who use OS X
#219After 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.
Re: Quick tip for developers who use OS X
#220Earlier quoted context omitted.
And that's why C-e C-u is burned into my hands :^)
Is it any different from C-a C-k ? Both seem to stuff things into the kill ring (or whatever it's called in bash). I guess lots of people leave C-a as the default escape key for screen.