`atuin import zsh` imports history in reverse order?

[leogama]

I've just installed atuin in my Ubuntu 20.04, ZSH 5.8 pc using the deb package in Releases.

Running atuin import zsh (or auto) successfully imports my command history, but the imported commands then show up in reverse order when searching it through atuin. That makes no sense... Commands saved after the import and correctly appended to the history file appear in the right order.

Is it a timestamping issue? My history file had no timestamp or extra info, just the plain commands. I noted that atuin adds timestamps to ZSH history file.

For now, I've just reverted the history file with tac before importing and got it done. 👍🏼

[misuzu]

Same issue (v14.0.0, NixOS), same solution...

[LeoniePhiline]

I can confirm, with atuin 15.0.0:

$HISTFILE (~/.zsh_history), oldest on top (as if ordered by timestamp ASC):

.local/share/atuin/history.db, with ORDER BY timestamp DESC, showing the oldest zsh entries on top as if they were the newest, since timestamps are assigned in reverse.

The timestamps are created as now - seconds(counter), counting upwards while iterating through the history file. This way, the top items are placed close to now, while the bottom items are placed "the longest ago".

https://github.com/atuinsh/atuin/blob/main/atuin-client/src/import/zsh.rs#L82-L88

---

Edit: This should also affect other importers. They use the same iterator and counter to manipulate timestamps.

My take is that the entire UnixByteLines must be made double ended and read in reverse by default.

As a workaround, all lines can be counted to know how far back the oldest (and first in the list) items to place on the timeline.

It might be pragmatic to just collect the iterator into a Vec and reverse that.

[ajesipow]

I opened a PR or this. Looking forward to feedback.