At 16:05 28.02.2006, James Bailie wrote:
Glenn Dawson wrote:
At 02:30 AM 2/28/2006, Kristian Vaaf wrote:
Hello.
I am just curious why the files I generate with script(1) output in CR/LF
forcing me to run dos2unix on them everytime?
Script just captures the output of your shell, and
On Friday 03 March 2006 04:52, Kristian Vaaf wrote:
At 16:05 28.02.2006, James Bailie wrote:
Glenn Dawson wrote:
At 02:30 AM 2/28/2006, Kristian Vaaf wrote:
Hello.
I am just curious why the files I generate with script(1) output
in CR/LF forcing me to run dos2unix on them
Kristian Vaaf wrote:
The last question though,
don't you find it the least bit stupid?
Sure is. One is probably not going to use script(1) very often
with programs which take the terminal out of canonical mode, so
it makes sense to normalize line terminators when writing to the
log file.
James Bailie wrote:
It would not be difficult to add an option to screen(1) to tell
it to normalize line terminators in the log file...
I had some time on my hands, so I made a patch to add a c
option to script(1) to collapse CRNL into NL in the log file. If
you're interested, it's sitting
Hello.
I am just curious why the files I generate with script(1) output in CR/LF
forcing me to run dos2unix on them everytime?
Isn't this a bit stupid?
Thanks,
Vaaf
___
freebsd-questions@freebsd.org mailing list
At 02:30 AM 2/28/2006, Kristian Vaaf wrote:
Hello.
I am just curious why the files I generate with script(1) output in CR/LF
forcing me to run dos2unix on them everytime?
Script just captures the output of your shell, and your shell has to
send crlf in order to get the cursor back to the
Glenn Dawson wrote:
At 02:30 AM 2/28/2006, Kristian Vaaf wrote:
Hello.
I am just curious why the files I generate with script(1) output in
CR/LF
forcing me to run dos2unix on them everytime?
Script just captures the output of your shell, and your shell has to
send crlf in order to
