On Mon, May 31, 2021 at 10:03 AM Brian Barker <b.m.bar...@btinternet.com> wrote:
>
> At 09:17 31/05/2021 -0700, Knute Snortum wrote:
> >On Mon, May 31, 2021 at 8:25 AM Brian Barker wrote:
> >> At 09:31 31/05/2021 -0400, Tim Slattery wrote:
> >>>On 30 May 2021 at 17:50, JxStarks wrote:
> >>>>Hi Ralph,
> >>>>I read that documentation and tried it. I'm running Windows 10
> >>>>Pro, 10.0.19041 and I still get the same response: " 'convert-ly
> >>>>is not recognized...". Am I missing something obvious?
> >>>
> >>>I think so. The name of the file is convert-ly.py, ...
> >>
> >>Are you sure? In my Windows 10 installation of Lilypond 2.22.1, the
> >>only file called "convert-ly" (in C:\Program Files
> >>(x86)\LilyPond\usr\bin) has no extension. Is this an error?
> >>
> >>>When you type a command, the OS will look for a file of that name
> >>>with any of several extensions that it knows about: *.exe, *.bat,
> >>>*.cmd, *.lnk that sort of thing. It doesn't know about the *.py
> >>>extension, so you have to type it in as part of the command.
> >>
> >>Don't you first have to correct the name of convert-ly to what it
> >>should have been: convert-ly.py? Or what did I do wrong at
> >>installation time to cause this?
> >
> >I don't think you caused anything. I think it's this way in the
> >2.22 installation. I don't know if it's intentional or not.
> >
> >Since your system doesn't recognize python as an executable, you'll
> >have to launch it from python. Type "python --version" to see if
> >python is in your path. If so, type "python path\to\convert-ly ..."
> >or create a script.
>
> So (to answer the original enquirer's question) do we agree that the
> 2.22 documentation about the use of convert-ly under Windows at
> https://lilypond.org/doc/v2.22/Documentation/usage/invoking-convert_002dly
> is wrong?
Specifically, this phrase:
"A Windows user would run the command;
convert-ly.py -e *.ly..."
...seems wrong; or the file name should be "convert-ly.py". I suggest
you rename the file to that, then see if it will execute. If not,
we'll work on getting Python associated with .py files.
--
Knute Snortum
