Python is in Lilypond's bin folder which you already put in your path.
On my Windows 10 VM system (multiple versions of lilypond installed) the
command convert-ly worked (no explicit python invocation and no need for the
.py extension suffix)
I'll see if I still have some virgin snapshot of a VM to try and see what
should be done apart from the Lillypond install itself.
On the given system I had to disable some python placeholder that referred me
with a message to the App execution setting 'App Installer' when invoking
python as a command to make it work. No clue whether that was due to any of the
installed applications or a native setting of Windows 10 (have Mac OS as a
daily driver OS AND windows VM only for rare cases where I need Windows)
> On 31 May 2021, at 21:21, JxStarks <jxsta...@gmail.com> wrote:
>
>
> or do I need to have some reference to Python in my PATH command? If so,
> what should it look like?
>
> Jerry
>
>> On Mon, May 31, 2021 at 3:19 PM JxStarks <jxsta...@gmail.com> wrote:
>> Hi all,
>>
>> Thanks for your many and informative responses. M.Tarenskeen correctly
>> identified a typo in my PATH command ("C;" instead of "C:"). I corrected
>> that, but the problem still persists. Here's my latest info from the Command
>> Prompt:
>> ===
>> C:\Users\Jerry\Documents\RPC\Music\FILE>echo %PATH%
>> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>> Files
>> (x86)\LilyPond\usr\bin;C:\Users\Jerry\AppData\Local\Microsoft\WindowsApps;
>>
>> C:\Users\Jerry\Documents\RPC\Music\FILE>convert-ly *.ly
>> 'convert-ly' is not recognized as an internal or external command,
>> operable program or batch file.
>> ===
>> Note: I tried both convert-ly and convert-ly.py, and neither one works for
>> me.
>>
>> At some iteration in the past, the PATH command was "[pre-set
>> paths];C:\Program Files (x86)\LilyPond\usr\bin;"
>>
>> Is it necessary to have the [pre-set paths] and the quotation marks?
>>
>> Jerry
>>
>>> On Mon, May 31, 2021 at 2:27 PM Brian Barker <b.m.bar...@btinternet.com>
>>> wrote:
>>> At 11:04 31/05/2021 -0700, Knute Snortum wrote:
>>> >I suggest you rename the file to that, ...
>>>
>>> For what it's worth, I didn't have this problem: that was Jerry
>>> Starks. Is he now happy? I was merely concerned that I was watching a
>>> conversation that seemed to include no doubt well-intentioned but
>>> misleading responses, including simple reference to the inaccurate
>>> documentation.
>>>
>>> Brian Barker
>>>
>>>
