basics/tree.md

@@ -1,6 +1,6 @@
 ---
 title: "tree"
-tags: [ "basics", "tree", "markdown" ]
+tags: [ "basics" ]
 ---
 
 The `tree` utility outputs a full listing of everything in your current directory, and those below.
@@ -23,14 +23,3 @@ README.md
 ```
 
 Each description-line starts with a tab.
-
-## Markdown Conversion
-
-To represent a file structure as a nested series of markdown lists, you can try this horrifying `sed` one-liner:
-
-```bash
-tree -tf --dirsfirst --gitignore --noreport --charset ascii  | \
-    sed -e 's/| \+/  /g' \
-    -e 's/[|`]-\+/ */g' \
-    -e 's:\(* \)\(\(.*/\)\([^/]\+\)\):\1[\4](\2):g'
-```

data/git/hooks.md

@@ -1,29 +0,0 @@
----
-title: "git hooks"
-tags: [ "Documentation", "data", "git" ]
----
-
-Check out the sample hooks:
-
-```bash
-cd $GIT_REPO
-ls .git/hooks
-head .git/hooks/pre-commit.sample
-```
-
-Add a hook to check the shell scripts in `$GIT_REPO` before making a commit:
-
-```bash
-echo '#!/bin/sh
-shellcheck *.sh' > .git/hooks/commit-msg
-chmod u+x .git/hooks/commit-msg
-```
-
-## Committing
-
-Your `git hooks` will not enter the repository, but you can commit them to a repository, then request others add these git hooks to their own branch, by putting a note in the project's `README.md`.
-
-```markdown
-The project comes with recommended git hooks.
-You can activate the hooks with `git config core.hooksPath hooks`.
-```

data/sqlite.md

@@ -1,21 +0,0 @@
----
-title: "sqlite"
-tags: [ "Documentation", "data" ]
----
-
-Work with a database:
-
-```bash
-sqlite3 "$FILE".sqlite3
-```
-Compress the database:
-
-```sqlite
-pragma vacuum;
-```
-Optimize the database:
-
-```sqlite
-pragma optimize;
-```
-

new.sh

@@ -14,7 +14,7 @@ filePath="$category/$(echo $name | sed 's/ /_/g').md"
 
 tagsList="$(echo \"$category | sed 's#\/#", "#g')\""
 
-[ -e "$filePath" ] && $EDITOR "$filePath" && exit 0
+[ -e "$filePath" ] && $EDITOR $filePath && exit 0
 
 echo "---
 title: \"$name\"