From: Jonathan Gregory <jgrg@autistici.org>
To: Ihor Radchenko <yantar92@posteo.net>
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: Thu, 27 Jul 2023 09:42:51 -0300 [thread overview]
Message-ID: <875y65cy0r.fsf@autistici.org> (raw)
In-Reply-To: <87a5vh95wg.fsf@localhost>
On 27 Jul 2023, Ihor Radchenko wrote:
> Jonathan Gregory <jgrg@autistici.org> writes:
>
>>> Ok. That fix has been already installed.
>>> https://git.sr.ht/~bzg/worg/commit/6f69d212f41bc372426dc9b4df286638fe8f2a92
>>
>> To the extent of the lilypond.org file, yes, but only if the
>> output is a PDF. My suggestion is to revert that commit and
>> incorporate the changes into ob-lilypond.
>
> Then, may you elaborate what purpose the changes are going to
> serve? Automatic page sizing? Automatic page settings?
Bug fix.
>> The purpose of the patch was to fix the problem described in
>> https://masto.ai/@rfc1149/110674961710491363. I wasn't trying
>> to introduce anything new.
>
> If we want to add boilerplate code to ob-lilypond, it does sound
> like introducing something new. Again, I feel confused. Please,
> explain in more details what you want to archive in terms of
> functionality.
No, the patch is a bug fix. There are no changes for the user.
Prior to the bug, we were able generate a "cropped" image when
running:
#+begin_src lilypond :file myfile.pdf
\version "2.20"
\paper { tagline="" }
{
c' e' g' e'
}
#+end_src
This is no longer the case, hence the patch.
>> No, the ob-lilypond patch is needed. It allows users to
>> generate music fragments (as opposed to a full page) in basic
>> mode using pdf, eps, and png.
>
> May your please explain what is "basic mode".
Basic mode is explained in
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html.
In summary:
With basic-mode you can embed LilyPond snippets into an Org-mode
file, compile and export them using typical Org-mode commands
(such as C-c C-e l p for PDF export). This is useful if you want
to mix blocks of LilyPond-generated score with text, and perhaps
other images to export to LaTeX, Docbook, PDF, or HTML.
> And what about users who do want a full page?
In that case the user would use "arrange mode", which is also
explained in the ob-doc-lilypond.html page. Try running the source
block example above with arrange-mode enabled using M-x
org-babel-lilypond-toggle-arrange-mode. To quote from that page:
With arrange-mode you can develop complete pieces of score whilst
organizing sections of the piece using typical literate
programming techniques. This allows you to assemble scores
programatically by using tables to store information among other
methods.
> Noweb and babel references are not allowed in header args. And
> ob-emacs-lisp also does not support :prologue.
I see, so there's no built-in way to auto-insert a boilerplate
without using the <<>> reference *inside* source blocks. Anyway,
let's not worry about this for now.
--
Jonathan
next prev parent reply other threads:[~2023-07-27 14:13 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 [this message]
2023-07-28 7:37 ` Ihor Radchenko
2023-07-28 14:02 ` Jonathan Gregory
2023-07-29 7:16 ` Ihor Radchenko
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=875y65cy0r.fsf@autistici.org \
--to=jgrg@autistici.org \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=victor@svictor.net \
--cc=yantar92@posteo.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).