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
btop logs to $XDG_CONFIG_HOME/btop/btop.log. This does not follow the XDG Base Directory Specification and is generally unexpected behavior.
Is your feature request related to a problem? Please describe.
I for example, set btop's $XDG_CONFIG_HOME to a location which is not writable, which it complains about every time I start it:
Describe the solution you'd like
This could, for example, be moved to $XDG_STATE_HOME or $XDG_CACHE_HOME:
The $XDG_STATE_HOME contains state data that should persist between (application) restarts, but that is not important or portable enough to the user that it should be stored in $XDG_DATA_HOME. It may contain:
actions history (logs, history, recently used files, …)
current state of the application that can be reused on a restart (view, layout, open files, undo history, …)
$XDG_CACHE_HOME defines the base directory relative to which user-specific non-essential data files should be stored.
This woud be much more intuitive, since $XDG_CONFIG_HOME is not meant for logging in the first place.
The text was updated successfully, but these errors were encountered:
I second this. Configurations are supposed to be portable between machines. I synchronize many of my XDG_CONFIG_HOME contents via Nextcloud between machines. This means that if I run btop on multiple machines at once, I can end up getting sync conflicts.
Just adding this as a real world use case where this causes "issues" (albeit minor ones).
btop logs to
$XDG_CONFIG_HOME/btop/btop.log
. This does not follow the XDG Base Directory Specification and is generally unexpected behavior.Is your feature request related to a problem? Please describe.
I for example, set btop's
$XDG_CONFIG_HOME
to a location which is not writable, which it complains about every time I start it:Describe the solution you'd like
This could, for example, be moved to
$XDG_STATE_HOME
or$XDG_CACHE_HOME
:This woud be much more intuitive, since
$XDG_CONFIG_HOME
is not meant for logging in the first place.The text was updated successfully, but these errors were encountered: