The Org table alignment markers "<l>", "<r>", "<c>" translate to the
markers in Markdown tables for left, right, center column alignment as
recognized by Blackfriday.
Fixes https://github.com/kaushalmodi/ox-hugo/issues/95
- Optimize code: Remove unnecessary progn, nested when
- Remove cruft from org-blackfriday-table about generating dummy
header. That code was ported from ox-gfm. But it gives error when
table has just 1 row. So commenting that out for now.
- Revisit that dummy header generation code at a later point.
- Make outshine work correctly in ox-hugo.el by NOT using the
alternative style ";; *" unknowingly in the comment header (instead
of ";;;;" style).
- Add missing newline in a test
- Now a post can have multiple aliases.
- If the specified alias doesn't have the section portion, it is
auto-derived from that post's section.
- To manually specify a section, include the "/" string in the
alias (see the tests in this commit for examples).
- Aliases are now always saved as TOML/YAML arrays.
Refactor:
- org-hugo--internal-tag-separator -> org-hugo--internal-list-separator
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
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
Puneeth Chaganti