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
After running the installer script, I expect the config file .config/atuin/config.toml to have been created.
What happened?
The config file (and indeed the .config/atuin directory) isn't created until the atuin command is run.
This was initially confusing: I was installing clients to use with a self-hosted atuin server, so wanted to edit the sync_address setting before running atuin login.
There was also no indication that a config file would be created by running an atuin command,
Atuin doctor output
I don't think this is relevant, but for one VM I tested this in:
This is even more confusing because the default version of config.toml changes some values from what their defaults would otherwise be (to enter_accepts = true and records = true).
When I was testing I installed on three machines minutes apart and one of them wouldn't sync its history with the others. It turned out that on that machine I had run an atuin command and edited the generated config file (whereas on the others I started with an empty file). This generated config file included records = true and changed the sync mechanism from v1 to v2.
What did you expect to happen?
After running the installer script, I expect the config file
.config/atuin/config.toml
to have been created.What happened?
The config file (and indeed the
.config/atuin
directory) isn't created until theatuin
command is run.This was initially confusing: I was installing clients to use with a self-hosted atuin server, so wanted to edit the
sync_address
setting before runningatuin login
.There was also no indication that a config file would be created by running an atuin command,
Atuin doctor output
I don't think this is relevant, but for one VM I tested this in:
Code of Conduct
The text was updated successfully, but these errors were encountered: