-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make lyluatex process LilyPond snippets in parallel #311
Comments
The idea is very good in itself. Nevertheless, I’m not sure I’d like to implement it:
|
@lemzwerg After looking further at this, it turned not to be so complicated as I feared. I took the occasion to make a switch I had thought about for quite a while: switching to MoonScript, that’s a more concise and readable lua dialect. May you please test with the parallel branch, and tell me what you think about it? After enhancing it, I think I’d release a lyluatex v2.0, as it’s quite a big change in the way lyluatex works. |
Sorry for the late reply. I use the new versions of
in the main document. However, it fails soon with
Am I missing something? |
Would you please have a MWE ? On which platform do you run LilyPond / LuaLaTeX ? |
Unfortunately, I currently don't have time to produce an MWE. However, I will send you the project privately, maybe this helps. I'm running on GNU/Linux; however, there's nothing in the project that should prevent compilation on Windows, say (I actually did this a few years ago but haven't tested it recently with the latest updates to both the LilyPond and lyluatex code). |
Thank you for the document. I get the same problem : I’m investigating on my free time, and will tell you what I find. |
While Lua itself isn't multi-threaded, it has 'coroutines', and using them it should be possible to emulate
lilypond-book
behaviour, I think: If a new lyluatex optionparallel=<n>
(or whatever) is set,lualatex
won't wait for the result of LilyPond for alilypond
environment but simply spawns a LilyPond process up to n times. This would enormously speed up everything, at the cost of running lualatex at least twice.The text was updated successfully, but these errors were encountered: