- Add test for JSON output creation
- Add single.json in bare_min layouts/_default for this testing purpose
- Update debugprint.html partial to pretty-print the outputs Param
- Add <!--endtoc--> comment at end of Org-inserted TOC's.
That acts as an aid to help filter out the TOC from Hugo
summaries. See the new test added in this commit for example:
https://ox-hugo.scripter.co/test/posts/no-toc-in-summary
This commit changes the TOC style quite a bit from the earlier
version. Read the below mini-blog-in-commit for more info.
- Add new function org-hugo--get-headline-number
- org-hugo-heading - Use above.
- org-hugo--build-toc - Generate unordered list instead of ordered
- Update/add tests!
@punchagan: You are most likely one of the few affected by the
backward incompatible change in this commit. To get sort of the old
style of numbered headings in TOC (while unnumbered headings in post
body), set `num' to `onlytoc`. Let me know how it works.
=== mini blog ===
Earlier, the TOC was exported as ordered list in Markdown. That
imposed a limitation that allowed exporting only the last number from
a section number.
So instead of:
1. Section 1
1.1 Section 1.1
1.2 Section 1.2
It would export as:
1. Section 1
1. Section 1.1
2. Section 1.2
Now the TOC is generated as an *unordered* list in Markdown.
- 1. Section 1
- 1.1 Section 1.1
- 1.2 Section 1.2
That would cause both bullets and numbers to show in HTML, so I am
using a nifty little trick I discovered in
https://github.com/kaushalmodi/ox-hugo/issues/93 to hide those
bullets **if the section numbers are present**.
In addition, I also wrap the section numbers in "section-num" class so
that user can choose to format them however they like using CSS (May
be even hide them).
===
Fixes https://github.com/kaushalmodi/ox-hugo/issues/76
- Add new defcustom org-hugo-export-with-section-numbers
- Default of this option is set to 'onlytoc
- So there will be no numbers in the body of the exported post. But
if TOC (Org) is enabled, the items will be numbered.
This is part 1 of a multi-part patch series to make the num and toc
options work together the "right way".
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.
`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").
Kaushal Modi
Puneeth Chaganti