Linux

13702 readers

487 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Atuin replaces your existing shell history with a SQLite database, and records additional context for your commands (github.com)

submitted 8 months ago by cm0002@lemmy.world to c/linux@programming.dev

10 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] beerclue@lemmy.world 8 points 8 months ago (1 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...

[–] just_another_person@lemmy.world 4 points 8 months ago (2 children)

That's not my point. Every shell already has history. What's the difference here?

[–] hallettj@leminal.space 4 points 8 months 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

[–] JadedBlueEyes@programming.dev 1 points 8 months ago

Bash by default limits history to ~1000 items iirc, and doesn't store anything but the command itself