Writing a log file

repuust · 15th July 2008, 15:26

Thanks for the help. Trust me, I went through the manual a dozen times, but couldn't find anything. Everything I found implied that SetDetailsPrint was the way to do logging, not downloading a specialized build and using LogText. Heck, if you type "logging" into the NSIS User Manual, LogSet never even comes up! I still don't even understand what SetDetailsPrint both is supposed to do.

Unfortunately, the output generated by LogText seems to be too verbose for my needs. I use the XML library which seems to generate about 300 "Jump: 224". Plus, I want to have a log file for install and un-install. I will probably just roll my own macro that writes to a file.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

15th July 2008, 15:26	#3
repuust Junior Member Join Date: Jul 2008 Posts: 5	Thanks for the help. Trust me, I went through the manual a dozen times, but couldn't find anything. Everything I found implied that SetDetailsPrint was the way to do logging, not downloading a specialized build and using LogText. Heck, if you type "logging" into the NSIS User Manual, LogSet never even comes up! I still don't even understand what SetDetailsPrint both is supposed to do. Unfortunately, the output generated by LogText seems to be too verbose for my needs. I use the XML library which seems to generate about 300 "Jump: 224". Plus, I want to have a log file for install and un-install. I will probably just roll my own macro that writes to a file.