Live data from Hacker News

Atuin – Magical Shell History

atuin.sh

61–70 of 72 posts

Re: Atuin – Magical Shell History

#61
post #49

Earlier quoted context omitted.

> does atuin give me anything significant over my current fzf based C-r I'm interested in this as well. I currently use fzf and I'm happy with what I've got (except for me syncing would probably be a nice feature to have). Also: I gave atuin a quick try and found the TUI to be worse than fzf. Why do I need a fullscreen ctrl-r interface? I found that distracting. But maybe that is configurable. I didn't look much furt…

It is configurable! And also the default is now to use 40 lines, not the alt screen (has its own drawbacks) You can set “inline_height” https://docs.atuin.sh/guide/basic-usage/#inline-window

But the inline_height seems to be a constant, rather than a percentage of the window, which is weird.

As long as you're here, do you know if the column showing the amount of time the command took can be removed? I know you can remove it from "atuin history list" with history_format, but I don't see a way to remove it from the inline window.

Re: Atuin – Magical Shell History

#62
post #31

The sync feature is great, though there are many oddities with search sort order, unnecessary terminal cleanups, odd timeouts, etc. In some aspects it's a big upgrade from fzf, in some aspects it's a downgrade.

The search defaults are pretty bad, but I'm happy with "fuzzy" mode.

I'm using it, but it's still much less natural than what I had with fzf.

Re: Atuin – Magical Shell History

#63
post #42
post #20

I see it also supports fish. That's been my shell for many years, it just works really well and, as far as I can tell (couldn't find a demo on their website), it doesn't add much to fish beyond syncing? Has anyone used fish + autuin? What are your thoughts? I'm curious to know if it is worth the extra tool, maybe I should just try it :)

The main thing would be opt-in syncing, and I think we might store a little more context than fish does in their SQLite! Otherwise consistency is nice if you use a few setups

fish doesn't use SQLite, but its own plaintext format. They've been trying to migrate to other formats.[1] Currently fish stores timestamps and directories in its history.

[1] https://github.com/fish-shell/fish-shell/issues/3341

Re: Atuin – Magical Shell History

#64
post #59
post #40

Earlier quoted context omitted.

You already have it Nothing syncs without you registering an account or logging in

lovely. I vaguely remember back when I first signed on, it wasn't opt-out by default so I assumed it stayed the same. disregard my quip! hahaha

I don't mean to be rude but this has been the case since the project first started in 2021. You have always had to sign in to sync anything at all

It's always been opt-in, or "opt-out by default".

Re: Atuin – Magical Shell History

#65
What are the terms and conditions regarding the data collected at api.atuin.sh

By default, the user's shell history is synced to a remote server

Unless they configure and run their own localhost server

Localhost server could be but is not the default when user enters

   atuin register
Instead remote server is pre-configured, asks for email, etc.

Interesting design choice

I have used SQLite to store and search history instead of Postgres

Works with Bourne shell (sh), no need for Bourne-Again shell (bash) or other larger shells

What does "magical" mean in this context

Re: Atuin – Magical Shell History

#67
post #17

For zsh users who like this idea and don't want to have to worry about anything leaving the device (not to insinuate that Atuin is doing anything below board, I don't think they are) I built my own version of this for myself called raven: https://github.com/tylersaunders/raven Raven has no sync component, stores your history in a sqlite, and never tries to move data off the device. It has a similar / large overlap in…

our sync is opt-in + optional, e2e encrypted, and self-hostable. if that's not enough, you can disable all network features via a feature flag at compile time if you don't care for sync, there are a bunch of other projects doing this (and supporting several shells), eg: - mcfly: https://github.com/cantino/mcfly - resh: https://github.com/curusarn/resh

> if that's not enough, you can disable all network features via a feature flag at compile time

Are there network features other than sync?

Re: Atuin – Magical Shell History

#68
I'm glad that there already is a tool that I was about to make. I don't usually like to change my workflow, but this seems like a very useful addition, since I can also add my history from past installations.

Re: Atuin – Magical Shell History

#69
post #6

I've been using Atuin for at least a year and a half, and I think it's definitely the tool I'd been looking for the most in my entire dev career. It has made me much more confident with my hazy memory. Before it I'd struggle consistently to remember most of my recent commands. bck-i was always a bit obtuse to me and I honestly never grokked it until I had Atuin wired into my workflow (hard) and ran into bck-i instead…

One of the things I really struggle to retain about the shell is the various expansions.

Unfortunately history shows the expanded form of what's happened, so I can't go reference that I used the third word of history item 773 as an argument, I only see the resolved argument.

Alas I haven't found any hooks in zsh that show promise here. I'd really love the pure history.

One technique I've used in the past is making a quick command in vim, that takes the selection or current line, and sends it to a given terminal. And perhaps starts a new line too. Basically using vim to author commands, to build the history log. Also I get to use vim, yay.

Re: Atuin – Magical Shell History

#70
post #19
post #6

I've been using Atuin for at least a year and a half, and I think it's definitely the tool I'd been looking for the most in my entire dev career. It has made me much more confident with my hazy memory. Before it I'd struggle consistently to remember most of my recent commands. bck-i was always a bit obtuse to me and I honestly never grokked it until I had Atuin wired into my workflow (hard) and ran into bck-i instead…

(dev here!) thank you so much! I love to hear things like this <3

Thanks for your work! Atuin is definitely one of those "How did nobody figure this out before now?" sort of ideas, executed really well. Two thumbs up.

I'm really intrigued by the upcoming Runbooks - they seem like they could be an absolute game changer. Any updates/teases on that front?

Post reply on HN