I've used putty and found its scroll buffer history logging to a file useful. If I need to save the output of a command that will generate 30K+ lines, opening a log file makes saving this output smart and easy. I know I can bump up the size of the scroll buffer. I am doing this now. But, there are several minor issues with this. Most have been covered in these forums. One is the trouble in finding the starting point of the output. There are tricks, and I use them, but it is surprisingly annoying to have to work so hard to do something that this fantastically efficient and time saving program can do.

Another convenient option to consider adding is select all (Ctrl-A). This would let me select the entire scroll buffer to paste into a text file myself. I can then edit out the bits I don't need.

Thanks Brian for your consideration.

[size=1][ June 18, 2008, 07:53 AM: Message edited by: Brian T. Pence ][/size]

I've used putty and found its scroll buffer history logging to a file useful. If I need to save the output of a command that will generate 30K+ lines, opening a log file makes saving this output smart and easy

Have you tried File->Open LOG and File->Close LOG?

Another convenient option to consider adding is select all (Ctrl-A).

It's a bit tricky to do this kind of thing in a terminal, because the ctrl-a may need to be sent to the host rather than interpreted locally. It is for this very reason that the copy/paste shortcuts are ctrl-insert and shift-insert (the original Microsoft defaults before ctrl-c/ctrl-v).

There is an easy way to do this, though. Just go to the top of the scrollbuffer and left-click. Now, go to the bottom of the buffer and shift-left-click. Just like in an edit control.

Are any of these options sufficient?

ugh - yes, the log option escaped me. Maybe it wasn't in the help?

🙂

And I know the Ctrl-A work arounds. Thanks for elaborating for the masses.

Thanks Brian