I have used a history log (history.log) for as long as I can remember. It's useful to be able go back (for me, way back) and see how I did something. I suppose the following remarks will also apply to a command log. A few weeks ago I noticed a delay between pressing <Enter> and seeing command output. I reckon it was between 1/3 and 1/2 second ... but it was troublesome. I'm confident that the delay had been growing for years (and I finally noticed it). My history log had grown to about 3.6 MB and that was the culprit. When I press <Enter>, TCC and Windows must open the file, map its contents, find the end of it, write to it, save it to disk, and close it. If it's 3.6 MB, that takes a noticeable amount of time. So I copied history.log to history.txt and emptied history.log. The delay went away. Later, I created a scheduled task which, every night, runs a BTM that appends history.log to history.txt and empties history.log. I'm confident that TCC will remain snappy. That log probably goes back four or five years. I have a couple others, zipped up and tucked away; the older one of them was saved in 2004. So I wonder (especially about the many long-time users here) ... how big is your log file?