On 01/29/15 18:16, openda...@hushmail.com wrote:
Hi Marc / Otto!
On 29. januar 2015 at 7:07 PM, "Marc Espie" <es...@nerim.net> wrote:
And it shouldn't ! script(1) is often used for debugging
purposes, and that "noise" becomes paramount to figuring
out what's going on.
Thanks, I had no idea. Would it be possible though to mention some use cases
where the noise is necessary?
Many thanks!
O.D.
When you want to know exactly what a process is spewing out. CR's
and all.
Really, script(1) says that it catches everything printed onto the
terminal in the first line.
I've used script to find out escape sequences from programs, to
figure out how cursor movement worked. I've also caught programs
with many gigs of output, so I could look for weird little things
it said (not my code, but I had to figure it out). Having the line
breaks in there let me see each individual line which was useful.
Lastly if you don't want to see them make an alias of cat/more
with output going through tr(1) and you'll never see them again.
That's the beauty of this world--you have little tools to make
stuff happen the way you want.
--STeve Andre'
