5 ms·
It looks like it's not possible to export the history to a format the shell can import[0], so if I wanted to try this out, my commands would be locked there. I
by maleldil 3y ago
It looks like it's not possible to export the history to a format the shell can import[0], so if I wanted to try this out, my commands would be locked there.
It looks interesting, so if I'm overlooking a way to do this with fish, I'd experiment with it.
[0]: https://github.com/ellie/atuin/issues/816 https://github.com/ellie/atuin/issues/816
- codetrotter 3y agoIf you just want to experiement with it for say a couple of weeks, does it really matter that the commands from those few weeks disappear if you decide not to continue using it? Presumably you already have a long history of commands from past years in the original format. And if your command line usage is similar to mine, then most of the commands you will use in the future will be covered by your existing history. So if a few weeks of experimenting with atuin ends with you deciding not to use atuin, then probably you will be fine going back to the old history files that do not include those weeks of activity.
- jamespwilliams 3y agoIt’d be pretty trivial to do this yourself though, shell history files are very simple
- getpost 3y agoYou can use sqlite[0] to export the database, or if you want a ui, use datasette[1]. On my mac, the database is stored at ~/.local/share/atuin/history.db [0] https://sqlite.org/cli.html#export_to_csv https://sqlite.org/cli.html#export_to_csv [1] https://docs.datasette.io/en/stable/csv_export.html https://docs.datasette.io/en/stable/csv_export.html
- ellieh 3y agoWe’d like to be able to also export history, but atuin doesn’t actually stop your old shell history from functioning either So you could uninstall it, and you won’t have lost a thing
- maleldil 3y agoSounds good, thank you! I'll start playing with it.