Running commands are not available

Feedback
1

I’m running in daemon mode, and I find another annoying case:

I’m running ssh in one terminal window, and it gets stuck. So I want to open another ssh session and see what happened, but I can’t find the still-running ssh command in atuin’s history.

This also means that new long running commands can’t be re-used and edited in another shell session via atuin. E.g. if I tail -F something new on one server with complex filtering in one terminal window, I can’t do the same for another server in another terminal window using atuin.

1 Like
2

In the case of bash, the history isn’t written to the history file until the session is ended.

In the case of Atuin (pure speculation, as I don’t know) I’d imagine it only pushes updates to the sync server upon session-close, or on the n’th minute update cycle.

(Edit - clarification)

3

I’ve finally patched it to restore to the old behavior for my ease of use. (Although I cannot update my local instance of atuin daemon yet, I will be able to fearlessly update it in the future after all my current sessions are closed.)