There is an advantage to this approach though: fewer errors. You're plucking a known working command from a list instead of manually typing a (possibly) broken version of it. Worse yet is when it's a command where typematic mistakes cause unintended side effects like data loss. So, mashing up 100 times can be pretty smart, especially if you're not a great typist.

Sorry, do you not keep sql scratch files around?

If deving on the cli name and save to separate files your reusable queries...

I've been using Atuin on my work computer and found it to be pretty good if you want something a bit fancier than Ctrl + R

Can’t find the info atm but if you setup inputrc to use vim controls you can use the vim search in psql.

So...Emacs huh

Me looking for apt update && apt upgrade -y

I definitely do this with terminal commands, because I'm not hunting for whatever the specific command line to animate my gif wallpaper is.

I do that sometimes, lazy as I can be

At work, was recently working on a script that alters the repo significantly. Every time I tested the script, I used the up arrow to get the git clean and git checkout HEAD -- files commands to reset the repo. I must've used those 100+ times.

I open the text file where my powershell history is stored when the command I want isn't recent enough.

That's when I realise I need more coffee.

oh the days before fzf