▲ 66 ▼ Atuin replaces your existing shell history with a SQLite database, and records additional context for your commands (github.com) submitted 1 year ago by cm0002@lemmy.world to c/linux@programming.dev 10 comments fedilink hide all child comments
[–] just_another_person@lemmy.world -1 points 1 year ago (4 children) Why? permalink fedilink source hideshow 4 child comments replies: [–] beerclue@lemmy.world 8 points 1 year ago (3 children) i for one can't be bothered to remember, for example, the syntax to add a new gitlab project to the allowed list of a hashicorp vault policy :) - i use zsh with fzf and ag, so i ctrl+r to find the last time i used this, adjust, execute. there are many use cases for checking out your shell's command history... permalink fedilink source parent hideshow 3 child comments replies: [–] just_another_person@lemmy.world 4 points 1 year ago (2 children) That's not my point. Every shell already has history. What's the difference here? permalink fedilink source parent hideshow 2 child comments replies: [–] hallettj@leminal.space 4 points 1 year ago It has a nice interface for searching history - nicer than the history search included with the shells I've used It has a "workspace" mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you're working on in that directory If you want you can back up, or sync history to multiple machines. I know I've been in situations where I know the command I want is in history, but it's in history on my desktop, and I'm on my laptop at the moment permalink fedilink source parent [–] JadedBlueEyes@programming.dev 0 points 1 year ago Bash by default limits history to ~1000 items iirc, and doesn't store anything but the command itself permalink fedilink source parent
[–] beerclue@lemmy.world 8 points 1 year ago (3 children) i for one can't be bothered to remember, for example, the syntax to add a new gitlab project to the allowed list of a hashicorp vault policy :) - i use zsh with fzf and ag, so i ctrl+r to find the last time i used this, adjust, execute. there are many use cases for checking out your shell's command history... permalink fedilink source parent hideshow 3 child comments replies: [–] just_another_person@lemmy.world 4 points 1 year ago (2 children) That's not my point. Every shell already has history. What's the difference here? permalink fedilink source parent hideshow 2 child comments replies: [–] hallettj@leminal.space 4 points 1 year ago It has a nice interface for searching history - nicer than the history search included with the shells I've used It has a "workspace" mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you're working on in that directory If you want you can back up, or sync history to multiple machines. I know I've been in situations where I know the command I want is in history, but it's in history on my desktop, and I'm on my laptop at the moment permalink fedilink source parent [–] JadedBlueEyes@programming.dev 0 points 1 year ago Bash by default limits history to ~1000 items iirc, and doesn't store anything but the command itself permalink fedilink source parent
[–] just_another_person@lemmy.world 4 points 1 year ago (2 children) That's not my point. Every shell already has history. What's the difference here? permalink fedilink source parent hideshow 2 child comments replies: [–] hallettj@leminal.space 4 points 1 year ago It has a nice interface for searching history - nicer than the history search included with the shells I've used It has a "workspace" mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you're working on in that directory If you want you can back up, or sync history to multiple machines. I know I've been in situations where I know the command I want is in history, but it's in history on my desktop, and I'm on my laptop at the moment permalink fedilink source parent [–] JadedBlueEyes@programming.dev 0 points 1 year ago Bash by default limits history to ~1000 items iirc, and doesn't store anything but the command itself permalink fedilink source parent
[–] hallettj@leminal.space 4 points 1 year ago It has a nice interface for searching history - nicer than the history search included with the shells I've used It has a "workspace" mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you're working on in that directory If you want you can back up, or sync history to multiple machines. I know I've been in situations where I know the command I want is in history, but it's in history on my desktop, and I'm on my laptop at the moment permalink fedilink source parent
[–] JadedBlueEyes@programming.dev 0 points 1 year ago Bash by default limits history to ~1000 items iirc, and doesn't store anything but the command itself permalink fedilink source parent