Debug log to memory instead of disk

[dev0]

How about putting the debug log in a memory buffer then displaying it as part of the GUI, instead of always writing it to disk. This would reduce disk IO, increase performance, remove yet another locked file, plus allow the user to see in real-time what was going on behind the scenes. 

[jeroen]

The debug log is exactly that - a debug log. It is not intended for users and not documented. It should not be in memory because then it would be lost in case of a crash. For user output see the statistics window and the SetStatisticsWindowText script setting, and the AppendLogfile and WriteLogfile commands.

[dev0]

I'd still like a way of seeing in real-time what MyDefrag is doing, much in the same format as it is in the most verbose logging method.  Opening (or reloading) the log file and scrolling to the bottom is both cumbersome and not real-time.  From what I can tell, this isn't doable with the current facilities provided in SetStatisticsWindowText, but perhaps this could be added as a !DEBUGTAILnn! (nn being a buffer of lines from the end of the log)

[jeroen]

I'm sorry but I don't think it's useful to display more detail than what is already displayed in the text just above the diskmap. For looking at the end of a logfile type "Windows logfile tail" or something like that in Google, there are many utilities available that will automatically scroll and show the end of a logfile.

[dev0]

Thank you for your feedback.  I was hoping I wouldn't have to use another 3rd party utility specifically for this purpose, since I use MyD on many systems.  I don't think it would be very difficult to add maybe a 3rd view option "debuglog" to view the current debuglog state.  Sorry for being persistent on this topic.