* ox-hugo.el:
- Obsolete org-hugo-export-subtree-* functions and replace them with
org-hugo-export-wim-* (What I Mean) functions. See the doc string
of org-hugo-export-wim-to-md for details.
- Fix the return values of org-hugo-export-as-md,
org-hugo-export-to-md, org-hugo-publish-to-md and the new
org-hugo-export-wim-to-md. Update their doc strings.
- (org-hugo-export-wim-to-md): This new function now exports using
per-file flow or per-subtree flow automatically. Improve the
messages printed during export.
- (org-hugo-export-to-md): Allow Org files exported using per-file
approach not get exported based on tags. See "Marking files to not
be exported" in documentation for details.
- (org-hugo-publish-to-md): Comment out this function. It doesn't
work (If someone was using it, please open an issue so that I can
uncomment that.)
* setup-ox-hugo.el:
- New function org-hugo-export-all-wim-to-md that uses the new
org-hugo-export-wim-to-md function.
- Stop printing too many messages when loading emacs.
- Increase org-export-headline-levels to 4.
- Don't export files and subtrees tagged
"dont_export_during_make_test" during "make test".
* Makefile:
- Now uses the new org-hugo-export-all-wim-to-md function
defined above, and thus no need to hard-code subtree-based and
file-based Org files.
- New rule do_test replaces the old test_subtree and test_file
rules.
- New rule md1 replaces the old mdtree and mdfile rules.
* ox-hugo-manual.org:
- Add section on "Marking files to not be exported"
- Update "Auto-export on Saving" to reflect the refactoring to
org-hugo-export-wim-* functions.
- Update bindings descriptions.
* Misc tests: Make changes to match the above changes.
This commit helps towards
https://github.com/kaushalmodi/ox-hugo/issues/39. Now Org files can be
exported seamlessly using the per-file or per-subtree flow using a
Makefile like one in this repo.
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
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
Ryan McGuire