Everyone, On Mon, Jul 11, 2016 at 5:08 AM, Mojca Miklavec [via Lilypond] < ml-node+s1069038n192549...@n5.nabble.com> wrote:
> To answer to David: yes, it's one-time cost (that gets re-triggered > every now and then in order to be able to get a more recent database > including potential new fonts on the system, but I don't know the > "rule" of when this gets triggered). In any case, after the initial > 10-minute-waiting each lilypond processing is reasonably fast. > > In order to be able to reproduce the problem reliably I would have to > figure out where the font cache is stored and make sure to delete it. > > There is a folder > LilyPond.app/Contents/Resources/var/cache/fontconfig > but it is empty (which makes sense). > > There is > > ~/Library/Caches/org.lilypond.lilypond/com.apple.opencl/com.apple.ocl.32.{data|maps} > > which seems to be something else. > > I'm not yet sure where else to look for. > I've noticed this one-time startup delay as well on Windows (7 and 8) and found that it got triggered anytime I changed the contents of the system font folder (C:\Windows\Fonts), whether adding or deleting a file. At the next time of compiling a LilyPond file, a new font-cache database would be created in "C:\Users\[MYUSERNAME]\.lilypond-fonts.cache-2" (note the initial period in the directory name). If I clear the contents of this folder, the initial delay comes up again to create a new database file. I suspect that this directory can be found across OSs in a similar location in the user's main directory, but I haven't confirmed this. HTH, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Re-Lilypond-taking-forever-to-typeset-tp192544p192552.html Sent from the Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond