Nick Payne writes:
Should the Lilypond install add the program directory to the path on
Windows? I normally use LP on Linux, where it is in the path, but I
just installed 2.17.6 on my notebook, which runs Windows 7 x64, and it
isn't in the path - I can't open a command prompt and run lilypond
On Wed, Nov 7, 2012 at 10:26 AM, Jan Nieuwenhuizen jann...@gnu.org wrote:
commit 917dab12e7a838f1f153e7c57fb921c0b19b9bc2
Author: Phil Holmes m...@philholmes.net
Date: Fri Jan 6 17:23:15 2012 +
Stops Windows PATH being changed
Such messages, and this one in
Janek Warchoł janek.lilyp...@gmail.com writes:
On Wed, Nov 7, 2012 at 10:26 AM, Jan Nieuwenhuizen jann...@gnu.org wrote:
commit 917dab12e7a838f1f153e7c57fb921c0b19b9bc2
Author: Phil Holmes m...@philholmes.net
Date: Fri Jan 6 17:23:15 2012 +
Stops Windows PATH
Janek Warchoł writes:
i suppose relevant issue is here
http://code.google.com/p/lilypond/issues/detail?id=1948
Interesting.
So instead of FIXING that bug, a new bug was introduced by
removing code. Great. Also no trail was left in Git, which
leaves the risk of someone restarting that cycle
David Kastrup writes:
I usually try to remember when pushing changes to do one
git commit --amend
for the sake of adding Issue : in front of the commit message. I
don't think many other bother, and my own success rate is probably below
70%.
Yes, that's quite nice. I like that a lot
Jan Nieuwenhuizen jann...@gnu.org writes:
Janek Warchoł writes:
i suppose relevant issue is here
http://code.google.com/p/lilypond/issues/detail?id=1948
Interesting.
So instead of FIXING that bug, a new bug was introduced by
removing code.
A new _installation_ step was introduced since
David Kastrup writes:
A new _installation_ step was introduced since the previous one would
not work more than a few times and left traces in the system when
uninstalling that would eventually lead to failure.
Who takes care of this new step?
Great. Also no trail was left in Git,
That
Jan Nieuwenhuizen jann...@gnu.org writes:
David Kastrup writes:
A new _installation_ step was introduced since the previous one would
not work more than a few times and left traces in the system when
uninstalling that would eventually lead to failure.
Who takes care of this new step?
