On Mon, Jun 08, 2009 at 11:13:00PM -0700, Norbert Papke wrote:
On June 8, 2009, Daniel Underwood wrote:
Further suppose that after running the command, I decide I want to
save the output to a text file, so I can analyze the results outside
of the terminal. What can I do? Well, I can do a
On June 8, 2009, Daniel Underwood wrote:
Further suppose that after running the command, I decide I want to
save the output to a text file, so I can analyze the results outside
of the terminal. What can I do? Well, I can do a traditional
copy-and-paste, or I could re-enter the previous
On Mon, Jun 8, 2009 at 10:44 PM, Daniel Underwood djuatde...@gmail.comwrote:
OK, this is perhaps a weird question, capable of being very confusing.
So let's take a for instance.
Suppose I run something like the Linux command fdupes on a directory
with many large files. This operation will
On Jun 8, 2009, at 8:48 PM, Lord Of Hyphens wrote:
On Mon, Jun 8, 2009 at 10:44 PM, Daniel Underwood djuatde...@gmail.com
wrote:
$ fdupes -r ~/directorywithlotsoflargefiles
(.lots of output, woops, should have sent to a text file!)
$ output[1] ~/textfile.txt
Hopefully this has
In the last episode (Jun 08), Steven Schlansker said:
On Jun 8, 2009, at 8:48 PM, Lord Of Hyphens wrote:
On Mon, Jun 8, 2009 at 10:44 PM, Daniel Underwood djuatde...@gmail.com
wrote:
$ fdupes -r ~/directorywithlotsoflargefiles
(.lots of output, woops, should have sent to a text
Daniel Underwood wrote:
I read up on tee, but I'm not sure it does the trick. From what I
understand, tee simply enters a mode where what you type gets put into
a text file.
What actually happens is when you pipe it to tee, it shows up in a text
file and on the screen. That lets you make
