While implementing the profile/config upgrade work (PR #6558) it became clear that during the early stages of NVDA loading the logging level has not yet been set from the config file. In order to get debug level logging for these early stages you have to run NVDA with a command line argument to set the log level to debug (E.G. pythonw nvda.pyw -l 10). This is hard to remember, and would be hard to ask end users to do.
Firstly, I propose we add a more memorable option, for instance pythonw nvda.pyw --debug. In extension to this, making it easier for an end user to temporarily enable debug level logging would also lower the barrier to getting debug logs attached to github issues. This could be done by adding a "restart with debug logging" option to the tools menu of NVDA. Selecting this would restart NVDA passing the previously mentioned --debug argument.
The benefit of this is for users who generally do not want debug level logging, and the debug level logging is enabled earlier in the NVDA startup.
While implementing the profile/config upgrade work (PR #6558) it became clear that during the early stages of NVDA loading the logging level has not yet been set from the config file. In order to get debug level logging for these early stages you have to run NVDA with a command line argument to set the log level to debug (E.G.
pythonw nvda.pyw -l 10). This is hard to remember, and would be hard to ask end users to do.Firstly, I propose we add a more memorable option, for instance
pythonw nvda.pyw --debug. In extension to this, making it easier for an end user to temporarily enable debug level logging would also lower the barrier to getting debug logs attached to github issues. This could be done by adding a "restart with debug logging" option to the tools menu of NVDA. Selecting this would restart NVDA passing the previously mentioned--debugargument.The benefit of this is for users who generally do not want debug level logging, and the debug level logging is enabled earlier in the NVDA startup.