OS X Command Line Utilities
131–140 of 243 posts
Re: OS X Command Line Utilities
#132It seems odd to have open /Applications/Safari.app/ as an example, when open -a safari does the same thing.
Re: OS X Command Line Utilities
#133This was supposed to be few lines of remarks. It expanded quickly in relation with my enthusiasm for this topic. I've been investing some time in the command line on my Mac. I am moving from a dilettante going to the shell on a per-need basis to a more seasoned terminal native. It pays off handesomely! It's hard to convey how nice it to have to have a keyboard-based unified environment instead of a series of disjoine…
> - Install iterm2. The main reason to use it >instead of the default Terminal application is that It just works©. What's wrong with the default Terminal application? I use it daily and have been for close to a decade. I never found myself wishing it did anything than what it already does. > -Use tmux. Meh. For most people screen works just as well. Perhaps more importantly, you can rely on screen being available pre…
Re: OS X Command Line Utilities
#134export CLICOLOR=1
export LSCOLORS=GxFxCxDxBxegedabagaced
I thought that was one of the most amazing things when I used a linux system, but OS X is black and white by default.
Re: OS X Command Line Utilities
#135This was supposed to be few lines of remarks. It expanded quickly in relation with my enthusiasm for this topic. I've been investing some time in the command line on my Mac. I am moving from a dilettante going to the shell on a per-need basis to a more seasoned terminal native. It pays off handesomely! It's hard to convey how nice it to have to have a keyboard-based unified environment instead of a series of disjoine…
It's called jump/mark. I aliased j to jump and added tab completion to zsh and it's made all the difference.
Usage
Mark .
Marks the current directory to be in the jump list.
Jump
Jumps to that directory.
Zsh is a much nicer shell than bash too and there are no glaring incompatibility issues I have seen in daily usage.
Re: OS X Command Line Utilities
#136My favorite command is 'say'. You can do all kinds of silly voices. Try this out: say hello -v Good
I used `say` to read out the cricket scores from a screenscraping bot whilst the TV (which was the radio at the time) was in use for games. Not quite TMS but it had a certain charm.
Re: OS X Command Line Utilities
#137This was supposed to be few lines of remarks. It expanded quickly in relation with my enthusiasm for this topic. I've been investing some time in the command line on my Mac. I am moving from a dilettante going to the shell on a per-need basis to a more seasoned terminal native. It pays off handesomely! It's hard to convey how nice it to have to have a keyboard-based unified environment instead of a series of disjoine…
Look into getting Emacs in one of its native OS X incarnations rather than using it in the terminal. Emacs is going to have a lot more options for colors (font locking is the Emacs-speak, I think) in its own app than when it's boxed into a terminal. You also get support for multiple "frames" (windows); Vim can't do this at all and I still miss that from Emacs. I use Linux rather than OS X but if you are parked in Ema…
Re: OS X Command Line Utilities
#138My favorite command is 'say'. You can do all kinds of silly voices. Try this out: say hello -v Good
Just mucking around, came up with this: wc -l
gshuf /usr/share/dict/words | head -n 10 | awk '{print $1 "! "}' | sayRe: OS X Command Line Utilities
#139Earlier quoted context omitted.
Look into getting Emacs in one of its native OS X incarnations rather than using it in the terminal. Emacs is going to have a lot more options for colors (font locking is the Emacs-speak, I think) in its own app than when it's boxed into a terminal. You also get support for multiple "frames" (windows); Vim can't do this at all and I still miss that from Emacs. I use Linux rather than OS X but if you are parked in Ema…
Vim can absolutely do multiple "frames". They're called splits.
Re: OS X Command Line Utilities
#140What always surprises me is that so many don't know or use the directory stack commands, pushd and popd. I'll admit I was also ignorant of them until something like 2005, but once I learned of them I switched and never looked back. Now I can't see someone write or type "cd" without a little bit of a cringe.
When i first found out about pushd and popd, i loved them, and used them all the time. These days, i never use them. The way i work now is that i have a bunch of terminal tabs open. Each tab has a shell which pretty much just sits in a single directory. If i need to switch to a different directory, i switch tabs. A nice effect of this is that each tab builds up a recent shell history specific to the directory it sits…
Easy enough to change in system preferences, though. And with using Vim NERDtree, or some other directory plugin, it makes sitting at the top level directory of your project, with multiple projects in multiple tabs, pretty easy.
Are you on Mac? If so, have you done anything to make tab-switching easier/faster? I'm interested because I only recently set mine up this way, and am always open to more efficient methods.