It's conventional to write a shortcode with a space after the starting
"{{<" (or "{{%") characters and a space before the ending pairs.
So do:
{{< SHORTCODE >}}
Not:
{{<SHORTCODE>}}
This commit makes that space insertion consistent for the exported
figure and highlight shortcodes.
For a reason unknown, if we have:
* Post title :good:
:PROPERTIES:
:EXPORT_FILE_NAME: post-title
:END:
** Post sub-heading :bad:
Note that the sub-heading is *immediately* after the post heading
(of course, not counting the property).
then (org-entry-get (point) "ALLTAGS") will return ":good:bad:"!
But if we have:
* Post title :good:
:PROPERTIES:
:EXPORT_FILE_NAME: post-title
:END:
Anything here but not an Org heading (even empty line works).
** Post sub-heading :bad:
then (org-entry-get (point) "ALLTAGS") will return
":good:", as expected.
This commit ensures that the "bad" tag does not leak into the post
front-matter if the first case above happens (even though that case
is rare).
- 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.
Kaushal Modi