-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
support repeated keywords in org mode files as arrays #11743
Comments
That's a breaking change. We'd need to support both. @kaushalmodi @niklasfasching Thoughts? |
Ah I apologize for my miscommunication. I meant to say One thing to note would be that the
|
I like it better than my It does remove the ability to specify multiline strings in org front matter I gueee. I never used hugo enough to have any idea whether that's something you want to keep. |
@jmooring what should be the next steps relating to this feature request? |
@augustfengd Testing with the current release and with your PR, it seems like the only functional improvement is to allow multi-word taxonomy terms. That alone I think is a valid reason to proceed. Note that this is a breaking change for those who have been ignoring this warning for the past 4.5 years:
Applicable to taxonomies named "tags", "categories", and "aliases", this:
...will produce a single term, while it used to produce two terms with a warning. I'll re-open the PR for review. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hello!
Could we be able to specify array values in org mode content over multiple lines instead of suffixing the keywords with
[]
. This would make the syntax less odd aesthetically (imo), and also allow terms to have spaces in them which is already the case for the other markup languages.I've accidentally and pre-emptively submitted an implementation when I should've created a proposal first.
The goal would be these two front matters are equivalent.
Thanks!
The text was updated successfully, but these errors were encountered: