Align Org tags and hugo tags #89
Comments
|
That's a valid point. I'll add fixing this the first thing on my list. |
|
To be clear, it will make more sense to apply this breaking change only to subtree based exports. I am assuming you are using subtree-based exports? |
|
Yes definitively. Along those lines, it would make a lot of sense to have the hugo section inherit from a subtree's property, too. This way I could use headings for different content types. |
Sorry, I didn't follow that. Can you open a new issue with an example of your use case? |
|
Sure. |
|
See #90 |
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)
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/ =====
|
@simonthum Please update from the master and try again (Melpa update should also be out in few hours). See https://ox-hugo.scripter.co/doc/tags-and-categories/ for details. |
|
Seems to work great. Thank you very much! |
I like to use the TAGS line to populate the list of tags I have available on a per-file basis. E.g.:
However, ox-hugo puts them on all posts. IMO this is what
would do in org-mode (see http://orgmode.org/org.html#Tag-inheritance). The point of the TAGS line is to merely have such idiosyncratic blog tags available in the tag editor (you can assign keys too).
The text was updated successfully, but these errors were encountered: