>On Feb 2 11:13, Rachel Trent wrote: >> I have a seemingly simple problem that I either haven't found the >> answer to or I didn't understand the answer when I saw it. I presume >> I'm not describing it with the correct terminology... >> >> Short version: >> In layman's terms, the Cygwin window cuts off at the top, and I'd like >> to know if the output that's been cut off is forever lost or if I >> might be able to save it to a file or view it some other way. >> >> Long version: >> Within a larger script, I copied over a thousand files from one server >> to another using the following command: >> cp -R -n -p -v "$package" "$destination" | tee -a "$destination"/copiedfiles.txt
In the future, to capture the errors as well: cp -R -n -p -v "$package" "$destination" 2>&1 | tee -a "$destination"/copiedfiles.txt >> >> However, several files failed to copy due to permissions issues/etc, >> and the copiedfiles.txt file does not include the error information. >> The onscreen output does include this information (due to using the -v >> verbose option), however I can only scroll up to see about 300 lines >> of information (surprise! I wasn't expecting this). My question is: >> can I somehow access the output that was cut off? > >This is not a Cygwin problem. The scrollback buffer is provided by the >underying Windows console. You can change that in the console window >properties dialog. > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple