-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Verbose logging for TUI #11
Comments
Logging to the terminal when a TUI is rendered might cause rendering issues. Have you considered the following alternatives:
|
Thank you for the ideas @koutheir! Another alternative would be using tui-logger. |
Logging inside TUI would make the logs unavailable for further analysis at a later date, which is a very common use case for logs. |
What do you suggest here? @koutheir |
I suggest saving the log entries to a log file that can be analyzed after the fact. |
|
Is your feature request related to a problem? Please describe.
Printing to stdout is not possible while running TUI since the output is locked by the terminal backend (
termion
). This causes verbose logging to be suppressed.Describe the solution you'd like
Add a new command-line flag named
--verbose
and somehow enable verbose logging while running the TUI.Describe alternatives you've considered
-
Additional context
This will be useful when some of the parameters cannot be retrieved due to insufficient permissions and error logs are printed. Right now there is no way of telling when the parameter list is fetched without errors when the TUI is launched.
The text was updated successfully, but these errors were encountered: