The thing with a lot of these tricks is that you have to get into the habit of using them. I knew `Ctrl+r` for history since I learned about the command line. I even have a nice shell integration with fzf. But I still used the up/down arrow keys for years or scrolled up when I was looking for a previous command, because I never remembered the shortcut and just took the path of least resistance to find something.
Usually what I do is writing these tricks down to a document that is easily accessible at a place where I know that I will look for when failing to remember them. I have a directory of docs where I write stuff like this down by language/tool/etc., so I can quickly look it up without having to search the internet. But I also have to actively remind myself that these things exist whenever I have a problem, stop me from just doing the inefficient thing.
This way, when I want to find it again, I CTRL-R and type ‘forkbomb’ .. voila, instant recall!
All I have to remember is the small ontology I keep in my head for the most important commands I use .. pretty easy if I also construct a narrative for those commands, contextually. “#downup #clearlog #checkconn #amialone #forkbomb”, etc.
phforms · · focus · HN ↗
Usually what I do is writing these tricks down to a document that is easily accessible at a place where I know that I will look for when failing to remember them. I have a directory of docs where I write stuff like this down by language/tool/etc., so I can quickly look it up without having to search the internet. But I also have to actively remind myself that these things exist whenever I have a problem, stop me from just doing the inefficient thing.
MomsAVoxell · · focus · HN ↗
All I have to remember is the small ontology I keep in my head for the most important commands I use .. pretty easy if I also construct a narrative for those commands, contextually. “#downup #clearlog #checkconn #amialone #forkbomb”, etc.