Keith OHara wrote: > > -Eluze <eluzew <at> gmail.com> writes: >> Luke Bakken wrote: >> > After running installer, system PATH was clobbered and only had >> Lilypond >> > path in >> > it. See attached screenshot. >> > >> the semi-colon at the beginning of the field named "variable value" is a >> strong indicator - if not the proof - that the variable "path" has more >> in >> it than only "C:\Program Files\lilypond\usr\bin"! >> > > Well, yes, but probably only that extra semicolon. > maybe…
> The LilyPond installer adds the ; at the beginning as well. > I installed a second version, and PATH was > C:\Program Files\LilyPond\usr\bin;;C:\Program Files\LilyPondNew\usr\bin > with two semicolons. > that's the way to add a new dir to PATH - if for any reason the PATH variable already had a (superfluous) semicolon at the end there will be two of them. this usually doesn't harm. i also installed further versions until i had a path of length over 960 - i'm not sure windows can/will handle the full path but i cannot imagine how the installer could mis-manage such a simple operation. Eluze -- View this message in context: http://old.nabble.com/Windows-install-clobbered-system-PATH-tp32570379p32666558.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
