Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org-columns and EXPORT_HUGO_SECTION* #615

Closed
johanwk opened this issue Apr 7, 2022 · 4 comments · Fixed by #616
Closed

org-columns and EXPORT_HUGO_SECTION* #615

johanwk opened this issue Apr 7, 2022 · 4 comments · Fixed by #616

Comments

@johanwk
Copy link

johanwk commented Apr 7, 2022

Regarding https://ox-hugo.scripter.co/doc/hugo-section/ and the use of EXPORT_HUGO_SECTION* for path fragments,

The use of * in the name of this org property doesn't work with org-columns for showing an overview of properties. Or, at least I haven't been able to use the property with an asterisk in its name in a #+columns: specification -- the value of the property is not shown.

Maybe an alias for EXPORT_HUGO_SECTION* could be introduced?

@kaushalmodi
Copy link
Owner

@johanwk Can you please give some more context?

  1. Please share a minimal Org file showing what you are trying to do.
  2. Also share what you expect that Org file to export as (expected Md file content, Md file location)

I haven't used org-columns or #+columns. So I don't understand what that has to do with EXPORT_HUGO_SECTION*.

@kaushalmodi
Copy link
Owner

@johanwk OK, I see.. So if I add this to the top of an Org file:

#+columns: %30ITEM %TODO %EXPORT_HUGO_SECTION* %TAGS

and then do C-c C-x C-c with the point being before the first heading in the file, I don't see the full concatenated section path.

That's because EXPORT_HUGO_SECTION* is not a "normal" property. ox-hugo concatenates the value of that special property from all the parent headings to derive the full section path.

So even if I aliased that property name to some "foo" property, it wouldn't work, because that whole section path is derived only at the time of export and not saved in one single property.

@johanwk
Copy link
Author

johanwk commented Apr 7, 2022

Right .. but I think it would be good enough to just see the literal value of the EXPORT_HUGO_SECTION* property. It's not that important to see the concatenated path that is assembled on export, since the column view will make that fairly easy to see anyway.

At least in my version of org-mode (9.5.2), the value of an EXPORT_HUGO_SECTION* is not shown in the column view.

kaushalmodi added a commit that referenced this issue Apr 7, 2022
This allows users to change the special property
`EXPORT_HUGO_SECTION*` to a string of their choice
e.g. `EXPORT_HUGO_SECTION_FRAG`.

Fixes #615.
kaushalmodi added a commit that referenced this issue Apr 8, 2022
This commit is marked as a "feature" because now you can view/edit
Hugo section fragments easily in Org Column view.

If you are an ox-hugo user affected by this breaking change, simply
replace all instances of "EXPORT_HUGO_SECTION*" with
"EXPORT_HUGO_SECTION_FRAG" in your Org files.

See https://ox-hugo.scripter.co/doc/deprecation-notices/#export-hugo-section-frag
for details.

Fixes #615.
@kaushalmodi
Copy link
Owner

@johanwk Please replace all occurrences of EXPORT_HUGO_SECTION* with EXPORT_HUGO_SECTION_FRAG in your Org files.

See https://ox-hugo.scripter.co/doc/deprecation-notices/#export-hugo-section-frag for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants