https://tldr.sh/
tldr
Ask HN: Can I see your cheatsheet?
31–40 of 173 posts
Re: Ask HN: Can I see your cheatsheet?
#32I have maybe 50 pages of cheat codes worth. I haven't had the time to post them somewhere yet. Remind me... a week from now :D
Remind me... a week from now :D
--> This is actually a real problem on forums --> just to remind a stranger on a forum to commment on something. --> I´m working on a concept / tool to make it simple.
--> Would you like to talk about that? Ron.
Re: Ask HN: Can I see your cheatsheet?
#33No maintained cheat sheet here either. I do use `history | grep` quite a lot though. One thing I try to do is to keep my keyboard shortcuts consistent between programs/systems. That way the chance of my instinct of pressing ` +a` to move the cursor to the start of the line will be correct more often. Another thing I try to do when a project has a set of complex commands that are needed, is to add them as a rule in it…
I use Ctrl+R chronically for the same thing.
Re: Ask HN: Can I see your cheatsheet?
#34My only real cheatsheet is a list of shortcuts I maintain for programs/apps I use: system: ctrl+space=switch keyboard input language iterm2: cmd+; = autocomplete fn+cmd+ = scroll to bottom of buffer fn+cmd+^ = pgup buffer fn+cmd+v = pgdown buffer fn+ = end of line shift+cmd+[ = previous tab shift+cmd+] = next tab cmd+K = delete til end of line cmd+enter = full-screen on/off cmd+shift+e = show command timeline!!! chro…
[deleted]
Re: Ask HN: Can I see your cheatsheet?
#35Try using flashcards (Anki) to remember shortcuts if you haven't yet. Just like with learning a foreign language, it's a quick way to get "action -> shortcut" mappings into your brain permanently for recall at any time, rather than relying on a cheatsheet.
Re: Ask HN: Can I see your cheatsheet?
#36No maintained cheat sheet here either. I do use `history | grep` quite a lot though. One thing I try to do is to keep my keyboard shortcuts consistent between programs/systems. That way the chance of my instinct of pressing ` +a` to move the cursor to the start of the line will be correct more often. Another thing I try to do when a project has a set of complex commands that are needed, is to add them as a rule in it…
same here - my cheatsheet is `history | grep`
Re: Ask HN: Can I see your cheatsheet?
#37For bash, this is my cheatsheet (can be viewed from within bash): https://github.com/darekkay/config-files/blob/master/bash/.c...
I also maintain cheatsheets for some dev stuff: https://github.com/darekkay/config-files/tree/master/cheat-s...
And then there's my Flexbox cheatsheet: https://darekkay.com/flexbox-cheatsheet/
Re: Ask HN: Can I see your cheatsheet?
#38I keep a printed copy of C++ operator precedence around the desk.
https://en.cppreference.com/mwiki/index.php?title=cpp/langua...
Re: Ask HN: Can I see your cheatsheet?
#39This surprised me that people do this. I don't have any, since if I have to look up one, it's not really useful :)
But my cheat sheet is google, I usually find what I want in no time.
Re: Ask HN: Can I see your cheatsheet?
#40No maintained cheat sheet here either. I do use `history | grep` quite a lot though. One thing I try to do is to keep my keyboard shortcuts consistent between programs/systems. That way the chance of my instinct of pressing ` +a` to move the cursor to the start of the line will be correct more often. Another thing I try to do when a project has a set of complex commands that are needed, is to add them as a rule in it…
same here - my cheatsheet is `history | grep`
I'm curious why history | grep and not ctrl-R?