New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the debug level configurable within neomutt #445
Comments
then debugfile should be configurable as well! |
+1 for the idea I like the idea to have an configurable debugfile. I don't like the current behavior I would prefer to always append to the same file. I can work on this, if nobody step in. |
@sileht Nobody has assigned theirselfes to this issue yet, therefore you can of course work on this. I'll assign you to it, so that people know this is WIP. Thanks! :) |
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes #445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes #445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes neomutt#445
This change allows to change debug_level and debug_file on the fly. It adds the -l mutt arguments to pass the logging file on startup. debug options passed as mutt arguments always override the configuration file. Closes #445
Starting neomutt with the option
-d 2
enables debug logging (if enabled by the build).Often, the user hasn't enabled this logging when then encounter a problem.
Often, restarting will leave neomutt in a slightly different state to the one that caused the problem.
I propose changing the internal
debuglevel
variable into a user-configurable$debug_level
Use case: User sees some unexpected behaviour
set debug_level=5
When
debug_level
is set > 0, a new log file will be opened.When
debug_level
is set to 0, the log file will be closed.The text was updated successfully, but these errors were encountered: