begin quoting Carl Lowenstein as of Tue, Mar 28, 2006 at 10:34:07AM -0800: [snip - using script for interactive session recording] > Note that script(1) saves a lot of things that you might not really > want to see, like all the fancy cursor-movement stuff that goes into > making up your Bash prompt, and of course the carriage-return > characters at the end of the line, and any backspaces that might have > been put in during command-line editing. But a quick pass with the > editor of your choice will clean this up.
Setting your prompt to something dead simple helps the cleanup process tremendously. Using ! and ^ instead of arrowing around helps as well. And if you have to correct too many typos... ^U and starting over really can save a lot of effort. > One of these days, if I use script more often, I will get around to > writing a sed script to clean up the output. :%s/^V^M//g in vi(m) does the line-endings just fine, but the line-editing stuff seemed more complicated than what I could see fitting in a sed script. But then, I only do simple things in sed scripts... and afraid I'm going to do poorly what's already been done in a CPAN module. :-) -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
