Yes, thanks for clearing that up. There's a side issue that I routed around in my additional patch by saying "if OS is Windows, ignore this error and don't log it":
If Zim has anything Errors or Warnings to say, in Windows, these are written to the log file and every time you quit if the log file isn't empty, you get a popup message. My understanding is that on unix, Zim writes to the standard error channel and the desktop generally discards the output.
So what should we do about all these non-fatal errors? Can we configure the logger to just shut up about warnings unless the user provides a command line switch turning them on?
Yes, thanks for clearing that up. There's a side issue that I routed around in my additional patch by saying "if OS is Windows, ignore this error and don't log it":
If Zim has anything Errors or Warnings to say, in Windows, these are written to the log file and every time you quit if the log file isn't empty, you get a popup message. My understanding is that on unix, Zim writes to the standard error channel and the desktop generally discards the output.
So what should we do about all these non-fatal errors? Can we configure the logger to just shut up about warnings unless the user provides a command line switch turning them on?