https://notes.arunsr.in/
cheat sheets, notes, learnings all go here.
Ask HN: Can I see your cheatsheet?
131–140 of 173 posts
Re: Ask HN: Can I see your cheatsheet?
#132I actually do most of my tasks in various GUIs. This has a large advantage in discoverability (and for my brain: memorability). So I find no need for cheat sheets in general.
If on command line, I am typically following an installation guide or something so no need for a cheat sheet.
If scripting, I refer to past scripts or use a search engine.
Re: Ask HN: Can I see your cheatsheet?
#133Set a huuuuuuuge shell history https://github.com/craigjperry2/dotfiles/blob/aa77ddcbde63bf... then fzf ctrl+r bindings mean you can recall anything right where you need it. If you’re going to do this then have an escape hatch for commands you don’t want memorised https://github.com/craigjperry2/dotfiles/blob/aa77ddcbde63bf...
History search is the way, especially with fzf. I love using fzf to pick git branches as well, so long as you use intelligible branch names :)
How do you use fzf for git branches? I didn’t know you could do that.
Re: Ask HN: Can I see your cheatsheet?
#134Kept them as blog posts: https://codeyarns.com/tech/index.html#cheatsheet
Re: Ask HN: Can I see your cheatsheet?
#135Re: Ask HN: Can I see your cheatsheet?
#136This is a great tool.
https://www.softwareok.com/?seite=Microsoft/QuickTextPaste
Re: Ask HN: Can I see your cheatsheet?
#137my only cheatsheets are customer-specific ... so they're basically unshareable (the general ideas of what's being done apply all over, but there's a lot of environment-specific stuff that I don't want to have to remember all the time :)
Re: Ask HN: Can I see your cheatsheet?
#138Earlier quoted context omitted.
Looks similar to https://github.com/tldr-pages/tldr
Very similar indeed. Seems the biggest difference is mainly the language the tool was written in.
I'm the author of `cheat`. The two tools are somewhat less similar than they initially appear, due entirely to poor documentation on my part.
If you're interested in a breakdown of the differences, I elaborated on this recently:
Re: Ask HN: Can I see your cheatsheet?
#139Earlier quoted context omitted.
History search is the way, especially with fzf. I love using fzf to pick git branches as well, so long as you use intelligible branch names :)
How do you use fzf for git branches? I didn’t know you could do that.
Re: Ask HN: Can I see your cheatsheet?
#140Earlier quoted context omitted.
How do you format them? Mine look very verbose, I don't like markdown at all, but since Gitlab/Github renders them, you can't use anything else...
Not sure I understand the question - I use code-blocks (```ls -alh```) or inline code (`ls -alh`). Everything else is comments and descriptions, what I am doing here. I don't really need rendering, most of the time I use Notepad++, or Typora, or my own Gitlab, or the markdown-text app in my nextcloud.
Maybe I do understand: I usually work from Windows, because I prefer the "frontend" over linux. However, all my work I do in WSL. Which allows me having multiple terminals open, multiple Linux OS etc. It is easy to copy&paste code. Perhaps it is not so easy doing everything with plain terminal in linux, e.g. vim, tmux (or, lets say, it requires a longer time to learn doing quick).