4 ms·
I have a markdown file that I don't actually view in markdown, but rather in my editor so that the syntax colors can break things up be it sections (e.g. the ba
by strangelove026 6y ago
I have a markdown file that I don't actually view in markdown, but rather in my editor so that the syntax colors can break things up be it sections (e.g. the bash section v the git section). Further I'll write the command, and then write an explanation in the comment which is a different color.
I can do a ctrl + f for "_git_" and get to my git section straight away.
_git_
- git checkout $deleting_commit^ -- $deleted_file <!-- undelete $deleted_file, ^ will grab the previous commit before the $deleting_commit-->
- git checkout develop .circleci/scripts/feature_branch_deploy.sh <!-- pull in the develop version of feature_branch_deploy.sh -->
- git clean -f <!-- revert all local changes on branch -->
- git reset HEAD~ <!-- undo most recent local commit -->
- mraza007 6y agoWhat text editor do you use to do that. I have explored vimwiki to keep track of things i learn and it has been helpful but sometimes it gets harder to maintain sometimes (thats just a personal opinion)
- strangelove026 6y agoYeah I hear you. I usually just keep a combination of things that I use often and some of the more fringe commands that are useful and might take awhile to find again. I use VS Code with the atom one dark theme, but I have an atom onedark plugin installed on vim that gives me the same colors / functionality. This is the only thing in my .vimrc ``` syntax on colorscheme onedark ```