- Rename org-hugo-publish-subtree to org-hugo-export-subtree-to-md to
fit the standard naming convention.
- Remove org-hugo-convert-region-to-md; does not seem necessary for
Hugo exporter.
@titaniumbones
Now,
- "C-c C-e H H" will work as old "M-x org-hugo-publish-subtree"
- "C-c C-e H A" will work as old "C-u M-x org-hugo-publish-subtree"
The rest of the change in this commit is indentation change and a very
old .md file that should have been deleted once the noexport feature
was implemented.
Use of ignoring errors thrown by org-back-to-heading:
You can add this to the posts Org file:
# Local Variables:
# eval: (add-hook 'after-save-hook #'org-hugo-publish-subtree :append :local)
# End:
.. and have the post subtree auto-export on each save, but also not
throw an error if you happen to save the file while the point was
above the top-most Org headline in the file.
- Add org-hugo--quote-string, org-hugo--get-valid-subtree,
org-hugo--get-post-subtree-coordinates
- Add examples to demonstrate how auto menu weight assignment works.
- 'name' is a separate 'identifier'-like Menu property. So use ":menu"
to get the menu entry 'name' (not to be confused with the menu 'name'
property!)
- Allow white space in menu entry 'name' (Example:
https://discourse.gohugo.io/t/working-with-multiple-menus-and-iterating-over-the-whole-set/7503)
- Refactor: menu-name(-str) -> menu-entry(-str) to prevent confusing
that with the menu name property.
- Remove 'children' from the list of settable Menu properties. As its
datatype is "Menu" and not "string" (from docs), I don't see that as
something a user would set. I believe, a user setting a menu parent
will mirror that menu entry as a child automatically in that parent
entry.
- Allow inheritance of HUGO_FRONT_MATTER_FORMAT property too.
- Add examples of white space use in ":menu" and ":name" for TOML and
YAML front matter
Now menu front matter data is specified as follows:
* Menu Alist Meta Data
:PROPERTIES:
:EXPORT_FILE_NAME: menu-alist-meta-data
:EXPORT_DATE: 2017-07-18
:EXPORT_HUGO_MENU: :name main :weight 80 :parent posts :identifier foo1
:END:
- Without the EXPORT_ prefix, those properties were as good as not
present; only the default values were exported.
- Hugo does not like slashes in dates; fix that
- Also add the resultant .md file
The option is set by the HUGO_CODE_FENCE property.
- If set to t (default), Markdown code fence is used.
- Else Hugo `highlight' shortcode is used.
Add examples.
This function replaces 2 older interactive functions:
org-hugo-export-current-subtree and org-hugo-walk-headlines
M-x org-hugo-publish-subtree will "do the right thing" when publishing
the current subtree.
C-u M-x org-hugo-publish-subtree will publish all the subtrees in the
document; but now the older limitation of posts to be level-1 headings
is removed.
This function tries to be intelligent; it will export only the current
or one of the parent subtrees that first is seen to contain the
EXPORT_FILE_NAME property. It does not simply export "the current"
subtree.
Also examples added to show how to exclude or comment out posts.
- Case where parenethesized text has leading/trailing spaces adjoining
the parentheses characters.
Earlier 'sluggifying' "Foo ( Bar ) Baz" resulted in 3 hyphens in the
slug string ("foo---bar---baz"). After this commit, those extra spaces
are removed in the slug generation process and so only 2 hyphens (as
expected) would be in the slug ("foo--bar--baz").
Also improve the doc-string of org-hugo--slug function.
Kaushal Modi
Matt Price