Re: Long compile times on Windows 10 status
2016-10-18 2:32 GMT+02:00 Andrew Bernard : > 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:pant...@hotmail.com] > Sent: Monday, 17 October 2016 10:45 AM > To: 'Andrew Bernard' ; lilypond-user@gnu.org > 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\\.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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Long compile times on Windows 10 status
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:pant...@hotmail.com] Sent: Monday, 17 October 2016 10:45 AM To: 'Andrew Bernard' ; lilypond-user@gnu.org 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\\.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. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Long compile times on Windows 10 status
Hi Steven, I get the slow compile on every run. I believe this is a current development issue. Andrew On 17 October 2016 at 10:45, Steven Weber wrote: > 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\\.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. > > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
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\\.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. --Steven From: lilypond-user [mailto:lilypond-user-bounces+panteck=hotmail@gnu.org] On Behalf Of Andrew Bernard Sent: Sunday, October 16, 2016 4:42 PM To: lilypond-user@gnu.org Subject: Long compile times on Windows 10 status Hi folks, Although a dyed in the wool Linux user, I am experimenting with Windows 10. At 2.19.48 I am seeing the long compile times that have been mentioned, for every run. With 2.19.39 the compilation is normal and quite fast. [I picked this previous release at random, to simply get back somewhere before the current problem arose.] Running Windows 10 14393.321. What is the current status on this, and is there a workaround? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user