On 2023-09-28 12:22 am, Jean Abou Samra wrote:
Le jeudi 28 septembre 2023 à 06:26 +0000, bobr...@centrum.is a écrit :
Understood. As noted in my original post, I also still have v2.22.2
installed
which I installed with the installer. The fact that I installed
2.22.2 with
the installer leaves me puzzled as to why I can't invoke it without
the full
path.
I think you might need to call it as "lilypond.exe", not "lilypond". Or
maybe
"lilypond-windows.exe". I don't really know much about Windows
terminals though.
lilypond-windows.exe differs only in that the executable targets the GUI
subsystem. The effect is that it runs without needing to spawn a
visible terminal window with the process. When setting up file
association for .ly files, it can be very useful. If you are already in
a console environment however, then there should be no functional
difference between lilypond.exe versus lilypond-windows.exe.
In general, executable types (.exe, .com, .bat, .cmd...) are assumed by
the classic* command prompt, so typing "lilypond" should be able to find
and resolve to a "lilypond.exe" in the PATH if it exists. You can run
"where lilypond" to verify not only that it is being found but also the
locations of all matches if there are multiple.
(* By "classic", I mean the old-school cmd.exe shell. If you are
running an alternate shell such as PowerShell, then you will need to
consult its documentation.)
-- Aaron Hill
