Live data from Hacker News

Atuin – Magical shell history

atuin.sh

111–118 of 118 posts

Re: Atuin – Magical shell history

#111

Why is this better than a shell's built-in history, possibly paired with fzf? I'm not asking sarcastically, either. Is this something awesome I should be using? What about it is going to blow my mind?

I had something similar set up Fish and fzf. When I first did that, I thought it was magic. Atuin brought back more of the magic.

It syncs across devices. I’ve got a number of raspberry pi devices I use and I never remember what command I used. Also preserves history when I inevitably need to replace the SD card.

Atuin also preserves information about the exit code. So you can filter on commands that worked. Which is great.

And, you can still use fzf to search your history if you want. I’ve got ctrl-r bound to search Atuin with fzf and ctrl-t to use native Atuin search.

If you’ve got an extensive history already, Atuin easily imports it. So I didn’t miss anything.

And because I wrote an ansible playbook to install it everywhere, including provisioning my self-hosted Atuin server, it just works.

Biggest downside was compiling for Raspberry Pis - which may be running slightly different versions of Raspbian. The project doesn’t provide the arm7 binaries. Eventually I figured out how to do fully static compilation with rust and that solved my problems.

Re: Atuin – Magical shell history

#112
post #110
post #79

Earlier quoted context omitted.

Why should it store garbage in the database?

Why do you enter garbage in the terminal? But seriously from the next answer: „ The reason it saves every command is so that it can produce statistics, for example exit code distribution and runs per day etc“

Because I'm a human and err??? And what value do GIGO statistics have? The next answer doesn't defend you weird take that it must store garbage, that's still on you

Re: Atuin – Magical shell history

#113
post #99
post #60

Can it do the magic of deduplication, cleaning failed commands with typos so your history isn't cluttered, and use frecency for autocompletions?

It does de-duplicate. It saves every command (even duplicates), but as soon as you search it only ever shows the last version you ran. The reason it saves every command is so that it can produce statistics, for example exit code distribution and runs per day etc.

Oh, the screencast had dupe lvim at 10s and then there are issues like this https://github.com/atuinsh/atuin/issues/409.

The runs/code can be stored as list to get the distribution, though for typo I don't want any distribution, I just want them gone, and for identical commands with different comments I'd want a single run stat

These are the cleaning type of things that would be closer to magical

Re: Atuin – Magical shell history

#114
post #113
post #99

Earlier quoted context omitted.

It does de-duplicate. It saves every command (even duplicates), but as soon as you search it only ever shows the last version you ran. The reason it saves every command is so that it can produce statistics, for example exit code distribution and runs per day etc.

Oh, the screencast had dupe lvim at 10s and then there are issues like this https://github.com/atuinsh/atuin/issues/409 . The runs/code can be stored as list to get the distribution, though for typo I don't want any distribution, I just want them gone, and for identical commands with different comments I'd want a single run stat These are the cleaning type of things that would be closer to magical

That issue is closed and fixed since almost a year. And as the author said, the 'list' command is supposed to list all invocations. When you search (Ctrl+R) you don't see duplicates (I guess the screencast might be old?).

It feels like you are just trying to find issues without having tried using it for real...

Re: Atuin – Magical shell history

#115
post #113

Earlier quoted context omitted.

Oh, the screencast had dupe lvim at 10s and then there are issues like this https://github.com/atuinsh/atuin/issues/409 . The runs/code can be stored as list to get the distribution, though for typo I don't want any distribution, I just want them gone, and for identical commands with different comments I'd want a single run stat These are the cleaning type of things that would be closer to magical

That issue is closed and fixed since almost a year. And as the author said, the 'list' command is supposed to list all invocations. When you search (Ctrl+R) you don't see duplicates (I guess the screencast might be old?). It feels like you are just trying to find issues without having tried using it for real...

It feels like you're just trying to pretend the issue isn't real

> closed and fixed ... 'list' command is supposed to list all

This is NOT a fix, but a confirmation that this design flaw is unlikely to get fixed. I don't need fzf to be flooded with useless info either.

How would using it for real help here?

Re: Atuin – Magical shell history

#116
I've been using a combination of git (append only when merging) and systemd for that for a long time now, my history file is 70k lines now and still works like a charm.

I wonder however how people can spend a lot of time in the shell and have no sync process at all in their shell history.

Post reply on HN