> On 26 Jan 2025, at 13:13, Jenifer Tribe <jonathan_tr...@hotmail.com> wrote: > > > Thanks Hans > I've not used the command line much, but something like this, for my old > 2.18.2 version: > > C:\Users\jenny\Documents\Music\Lilypond\Isaac\Palle palle>\"Program Files > (x86)"\LilyPond\usr\bin\lilypond.exe isaac-palle-parts.ly > <http://isaac-palle-parts.ly/> > > This compiles ok, but as you implied, doesn't produce the log file that the > double-click used to. With a new large piece I get a lot of typos (!) so > maybe I need to pipe the info from the cmd line to a logfile. Typos? Or just missing conversions?
Given that you’ve used an old version before there is a good chance that a lot of the signalled errors of 2.24 will be syntax-updates required by newer releases. So a first attempt on fixing would be to run convert-ly on it. On windows 11 you first need to get rid of the Microsoft magic of intercepting any attempt to run Python and instruct users to install the Python app from the store. On the command-line with Lilypond bin folder in your path running python —version would yield something like C:\Users\aikebah\Desktop>python --version Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases. if you (just like me) did not install a Python app from the store. After following the instructions and disabling the App Execution Aliases for python (and while at it python3) that should change to C:\Users\aikebah\Desktop>python --version Python 3.10.8 and then you can do the likes of python C:\path\to\lilypond\bin\convert-ly.py bla.ly or for convenience set CONVERTLY=path\to\lilypond\bin\convert-ly.py which allows you to use python %CONVERTLY% bla.ly <http://bla.ly/> which would yield output like convert-ly.py: Processing `bla.ly'... Applying conversion: 2.19.2, 2.19.7, 2.19.11, 2.19.16, 2.19.22, 2.19.24, 2.19.28, 2.19.29, 2.19.32, 2.19.39, 2.19.40, 2.19.46, 2.19.49, 2.20.0, 2.21.0, 2.21.2, 2.22.0, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12, 2.23.13, 2.23.14, 2.24.0 \version "2.24.0" { c' d' e' f' } which, by piping the output would allow you to save the updated version to a new file or if you include the `-e` flag to directly edit the file in-place C:\Users\aikebah\Desktop>python %CONVERTLY% -e bla.ly convert-ly.py (GNU LilyPond) 2.24.4 convert-ly.py: Processing `bla.ly'... Applying conversion: 2.19.2, 2.19.7, 2.19.11, 2.19.16, 2.19.22, 2.19.24, 2.19.28, 2.19.29, 2.19.32, 2.19.39, 2.19.40, 2.19.46, 2.19.49, 2.20.0, 2.21.0, 2.21.2, 2.22.0, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12, 2.23.13, 2.23.14, 2.24.0 after which there will be a backup (bla.ly~) of the original side-by-side with the file (bla.ly) that got its syntax updated with the changes that were to be made to the syntax due to the version-change.. (and if you never coded the \version “<your lilypond version” in the old scores you would get) C:\Users\aikebah\Desktop>python %CONVERTLY% -e bla.ly convert-ly.py (GNU LilyPond) 2.24.4 convert-ly.py: Processing `bla.ly'... convert-ly.py: error: bla.ly: Unable to determine version. Skipping convert-ly.py: warning: There was 1 error. in that case put a \version “<your old version>” (e.g. \version “2.18.2”) in your file and repeat the python-command > > Maybe I also need to move the lilypond files to somewhere more convenient so > I don't have quite so much typing to do! > > In trying to fix this problem generally, I set Path in the environment > variables. Perhaps I should remove this, though it's probably harmless. Extending the path with the lilypond bin folder would work fine (and allow, as done above, to also run the python.exe from the lilypond distribution by simply typing python), but for convert-ly you would need to specify the full path of the file… or use the additional environment variable trick > All the best > Jonathan > From: Hans Aikema <hans.aik...@aikebah.net <mailto:hans.aik...@aikebah.net>> > Sent: 26 January 2025 11:43 > To: Jenifer Tribe <jonathan_tr...@hotmail.com > <mailto:jonathan_tr...@hotmail.com>> > Cc: lilypond-user@gnu.org <mailto:lilypond-user@gnu.org> > <lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>> > Subject: Re: problem for windows 11 users > > > > On 26 Jan 2025, at 11:52, Jenifer Tribe <jonathan_tr...@hotmail.com > <mailto:jonathan_tr...@hotmail.com>> wrote: > > .., if there are any! > > It is no longer possible to doubleclick on a .ly file to compile a script. > Windows 11 cannot identify the specific program associated lilypond, so all > you see is an option to choose Lilypond 'Just once' followed by abject > failure. Windows only seems to recognise programs which they have classified > as apps, so no version appears in the list of default programs. > > Likely some corruption (most likely somewhere in the registry) on your > system. I still had a clean Windows 11 VM (normally work on the Mac), so I > downloaded 2.24.4, unzipped it to C:\Users\<mysuser>\lilypond-2.24.4 and had > the opportunity to set it to always and have compile-on-doubleclick. > > Fixing your system likely will need some Windows Registry wizardry as > Microsoft has fully restructured the way file associations are stored in the > registry, so unfortunately cannot assist you on where to look in the registry. > > In any case you’re likely better off with either direct command-line usage or > using tools like Frescobaldi, since you will loose all the error/warning > outputs lilypond might give in your current way-of-working. > When I deliberately put an error in my lilypond (not terminating a string) I > don’t have anything to go by to find out that lilypond complains about a too > early end-of-file whereas running it myself from the CMD prompt nicely show > me the errors that lilypond reports: > > %%% > C:\Users\aikebah\Desktop>\Users\aikebah\lilypond-2.24.4\bin\lilypond.exe > bla.ly <http://bla.ly/> > GNU LilyPond 2.24.4 (running Guile 2.2) > Processing `bla.ly <http://bla.ly/>' > Parsing... > bla.ly <http://bla.ly/>:1:10: error: end quote missing > \version > "2.24.0 > bla.ly <http://bla.ly/>:1: warning: no \version statement found, please add > > \version "2.24.4" > > for future compatibility > fatal error: failed files: "bla.ly <http://bla.ly/>" > %%% > > > A similar problem has been reported with jpg and png files not being > associated with Photos. There is apparently a repair option that can be > applied in that case. > There may be some manual work-round. It was working for me on a very old > Lilypond version, and only stopped when I upgraded to 2.24.2. Reverting to > the old version, that now has the same problem. > Jonathan
