Jonathan Gregory <j...@autistici.org> writes: >> For example, python2/3 or MathJax4,4- were breaking and some >> people were relying on legacy code. So, we had to provide some >> extra versions checks and toggles on Org side as well. > > We're talking about different things here. Lilypond needs the > \version to upgrade the syntax. IIUC this makes it possible for a > future version to compile input code correctly, even if it was > written in a previous version (which may have used some different > syntax), as long as the \version is included in the main file. > There's even a `convert-ly` command to make upgrades based on the > \version, so I'd suggest moving only \paper settings to the > ob-lilypond file and keeping the \version in the source file.
May it be possible to mix multiple \version commands? So that we declare \version for \paper and user can declare other \version for the code block body. >> #+begin_src emacs-lisp :prologue (org-babel-ref-resolve >> "test[]") >> (+ 1 2) >> #+end_src >> >> It think that it will be logical to add reference resolution to >> :prologue/:epilogue. I will see what I can do. (I may need to >> look through which header args are resolved and which are not - >> there seems to be no consistency) > > What do you mean by reference resolution? #+begin_src emacs-lisp :prologue test[] -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
