I use "cheat" to help with less-used options for *NIX commands, probably similar to what you're doing. You create a separate "cheat sheet" for each command (7z, ant, etc.) and then "cheat 7z" dumps it to the console so you can cut-and-paste what you need.
I have automation around the downloading of pdfs that interest me and the production of man pages to pdfs. Gradually I'm developing conventions around format and so on, but it's pretty idiosyncratic, as you can imagine.
Comments
I have a git repo with work notes in.
It all goes in there:
300 folders and counting...I use "cheat" to help with less-used options for *NIX commands, probably similar to what you're doing. You create a separate "cheat sheet" for each command (7z, ant, etc.) and then "cheat 7z" dumps it to the console so you can cut-and-paste what you need.
https://github.com/chrisallenlane/cheat
So far I've relied on grep, but I like that idea and will likely implement it.
How do you manage this repository? Have auto-commits, auto-pushing, auto-anything?
I have automation around the downloading of pdfs that interest me and the production of man pages to pdfs. Gradually I'm developing conventions around format and so on, but it's pretty idiosyncratic, as you can imagine.