#atuin — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #atuin, aggregated by home.social.
-
📝 #Atuin Wrapped 2025
My 2025 in shell history
https://calebhearth.com/m/atuin-wrapped-2025 -
📝 #Atuin Wrapped 2025
My 2025 in shell history
https://calebhearth.com/m/atuin-wrapped-2025 -
#toolsday: Atuin 🦀
Deine Shell-History kennt nur grep? Atuin ersetzt sie komplett: SQLite-Backend, volle Textsuche, Sync zwischen Maschinen, und du findest jeden Befehl von vor 6 Monaten — in Sekunden.
Einmal installiert, vergisst du Ctrl+R.
Link: https://github.com/atuinsh/atuin
Welchen Befehl suchst du am häufigsten? 👇
-
#toolsday: Atuin 🦀
Deine Shell-History kennt nur grep? Atuin ersetzt sie komplett: SQLite-Backend, volle Textsuche, Sync zwischen Maschinen, und du findest jeden Befehl von vor 6 Monaten — in Sekunden.
Einmal installiert, vergisst du Ctrl+R.
Link: https://github.com/atuinsh/atuin
Welchen Befehl suchst du am häufigsten? 👇
-
🐢 #Atuin is an #opensource shell history tool written in #Rust that replaces your existing shell history with a #SQLite database and records extra context for every command 🧵👇 #cli #devtools #devops
⚡ ctrl-r and up-arrow (configurable) are rebound to a full-screen history search UI, with enter to execute and tab to edit a command
-
Here's today's "peanut butter & chocolate" combination: I love `atuin`. I've been using it for at least a couple of years now. I love `fc`, though with `atuin` in place, it's harder to put yourself in an `fc` situation.
`fc` excels: opens up some previous command in your favorite editor; tweak as needed; write and quit; the changed command is executed and added to history.
`atuin` excels at almost everything else, but not this. My workflow in `atuin` to accomplish the same thing is:
* use arrows or Ctrl-R to select the command that wasn't quite right
* tab takes you back to the command line with the selected command, but does **not** execute it
* I use Vi-mode, so I have to hit ESC, and then v (and because it's Zsh, v again) to get into my editor. If you use Emacs-mode (the default), I think it's Ctrl-X Ctrl-E to go from normal typing into your full-blown editor
* tweak; write; quit
* ...and now you have the edited command, **but it still hasn't executed**
* hit returnMy Atuin PR addresses this: https://github.com/atuinsh/atuin/pull/2851
-
Here's today's "peanut butter & chocolate" combination: I love `atuin`. I've been using it for at least a couple of years now. I love `fc`, though with `atuin` in place, it's harder to put yourself in an `fc` situation.
`fc` excels: opens up some previous command in your favorite editor; tweak as needed; write and quit; the changed command is executed and added to history.
`atuin` excels at almost everything else, but not this. My workflow in `atuin` to accomplish the same thing is:
* use arrows or Ctrl-R to select the command that wasn't quite right
* tab takes you back to the command line with the selected command, but does **not** execute it
* I use Vi-mode, so I have to hit ESC, and then v (and because it's Zsh, v again) to get into my editor. If you use Emacs-mode (the default), I think it's Ctrl-X Ctrl-E to go from normal typing into your full-blown editor
* tweak; write; quit
* ...and now you have the edited command, **but it still hasn't executed**
* hit returnMy Atuin PR addresses this: https://github.com/atuinsh/atuin/pull/2851
-
I still wish #atuin, which I have installed on all my machines, will support syncing more than bash history, environment variables, and aliases 😇 Extremely useful, regardless. In the meantime, we get an optional #aichat-like feature. Inevitable, I guess, though aichat is more than an English-to-bash helper.
The new opt-in feature, Atuin #AI, offers an English-to-bash helper directly within the shell. It leverages advanced models and a dataset of man pages and command outputs for accuracy, includes safety guardrails to flag potentially dangerous commands, and prioritizes data privacy by default. Users can grant access to more specific data like directory contents for enhanced command generation.
-
Here’s your regular #CommandLine #PSA: #Starship helps you every time you hit return, in every shell. #Atuin makes history 10x more useful. #Direnv is becoming my friend but I need to understand better how to use it, and it needs additions to work in more situations.(e.g., #uv layout, #pixi layout, better path handling in #GitBashForWindows)
-
Here’s your regular #CommandLine #PSA: #Starship helps you every time you hit return, in every shell. #Atuin makes history 10x more useful. #Direnv is becoming my friend but I need to understand better how to use it, and it needs additions to work in more situations.(e.g., #uv layout, #pixi layout, better path handling in #GitBashForWindows)
-
Here’s your regular #CommandLine #PSA: #Starship helps you every time you hit return, in every shell. #Atuin makes history 10x more useful. #Direnv is becoming my friend but I need to understand better how to use it, and it needs additions to work in more situations.(e.g., #uv layout, #pixi layout, better path handling in #GitBashForWindows)
-
Here’s your regular #CommandLine #PSA: #Starship helps you every time you hit return, in every shell. #Atuin makes history 10x more useful. #Direnv is becoming my friend but I need to understand better how to use it, and it needs additions to work in more situations.(e.g., #uv layout, #pixi layout, better path handling in #GitBashForWindows)
