I noticed that several reported lyluatex issues are related to MiKTeX, especially on Windows. The recurring problems seem to involve process execution, command quoting, paths with spaces, and interaction between LuaTeX, LilyPond, Ghostscript, and MiKTeX.
I do not currently have a Windows/MiKTeX setup myself, so I cannot properly test these cases locally.
To make progress, I created a separate branch:
This branch contains experimental changes in lyluatex.lua intended to make process handling more MiKTeX-friendly. In particular, process pipes are routed through LuaTeX’s os.kpsepopen when available, with a fallback to io.popen.
Important note: the lua file should be placed in ~/texmf/scripts/lua/lyluatex/, not in ~/texmf/tex/lualatex/lyluatex/.
The goal is not to claim that MiKTeX support is fixed yet, but to create a test branch where affected users can help verify whether this approach improves the situation.
What I would like MiKTeX users to test
If you previously reported or encountered MiKTeX-related lyluatex problems, please try the miktex branch and report whether it changes anything for your case.
In particular, please test whether:
- LilyPond is found and started correctly;
- paths containing spaces still work;
- your normal lyluatex document compiles;
- scores are generated and included correctly;
- any previous MiKTeX-specific error message changes or disappears.
Please include:
- Windows version;
- MiKTeX version;
- LuaTeX version;
- LilyPond version;
- Ghostscript version, if relevant;
- the exact command used to compile;
- the relevant
.log output;
- whether the same document works with the current
master branch.
How to test
Check out the branch:
Then use the lyluatex.lua from that branch in your local test setup and compile your document as usual.
If possible, please also test a document located in a path with spaces, for example somewhere below:
C:\Users\<Your Name>\Documents\...
and, if applicable, a LilyPond installation path with spaces.
Current status
The branch has been smoke-tested on Linux/TeX Live, but not yet on Windows/MiKTeX.
I will keep applying focused changes to this branch based on feedback. Once we have a robust solution that works for affected MiKTeX users and does not regress TeX Live setups, I intend to merge the relevant changes back into master.
Thanks in advance to anyone willing to test this. I need help from actual MiKTeX/Windows users to make this reliable.
Related MiKTeX/Windows issues:
I noticed that several reported lyluatex issues are related to MiKTeX, especially on Windows. The recurring problems seem to involve process execution, command quoting, paths with spaces, and interaction between LuaTeX, LilyPond, Ghostscript, and MiKTeX.
I do not currently have a Windows/MiKTeX setup myself, so I cannot properly test these cases locally.
To make progress, I created a separate branch:
This branch contains experimental changes in
lyluatex.luaintended to make process handling more MiKTeX-friendly. In particular, process pipes are routed through LuaTeX’sos.kpsepopenwhen available, with a fallback toio.popen.Important note: the lua file should be placed in
~/texmf/scripts/lua/lyluatex/, not in~/texmf/tex/lualatex/lyluatex/.The goal is not to claim that MiKTeX support is fixed yet, but to create a test branch where affected users can help verify whether this approach improves the situation.
What I would like MiKTeX users to test
If you previously reported or encountered MiKTeX-related lyluatex problems, please try the
miktexbranch and report whether it changes anything for your case.In particular, please test whether:
Please include:
.logoutput;masterbranch.How to test
Check out the branch:
Then use the
lyluatex.luafrom that branch in your local test setup and compile your document as usual.If possible, please also test a document located in a path with spaces, for example somewhere below:
and, if applicable, a LilyPond installation path with spaces.
Current status
The branch has been smoke-tested on Linux/TeX Live, but not yet on Windows/MiKTeX.
I will keep applying focused changes to this branch based on feedback. Once we have a robust solution that works for affected MiKTeX users and does not regress TeX Live setups, I intend to merge the relevant changes back into
master.Thanks in advance to anyone willing to test this. I need help from actual MiKTeX/Windows users to make this reliable.
Related MiKTeX/Windows issues:
lyluatextools.stynot found (MiKTeX) #258 — MiKTeX package/file layout issue involving missinglyluatextools.sty.extract_includepathscrash:bad argument #2 to 'gsub'.