On Sat 24 Dec 2016 at 20:02:43 (-0600), David Wright wrote: > On Sun 25 Dec 2016 at 10:51:15 (+1100), Andrew Bernard wrote: > > Same problem on Linux. I would class this as a defect - I would not expect > > to be restricted in music filenames due to clashes with internal files. No > > wonder it is not documented. > > This bug has either been introduced in 2.19, or it exists in lilyponds > downloaded/installed from lilypond.org but not in the distribution's > own version. Perhaps someone who runs 2.18.2 downloaded from the web > can ascertain which.
Correction... it's in Debian's 2.18.2 as well. I was fooled by the lack of satb.ly in that version, but suomi.ly triggers the same behaviour. Looking at the strace, I can't figure out why LP wants to search for all these filename patterns: stat64("/usr/share/lilypond/2.18.2/fonts/svg/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/type1/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or director y) stat64("/usr/share/lilypond/2.18.2/fonts/otf/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/scm/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ps/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ly/suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("suomi.ly.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/svg/suomi.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/type1/suomi.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/otf/suomi.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/scm/suomi.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ps/suomi.ly", 0xbfd04a10) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ly/suomi.ly", {st_mode=S_IFREG|0644, st_size=929, ...}) = 0 stat64("/usr/share/lilypond/2.18.2/fonts/svg/init.ly", 0xbfd04a80) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/type1/init.ly", 0xbfd04a80) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/fonts/otf/init.ly", 0xbfd04a80) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/scm/init.ly", 0xbfd04a80) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ps/init.ly", 0xbfd04a80) = -1 ENOENT (No such file or directory) stat64("/usr/share/lilypond/2.18.2/ly/init.ly", {st_mode=S_IFREG|0644, st_size=2780, ...}) = 0 write(2, "Processing `/usr/share/lilypond/"..., 52Processing `/usr/share/lilypond/2.18.2/ly/suomi.ly' It appears that once it has found the file /usr/share/lilypond/2.18.2/ly/suomi.ly it doesn't bother looking for suomi.ly. It appears that the simplest workaround is to give any sort of path to LP rather than a bare filename. The chances of LP finding /usr/share/lilypond/2.18.2/ly/anything/suomi.ly or /usr/share/lilypond/2.18.2/ly//anything/suomi.ly is effectively zero. Cheers, David. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user