Comment by nidnogg

1 year ago

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 when SSH'd.

Anytime a peer views my screenshare, they ask "what's the funny thing that makes you so fast". I then proceed to share, first and foremost, Atuin.

Thanks Atuin team! Would love to contribute someday with more time.

12 comments

nidnogg

Reply
ellieh  1 year ago

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

  • digdugdirk  1 year ago

    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?

jauntywundrkind  1 year ago

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.

thibaultamartin  1 year ago

I second this wholeheartedly. Atuin is a joy to use and makes it so easier to find past commands. Thanks a lot atuin, and thanks to the colleague who recommended it!