Make KrDebugLogger (and so the e.g. /tmp/krdebug trace file) usable by any file of Krusader.
Interestingly, that also helps when a user has a particular problem that developers can't reproduce. Then a developer can add a lot of KRFUNC, etc. to the krusader code, send the debug Krusader executable to the user, the user can experiment his particular problem, and finally the user is able to send the "krdebug" trace file to the Krusader developers, so they can know better what happened.
Enter some zip files, 7z files, iso files, etc. and check the information that is automatically added to the /tmp/krdebug file . Add some KRFUNC in other files (like the main.cpp one), execute Krusader and also check the information that is automatically added to the /tmp/krdebug file
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
Is there a specific reason to not use QCDebug? kdebugsettings can configure the writing location for all QCDebug users, so I suspect you should be able to do it inside the program too.
Thanks, Luigi Toscano, definitely qCDebug is something worth looking for, and this task can be a first step because it simplifies the prior situation.
So we can ship the changes of the present task and later see if Krusader (and its kioslave named "krarc") can use the system of qCDebug.