set -o vi
ESC k /command
or just grep history...
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
set -o vi
ESC k /command
or just grep history...
It's too early to call me out like that.
Why are you making personal attacks against me.
Guilty!
I type the first few letters and use up arrow, or !start of command name
Nah just save all your commands in a text file on the desktop then make an alias to open it in nano so you just have to type "com". Works for dumb ol me
.. And waste an opportunity to type on my ludicrously expensive mechanical keyboard?
FRIG no
Atuin Magic Shell History is pretty good.
Me, playing indie games on Apple and doing the same with xattr -d com.apple.quarantine ~filepath
Set -o vi
I see so many people loving on atuin in the comments but I just tried it and don't get it. It seems so much worse than the built in search. I guess it's not for me.
I've been using it for a few months, and so far it's not as good as just regular old command history. I think any benefit might be for really, really old commands, or commands happening in a specific location. So, I'm going to keep using it to see if it helps then. But, so far it's a massive downgrade.
I thought command line users like typing things. I avoid typing where possible, and dont use the command line on Linux.
For a while I was using a VPN where the connections we all via command line. I loved it, because once you type it, it's just up up up to find that location again and swap around.
Now I have to use the mouse and click like a damn fool!
Part of the reason for a command line is being able to reproduce commands exactly. Going back through the command history is an important part of that.
In my first professional programming job writing custom software for clients in 1995, one of our standard sales pitches to clients was the idea that a GUI-based application would do away with the need for command prompts. This was always met with applause and great rejoicing. It's kind of remarkable that command prompts are still going strong thirty years later. I'm sure nobody would appreciate having this phenomenon compared to the Amish so I won't do it. But I think it's pretty cool that the Amish are still around doing their thing.
GUI is great, unless you want to automate something.. Then you either want a CLI or API