Quite frequently I'll run across a previously unknown gem that keeps my head from getting too big. It doesn't matter how long you've been doing this type of work, there are things that everyone can learn. I had a situation the other day where I needed to direct the output from a process to both a file and std out. Now there are several ways one can accomplish this, whether with named pipes or a bit of creative redirects. I did a bit of research and found that there is a tool just for such an occasion - tee.
Think of a T-fitting used in plumbing and you get the idea. By piping output to tee, you can still get the output via std out but also send it to a file. It's a standard *nix command, so check out the man page for more info.
Showing posts with label cli. Show all posts
Showing posts with label cli. Show all posts
Sunday, October 20, 2013
Tuesday, August 27, 2013
How to edit multiple files automatically with vim
From time to time I may have a slew of files that I need to make bulk changes to but don't want to edit each one by hand. A quick and easy way to do this is by using vim's -c option. For those of you who are thinking "what about sed?" just hold on to your seat. The sed command is also a favorite of mine, but the mood just struck me today to talk about vim.
Almost everyone who uses Unix or Linux agrees that vim (or vi for the super-hardcore folks) is the editor of choice. Pico and nano are for sissies. Emacs, you say? I believe the old joke goes "Emacs is a great operating system but lacks a good editor." I give you a +1 if you get the joke. Kidding aside, let me get to the point of the post.
Almost everyone who uses Unix or Linux agrees that vim (or vi for the super-hardcore folks) is the editor of choice. Pico and nano are for sissies. Emacs, you say? I believe the old joke goes "Emacs is a great operating system but lacks a good editor." I give you a +1 if you get the joke. Kidding aside, let me get to the point of the post.
Subscribe to:
Posts (Atom)