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.
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?
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.
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!
That's like calling a CRM app "Wiki" because you like the idea of collaborative editing of knowledge (in a world where Wikipedia already exists and is synonymous with wikipedia.org). Like... sure, no one can stop you, but it seems both counterproductive to your own marketing and mildly disrespectful to the other projects that are closer to the original ethos behind the name. It's not that hard to name things uniquely, at least call it "Memexa Code" or something.
Geez, thank you for taking the time to write that!
Seconded, very much. I Ctrl-f'd for "Bush", because in my head I immediately went, awh no, I bet it's going to be something a million miles away from what Vannevar Bush was trying to describe.
I strongly dislike when people naming things just pick something from the past to squat and vibe off. Have some respect for the legends of yesteryear, don't simply squat their concept-names with some very tangentially related product. Pick a different vibe. As my co-commenter said, even just put a tiny spin on it, to leave the original word unassaulted.
Billing. Subscription plans and invoices in micro services architecture.
I honestly hate it at this point and would appreciate any reading on the topic. It's been a grueling 4 months of back and forth with a lot of mission critical business aspects to handle that I had to learn on the fly.
Good luck with a quick git diff spanning thousands of lines. AI code can be notoriously verbose and over engineered. Of course you want to be in control.
I've been wrestling with this for a good long while as well.
A lot of business-y, corporate weight on my shoulders from $DAYJOB piling up and feeling out of touch with code at times.
I'm glad I still manage to have moments like OP every now and then
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.