You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating this GH issue on basis of a conversation on Discord between 15th and 16th Dec 2024.
Currently, several fields are recorded in a database row for every command that are not (directly) displayed in the TUI.
The field that sparked the conversation on Discord was exit. While there is indication of a non-successful exit code via coloring of the duration field in the TUI, some people (including me) might find it beneficial to see the actual exit code verbatim in the TUI.
In general, it would be nice if Atuin would allow to configure the fields that are displayed in the TUI.
The text was updated successfully, but these errors were encountered:
I am creating this GH issue on basis of a conversation on Discord between 15th and 16th Dec 2024.
Currently, several fields are recorded in a database row for every command that are not (directly) displayed in the TUI.
The field that sparked the conversation on Discord was
exit
. While there is indication of a non-successful exit code via coloring of the duration field in the TUI, some people (including me) might find it beneficial to see the actual exit code verbatim in the TUI.In general, it would be nice if Atuin would allow to configure the fields that are displayed in the TUI.
The text was updated successfully, but these errors were encountered: