4 ms·
I think GP is suggesting it in other places, like replacing: #+STARTUP: indent #+OPTIONS: ^:nil With something more like: { "STARTUP" : ["indent"], "OP
by Jtsummers 5y ago
I think GP is suggesting it in other places, like replacing:
#+STARTUP: indent
#+OPTIONS: ^:nil
With something more like:
{ "STARTUP" : ["indent"], "OPTIONS" : { "^":null} }
That is, not using it to markup the document proper, but to encode all the various metadata bits in a more uniform notation.
I disagree that it's less clunky than the present situation, but it may be more consistent. I mean, you'd still need something to mark that some JSON follows and is separate from the other text in the document.
#+CONFIG: <JSON String>
S-expressions would make more sense, if we're sticking with emacs lisp anyways. But would still be clunkier than the current system at least for writers. Maybe better for people trying to implement org-mode (fully) in other systems.
- taeric 5y agoThe gp mentioned source blocks, so I picked up there. It looks like you and I are in agreement? That it may be more consistent, due to it always being json. But it hardly seems any better.
- Jtsummers 5y agoThey called out the results of source blocks, which you can already get in a variety of formats so JSON wouldn't be a bad option to add. But yes, we are in agreement. It wouldn't be much better for someone typing directly into org files. It's the same reason markdown and other formats get translated into HTML, heavyweight markups are annoying to type, even if consistent. It might be better for tooling around org-mode, but at that point you're pushing away from org files as plaintext entities meant to be directly edited and towards them being serialization formats you interact with through other programs.
- taeric 5y agoAh, so they did. Reading for the win. :)