Re: Long compile times on Windows 10 status

[Thomas Morley]

2016-10-18 2:32 GMT+02:00 Andrew Bernard <address@hidden>:
> Hi Steven,
>
>
>
> With 2.19.48 your suggestion did not work for me. With 2.19.49, it does.
>
>
>
> Since this is going to hit everybody, presumably, should it be documented in
> the manual somewhere folks?
>
>
>
> Can the Windows installer do something like this?
>
>
>
> I’m new to Windows, having previously led a trouble free life with Linux.
>
>
>
> Andrew
>
>
>
>
>
>
>
> From: Steven Weber [mailto:address@hidden
> Sent: Monday, 17 October 2016 10:45 AM
> To: 'Andrew Bernard' <address@hidden>; address@hidden
> Subject: RE: Long compile times on Windows 10 status
>
>
>
> I’ve found that whenever I install a new font on my computer, I wind up in
> this state.
>
>
>
> That being said, I can recover back to normal speeds by deleting the
> C:\Users\<me>\.lilypond-fonts.cache-2 folder.  The first build after doing
> this will be slow (because it’s rebuilding the font cache), but after that,
> speeds are back to normal.
>
>

In the german forum Manuela reports same problems.

Basically she found:

\paper {
#(define fonts
     (set-global-fonts
      #:music "gonville"  ; (the main notation font)
      #:roman "Traditional Arabic" ; (the main/serif text font)
      )
}

causing the slow down for windows even with 2.19.42.

If you understand german:
http://www.lilypondforum.de/index.php?topic=2397.msg13521#msg13521

Being on LINUX I obviously can't check, though I thought I share it
here, probably it helps...

Cheers,
  Harm