Currently, if we require a user to send us logs to debug an issue they're having, it's very complicated.
A user can use c2-logs, but it requires the user to download another project.
A user can use the /debug-relaunch-with-console command from #6799, but it spawns the old conhost so the user doesn't have an easy time to actually export the logs to a file.
I propose we add a command similar to /debug-relaunch-with-console that relaunches Chatterino with logs saving to a file enabled. When this flag is enabled, we'd overwrite the qt logging handler with one that saves logs to a file.
See https://doc.qt.io/qt-6/qtlogging.html#qInstallMessageHandler
Currently, if we require a user to send us logs to debug an issue they're having, it's very complicated.
A user can use c2-logs, but it requires the user to download another project.
A user can use the
/debug-relaunch-with-consolecommand from #6799, but it spawns the old conhost so the user doesn't have an easy time to actually export the logs to a file.I propose we add a command similar to
/debug-relaunch-with-consolethat relaunches Chatterino with logs saving to a file enabled. When this flag is enabled, we'd overwrite the qt logging handler with one that saves logs to a file.See https://doc.qt.io/qt-6/qtlogging.html#qInstallMessageHandler