Open matthewcmead opened 1 month ago
Hey!
history.db
isn't meant to be written to externally. We have a central source (records.db
) that stores history encrypted, ready to sync. If it's not added to records, it won't function properly. We have an import function that handles history from other sources, and ensures it's stored correctly.
I'd suggest one of the following
What did you expect to happen?
I've been using https://github.com/ddworken/hishtory/ for global history capture and would like to migrate to atuin. I have been unable to find a way to import hishtory's structured history data into atuin in a way that atuin will use. Here's what I've done:
I've used clickhouse-local with the following SQL to transform the hishtory data to atuin's schema:
I then exported this to TSV, and used sqlite3 to load the history data into atuin's history.db file:
I'm then able to see the entries in the sqlite table.
What happened?
I expected atuin to allow me to search these prior history entries, but it does not. Is there some mechanism to get atuin to sync all its internal data off the history.db history table and incorporate it future executions of the program?
Thanks!
Atuin doctor output
Code of Conduct