From: Ihor Radchenko <yantar92@posteo.net>
To: Jonathan Gregory <jgrg@autistici.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
"Victor A. Stoichita" <victor@svictor.net>,
emacs-orgmode@gnu.org
Subject: Re: [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?)
Date: Sat, 29 Jul 2023 07:16:09 +0000 [thread overview]
Message-ID: <87pm4bp4qu.fsf@localhost> (raw)
In-Reply-To: <87o7jwazmn.fsf@autistici.org>
Jonathan Gregory <jgrg@autistici.org> writes:
> The basic-mode term is not very helpful. Perhaps
> [inline/cropped/embedded]-mode would have been more descriptive in
> terms of what it does.
Sounds reasonable. I like "inline-mode", although no strong opinion.
> ... Anyway, hard-coding paper settings would
> simplify things a bit, but I'm not sure that hard-coding the
> version is a good idea and may produce errors with older
> installations.
Do people have reasons to use older versions even when they could use
the newest?
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.
>> #+name: test
>> #+begin_src emacs-lisp
>> (message "This is test")
>> #+end_src
>>
>> #+begin_src emacs-lisp :prologue (org-sbe test)
>> (+ 1 2)
>> #+end_src
Correction: `org-sbe' will execute src block. So, my example is not
completely accurate. Getting src block body is still doable, but a tiny
bit more tricky:
#+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)
> Interesting. I didn't know about org-sbe. Looks useful. I'll look
> into it when I find time. In the meantime, we can use:
>
> #+PROPERTY: header-args:lilypond :noweb yes :exports results
> :prologue (org-sbe version-and-paper)
(This will work because ob-org, by accident, produces body as result of
evaluation, with default header args)
--
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>
next prev parent reply other threads:[~2023-07-29 7:38 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 15:13 Moving some lisp/ob-*.el files to org-contrib - your advice? Bastien
2021-05-03 17:49 ` Timothy
2021-05-03 18:05 ` Bastien
2021-05-03 19:36 ` Palak Mathur
2021-05-03 19:44 ` Timothy
2021-05-03 19:47 ` Palak Mathur
2021-05-03 20:34 ` Bastien
2021-05-03 20:33 ` Bastien
2021-05-04 7:55 ` Eric S Fraga
2021-05-19 3:36 ` Jack Kamm
2021-05-03 20:52 ` Victor A. Stoichita
2021-05-04 10:19 ` Dr. Arne Babenhauserheide
2021-05-04 11:28 ` Bastien
2021-05-04 18:38 ` Victor A. Stoichita
2023-07-12 13:40 ` [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?) Ihor Radchenko
2023-07-12 22:35 ` Jonathan Gregory
2023-07-13 6:52 ` Dr. Arne Babenhauserheide
2023-07-13 10:08 ` Ihor Radchenko
2023-07-13 11:04 ` Jonathan Gregory
2023-07-14 12:38 ` Jonathan Gregory
2023-07-14 13:15 ` Dr. Arne Babenhauserheide
2023-07-14 13:52 ` Ihor Radchenko
2023-07-14 18:06 ` Ihor Radchenko
2023-07-17 17:02 ` Jonathan Gregory
2023-07-18 9:38 ` Ihor Radchenko
2023-07-19 12:17 ` Jonathan Gregory
2023-07-20 7:13 ` Ihor Radchenko
2023-07-20 17:53 ` Jonathan Gregory
2023-07-21 7:36 ` Ihor Radchenko
2023-07-21 11:38 ` Jonathan Gregory
2023-07-22 8:12 ` Ihor Radchenko
2023-07-25 16:16 ` Henrik Frisk
2023-07-25 16:26 ` Henrik Frisk
2023-07-25 17:17 ` Jonathan Gregory
2023-07-25 21:40 ` Henrik Frisk
2023-07-25 17:29 ` Jonathan Gregory
2023-07-26 8:15 ` Ihor Radchenko
2023-07-26 12:35 ` Jonathan Gregory
2023-07-27 7:21 ` Ihor Radchenko
2023-07-27 12:42 ` Jonathan Gregory
2023-07-28 7:37 ` Ihor Radchenko
2023-07-28 14:02 ` Jonathan Gregory
2023-07-29 7:16 ` Ihor Radchenko [this message]
2023-07-31 11:14 ` Jonathan Gregory
2023-07-31 11:58 ` Ihor Radchenko
2023-07-31 12:42 ` Jonathan Gregory
2023-08-08 13:01 ` Ihor Radchenko
2023-08-10 11:05 ` Jonathan Gregory
2023-08-11 7:04 ` Ihor Radchenko
2023-08-15 7:33 ` Henrik Frisk
2023-08-15 10:41 ` Ihor Radchenko
2023-08-15 15:57 ` Henrik Frisk
2023-08-15 16:04 ` Ihor Radchenko
2023-08-16 12:54 ` Jonathan Gregory
2023-08-17 10:26 ` Ihor Radchenko
2023-08-19 12:56 ` Jonathan Gregory
2023-08-20 7:20 ` Ihor Radchenko
2023-08-20 12:47 ` Jonathan Gregory
2023-08-20 13:46 ` Dr. Arne Babenhauserheide
2023-08-21 7:48 ` Ihor Radchenko
2023-07-13 6:33 ` [BUG] WORG example for ob-lilypond is no longer working as described Dr. Arne Babenhauserheide
2023-07-13 7:03 ` Dr. Arne Babenhauserheide
2023-07-13 8:03 ` Jean Abou Samra
2023-07-16 12:21 ` Graham King
2023-07-16 12:30 ` Ihor Radchenko
2021-05-04 11:32 ` Moving some lisp/ob-*.el files to org-contrib - your advice? Bastien
2021-05-03 22:19 ` Tim Cross
2021-05-03 23:15 ` Bastien
2021-05-04 10:19 ` Dr. Arne Babenhauserheide
2021-05-04 11:10 ` Bastien
2021-09-26 8:17 ` Bastien
2021-05-06 9:19 ` Jean Louis
2021-05-06 9:39 ` Bastien
2021-05-14 18:23 ` Greg Minshall
2021-05-17 16:39 ` Greg Minshall
2021-09-26 12:50 ` Bastien Guerry
2021-10-02 17:11 ` Bastien Guerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm4bp4qu.fsf@localhost \
--to=yantar92@posteo.net \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=jgrg@autistici.org \
--cc=victor@svictor.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).