Good documentation should include two distinct elements - a Guide and an API:
- The Guide builds concepts, providing examples, etc.
GitBook is well suited to
| #!/bin/bash | |
| if [ -f ~/Library/KeyBindings/DefaultkeyBinding.dict ]; then | |
| echo "~/Library/KeyBindings/DefaultkeyBinding.dict already exists" | |
| exit -1 | |
| fi | |
| mkdir -p ~/Library/KeyBindings | |
| cat << EOF > ~/Library/KeyBindings/DefaultkeyBinding.dict | |
| { | |
| "₩" = ("insertText:", "\`"); |
Good documentation should include two distinct elements - a Guide and an API:
GitBook is well suited to
| #!/bin/bash | |
| # | |
| # git-mv-with-history -- move/rename file or folder, with history. | |
| # | |
| # Moving a file in git doesn't track history, so the purpose of this | |
| # utility is best explained from the kernel wiki: | |
| # | |
| # Git has a rename command git mv, but that is just for convenience. | |
| # The effect is indistinguishable from removing the file and adding another | |
| # with different name and the same content. |
| <?php | |
| /* | |
| * XSS filter, recursively handles HTML tags & UTF encoding | |
| * Optionally handles base64 encoding | |
| * | |
| * ***DEPRECATION RECOMMENDED*** Not updated or maintained since 2011 | |
| * A MAINTAINED & BETTER ALTERNATIVE => kses | |
| * https://github.com/RichardVasquez/kses/ | |
| * | |
| * This was built from numerous sources |