Fixes#89
- Restore the default Org behavior of `#+TAGS`. Now that keyword (and
the `EXPORT_TAGS` property) is **not** used by `ox-hugo`.
- File-based exports must now use `#+HUGO_TAGS` to set the post tags.
- Subtree-based exports can use the `EXPORT_HUGO_TAGS` property to
override Org-style tags on the same headline (and the ones inherited
from Org-style tags from any of the parent subtrees and
`#+FILETAGS`).
- Note that for subtree-based exports, `#+FILETAGS` can be used to
set tags globally in the file. Earlier `#+TAGS` was used for
that purpose.
- Subtree-based exports can use the `EXPORT_HUGO_CATEGORIES` property
to override Org-style categories (tags with "@" prefix) on the same
headline (and the ones inherited from Org-style categories from any
of the parent subtrees and `#+FILETAGS`).
- Note that for subtree-based exports, `#+FILETAGS` can be used to
set categories (tags with "@") globally in the file.
** Why use #+FILETAGS and not #+TAGS??
- About `#+FILETAGS` -- [Tag Inheritance](http://orgmode.org/manual/Tag-inheritance.html)
- About `#+TAGS` -- [Setting Tags](http://orgmode.org/manual/Setting-tags.html)
=====
See https://ox-hugo.scripter.co/doc/tags-and-categories/
=====
This affected subtree-based post exports where a post subtree heading
was immediately followed by that post's sub-heading.
Example:
* Post heading
<snip EXPORT_FILE_NAME property>
** Post sub-heading
Fixes#87
Unrelated:
- Rename gen_test_md target in Makefile to just md
- Add gen_test_md target to the Makefile for just generating the
Markdown files, and not doing checks.
- Use the doc Org macro in the documentation.
- Add more tests! and make the supercool use of NoWeb and ":export
results" ":results output replace" to prevent copy-pasting the same
code blocks between tests and documentation.
- Had to mark org source blocks as safe in setup-ox-hugo.el for
tests to pass and docs to generate using the "test" and "doc"
Makefile targets.
`org-hugo-slug' earlier stripped off only the `code' HTML tag (`<code>
.. </code>') from the input string, if present.
Now it does that for *any* HTML tag, like `span' (only inside
`org-hugo-slug' when deriving the slug string). For example, `<span
class="timestamp-wrapper"><span class="timestamp"><2017-10-11
Wed></span></span>'.
Move ox-hugo_export-gh-doc function to its own file (so that only that
file needs to be evaluated if that function needs to be run directly
from within Emacs, without doing "make doc").
Now ox-hugo by default requires text, to be sub/super-scripted, to
be wrapped in {}.
So now "a_b" will be exported as "a_b", but "a_{b}" will be exported
as "a<sub>b</sub>". To revert back to the earlier behavior, user needs
to add "#+OPTIONS: ^:t" to their Org file.
Kaushal Modi