Many thanks - yes, that's what it was. I'm using VSCode and its Lilypond extension, and I had installed the vscode-pdf viewer, which clashed with my LaTeX-Workshop extension, which has its own PDF viewer in it. Anyway, after a bit of fiddling and a few VSCode restarts I was able to use the LaTeX pdf viewer for the Lilypond output. All good now!
As it's now 1am, and I have been wrestling with some 17th century music (full of huge leaps and multiple changes of clef), time for whisky... and sleep! Thank you again, Alasdair On Sun, May 24, 2020 at 11:56 PM Phil Holmes <[email protected]> wrote: > You get this sort of error if the PDF from the previous compilation is > still open in many PDF viewers - they lock the file. Try closing your PDF > viewer and trying again. > > -- > Phil Holmes > > > > ----- Original Message ----- > *From:* Alasdair McAndrew <[email protected]> > *To:* lilypond-user Mailinglist <[email protected]> > *Sent:* Sunday, May 24, 2020 1:43 PM > *Subject:* A fatal error with a new installation > > I have just installed Lilypond on Windows 10, following the instructions > to basically download, install, and add its path to the environment > variable. > > However, it won't compile; on a simple file; the log finishes with: > > warning: `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 > -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 > > -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -dAutoRotatePages=/None -dPrinted= > false -sOutputFile=/Users/amca/Lilypond/Butler_divisions_D_major.pdf > -c.setpdfwrite -f./tmp-lilypond-c5ihri)' failed (1) > > fatal error: failed files: > "C:\\Users\\amca\\Lilypond\\Butler_divisions_D_major.ly" > > > When I changed the name of the file it compiled once, and then wouldn't > compile again - it threw the same error message. > > As I say, this is a new installation - just installed this afternoon, and > there were no previous versions of Lilypond on this system. I've checked a > few times, and the only way I can get a new compilation is to rename the > file. > > What's going on here and how can I fix it? > > Thanks, > Alasdair > > -- > https://numbersandshapes.net > > -- https://numbersandshapes.net
