Closed marczellm closed 7 years ago
Thank you for the report, I hadn't run into this so far.
To start pinning it down:
lilyDynamics
or twoBeamedQuavers
or \lilyText
Obviously the issue is when loading a glyph by its name.
I suspect this code in core/genericAccess.inp
\ifluatex
% ...
\def\lilyGetGlyph#1{\directlua{documentdata.fontchar "#1"}}
\fi
to be the culprit but currently don't have a clue how to fix the issue. @davebellows do you have an idea?
So the bug is fixed, but I can't tell for sure when it will be in the CTAN version (and when it will be available in TeXLive etc.
I use LuaTeX 1.0.4 on MiKTeX on Windows 10 x64, and the CTAN version of
lilyglyphs
.When I compile
I get an error saying