~tagglink/node

c45217c5791d9a6a6d1c61b3b8b6c9f8868519c5 — Tomas Granlund 2 years ago 7416d9f
fixed the readme
1 files changed, 6 insertions(+), 4 deletions(-)

M README.md
M README.md => README.md +6 -4
@@ 38,9 38,11 @@ Clang is the most accessible C compiler for windows users and the one I use, but
Each line in the tree file is parsed in the following way:
1. The number of `<` characters at the beginning of the line is the depth of the nav entry.
2. The first non-`<` character is the start of the Title of the nav entry.
3. The last sequence of non-whitespace characters before the newline is the file entry. This will be interpreted as one of two things:
  1. If the file entry ends with `.md`, the file is parsed as Markdown and the resulting HTML file is the `href` target for this nav entry.
  2. Otherwise the file entry is directly interpreted as the `href` target for this nav entry.
3. The last sequence of non-whitespace characters before the newline is the file entry.

The file entry will be interpreted as one of two things:
1. If the file entry ends with `.md`, the file is parsed as Markdown and the resulting HTML file is the `href` target for this nav entry.
2. Otherwise the file entry is directly interpreted as the `href` target for this nav entry.

The file given to `-h` must contain two occurrences of `%s`, where the first will be replaced by the note's title, and the second with the site's nav.



@@ 66,7 68,7 @@ Example `head.html`:
```

Example `foot.html`:
````html
```html
  </main>
  <footer>
    <a href="https://sr.ht/~MeOnSourcehut/"><img src="/res/sourcehut.svg"></a>