Starting with version 18.13 (#3201, specifically), Atuin by default writes logs to ~/.atuin/logs. The path is configurable, but I believe it would be more consistent to use the XDG recommended location, like is already done with config files and persistent data.
The XDG specification recommends $XDG_STATE_HOME ($HOME/.local/state by default) for storing user-specific log files:
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, …)
Not filing as a bug because I'm not sure if this was intentional or not. Or if there is perhaps a better strategy, like writing to syslog/journald if present, and whatever the corresponding macOS service is? That would also save the headache of maintaining log cleanup code, but I guess logging to the filesystem is still needed as a fallback for non-systemd systems.
See also: #3333.
Starting with version 18.13 (#3201, specifically), Atuin by default writes logs to
~/.atuin/logs. The path is configurable, but I believe it would be more consistent to use the XDG recommended location, like is already done with config files and persistent data.The XDG specification recommends
$XDG_STATE_HOME($HOME/.local/stateby default) for storing user-specific log files:Not filing as a bug because I'm not sure if this was intentional or not. Or if there is perhaps a better strategy, like writing to
syslog/journaldif present, and whatever the corresponding macOS service is? That would also save the headache of maintaining log cleanup code, but I guess logging to the filesystem is still needed as a fallback for non-systemdsystems.See also: #3333.