Re: Font trouble when compiling via Windows Subsystem for Linux

2018-06-17 Thread Aaron Hill
On 2018-06-16 20:08, Brent Annable wrote: Hi all, Some of you may remember my memory allocation error from a while ago: trying to compile a 200-page PDF using a 32-bit version of Lilypond on a 64-bit Windows 10 system caused it to run out of memory. I eventually solved the problem by running

Re: Font trouble when compiling via Windows Subsystem for Linux

2018-06-17 Thread Brent Annable
Hey Andrew, Yeah I tried that solution first, but got an error message when I tried to install Ubuntu the first time. I was at the height of my frustration at that point, so I rage quit and never went back to that solution. I think you’re right, I should probably reconsider it as this bash shell

Re: Font trouble when compiling via Windows Subsystem for Linux

2018-06-17 Thread Andrew Bernard
Hi Brent, Not to answer your question, but why don't you run full blown proper Linux under Virtualbox on Windows 10? This is what I do. Has large advantages. Andrew ___ lilypond-user mailing list lilypond-user@gnu.org

Font trouble when compiling via Windows Subsystem for Linux

2018-06-16 Thread Brent Annable
Hi all, Some of you may remember my memory allocation error from a while ago: trying to compile a 200-page PDF using a 32-bit version of Lilypond on a 64-bit Windows 10 system caused it to run out of memory. I eventually solved the problem by running Lilypond under the Windows Subsystem for Linux