Curate your shell history
(esham.io)
from learnbyexample@programming.dev to linux@lemmy.ml on 15 Jun 04:18
https://programming.dev/post/32232151
from learnbyexample@programming.dev to linux@lemmy.ml on 15 Jun 04:18
https://programming.dev/post/32232151
threaded - newest
I comment the commands that I want and then use vim to remove ones without comments.
For example, I run:
Usually comment explains what the command does so I can find it by description using fzf history search. And then you can easily find all lines that contain (or do not contain “
# keep
”) in your history to remove or keep.We are same. I sometimes use comments as kind of tags, like
or
or sometimes I’ll add
# works
at the end of a long string of attempts (usually involving dialing into a regexp), likeI might try this. Normally would just pipe history into grep to search or scroll till I found the right command. Also
smite
is a great name for that function.I use ctrl-r.
Excellent, thanks
Right, I was starting to think “Oh yeah and maybe I could fzf history…” then wait, I already do that
reverse-i-search
then edit. If I use that often enough, alias in ~/.bashrc or even function to make it composable.Atuin (by @ellie@hachyderm.io) makes the history storage and management side much easier and portable, but could perhaps use a “smite mode” to make deletion interactively easier. The current interactive implementation prioritizes safety over expediency which is fine, but a “today I clean things” option could perhaps instead prioritize the other way around and enable one key delete w/ undo instead.
Is this some sort of bash/zsh joke that I’m too fish to understand?
Okay I can see how curating could work. But if you’re lazy like me, I recommend this:
github.com/PatrickF1/fzf.fish