On Mon, Oct 12, 2009 at 12:59 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
If everything is based on the existence of a given directory, then all
is clear. I believed that the registry had something to do.
No, it only checks for the dir:
Mark Austin wrote:
2009/10/10 Nick Payne nick.pa...@internode.on.net:
Mark Austin wrote:
Having downloaded 2.13.4 for Windows, and not having used Lilypond
for
a few weks, I tried to complie a new tune. In attempting to convert
to
the new version, I got this error from Lilypond
It clearly shows I think, that there is nothing wrong with the pretty
name GNU LilyPond (yes, without the ugly underscore), but the nsis
script should be written to use LilyPond and not the ugly GNU_LilyPond
as installation folder.
Though I very strongly object to having the meaningless,
Valentin Villenave wrote Saturday, October 10, 2009 9:59 PM
On Sat, Oct 10, 2009 at 7:49 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
I installed both Neil's and Graham's 2.13.4 releases under
Windows Vista and
AFAICR the default directory was LilyPond as usual. I certainly
didn't
change
Trevor Daniels wrote:
Ahh - I see what you mean. The name of the -installer- changed.
This doesn't affect anything when doing a straight install under
Windows. The default install directory is unaffected. That's what
I misunderstood. Thanks Valentin.
No, I installed 2.13.4 on both XP and
Nick Payne wrote Sunday, October 11, 2009 10:59 AM
Trevor Daniels wrote:
Ahh - I see what you mean. The name of the -installer- changed.
This doesn't affect anything when doing a straight install under
Windows. The default install directory is unaffected. That's
what
I misunderstood.
Hello,
I had the same problem and changed the directory in JEdit. If it is
reversed to only Liliypond, I hope someone will write it in this list.
Has the installation descripition in the documentation been changed?
However, it seems the default directory name is actually picked
up from the
2009/10/11 Hajo Dezelski dl1...@googlemail.com:
Could be, but as far as I remember it is recommended, that you
uninstall the old version before you install the knew one.
It is not only recommended, you can not install the new version
without previously uninstalling the old one, because the
Francisco Vila wrote Sunday, October 11, 2009 3:54 PM
2009/10/11 Hajo Dezelski dl1...@googlemail.com:
Could be, but as far as I remember it is recommended, that you
uninstall the old version before you install the knew one.
It is not only recommended, you can not install the new version
2009/10/11 Trevor Daniels t.dani...@treda.co.uk:
You don't need to uninstall; rename works
fine if you want to keep the previous around.
I didn't know that the installer could be fooled that easy. I rather
remember the opposite: the installer refusing to cooperate even after
having uninstalled
Trevor Daniels wrote:
Nick Payne wrote Sunday, October 11, 2009 10:59 AM
Trevor Daniels wrote:
Ahh - I see what you mean. The name of the -installer- changed.
This doesn't affect anything when doing a straight install under
Windows. The default install directory is unaffected. That's
Nick Payne wrote Sunday, October 11, 2009 7:42 PM
Trevor Daniels wrote:
Nick Payne wrote Sunday, October 11, 2009 10:59 AM
Trevor Daniels wrote:
Ahh - I see what you mean. The name of the -installer-
changed.
This doesn't affect anything when doing a straight install
under
Windows.
On Sun, Oct 11, 2009 at 9:17 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
I used that download but I didn't uninstall; I usually just remain
the directory in Program Files before an install as I like to keep
old versions readily to hand. This seems to be the difference
between our
On 2009-10-11, Valentin Villenave wrote:
On Sun, Oct 11, 2009 at 9:17 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
I used that download but I didn't uninstall; I usually just remain
the directory in Program Files before an install as I like to keep
old versions readily to hand. This
On 2009-10-11, Patrick McCarty wrote:
On 2009-10-11, Valentin Villenave wrote:
On Sun, Oct 11, 2009 at 9:17 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
I used that download but I didn't uninstall; I usually just remain
the directory in Program Files before an install as I like to
On Sun, Oct 11, 2009 at 10:52 PM, Patrick McCarty pnor...@gmail.com wrote:
And here is a patch to revert the change.
This is similar to the patch I posted earlier -- except that yours does work :-)
Cheers,
Valentin
From 2dbcd7705dcfaa93eedf9df8eb50616d4503a885 Mon Sep 17 00:00:00 2001
From:
Francisco Vila wrote Sunday, October 11, 2009 5:12 PM
2009/10/11 Trevor Daniels t.dani...@treda.co.uk:
You don't need to uninstall; rename works
fine if you want to keep the previous around.
I didn't know that the installer could be fooled that easy. I
rather
remember the opposite: the
Having downloaded 2.13.4 for Windows, and not having used Lilypond for
a few weks, I tried to complie a new tune. In attempting to convert to
the new version, I got this error from Lilypond Tool:
convert-ly.py --edit C:\Users\Mark Austin\Documents\Marks
Files\Folklore\Mumming
Mark Austin wrote:
Having downloaded 2.13.4 for Windows, and not having used Lilypond for
a few weks, I tried to complie a new tune. In attempting to convert to
the new version, I got this error from Lilypond Tool:
convert-ly.py --edit C:\Users\Mark Austin\Documents\Marks
Files\Folklore\Mumming
2009/10/10 Nick Payne nick.pa...@internode.on.net:
Mark Austin wrote:
Having downloaded 2.13.4 for Windows, and not having used Lilypond for
a few weks, I tried to complie a new tune. In attempting to convert to
the new version, I got this error from Lilypond Tool:
convert-ly.py --edit
Mark Austin wrote:
2009/10/10 Nick Payne nick.pa...@internode.on.net:
Mark Austin wrote:
Having downloaded 2.13.4 for Windows, and not having used Lilypond for
a few weks, I tried to complie a new tune. In attempting to convert to
the new version, I got this error from Lilypond Tool:
Have these files moved or something?
The 2.13.4 default install dir is now C:\Program Files\GNU_LilyPond
and not C:\Program Files\LilyPond...
Who invented this stupidity? Is there a nonGNU lilypond? Is GIMP
installed in GNU_IMP?
Why people always have the temptation to break things that
On Sat, Oct 10, 2009 at 6:16 PM, Bertalan Fodor (LilyPondTool)
lilypondt...@organum.hu wrote:
The 2.13.4 default install dir is now C:\Program Files\GNU_LilyPond and
not C:\Program Files\LilyPond...
Who invented this stupidity? Is there a nonGNU lilypond? Is GIMP installed
in GNU_IMP?
Why
2009/10/10 Valentin Villenave v.villen...@gmail.com:
Actually, I first noticed it with Neil's temporary 2.13.4 mingw build,
back in July. I can't find any trace of this pretty_name change on
Jan's Github repo, I assume it's just some temporary whimsical idea
from either Graham or Neil :-)
On Sat, Oct 10, 2009 at 06:47:18PM +0200, Valentin Villenave wrote:
On Sat, Oct 10, 2009 at 6:16 PM, Bertalan Fodor (LilyPondTool)
lilypondt...@organum.hu wrote:
Who invented this stupidity? Is there a nonGNU lilypond? Is GIMP installed
in GNU_IMP?
Why people always have the temptation to
On Sat, Oct 10, 2009 at 7:10 PM, Graham Percival
gra...@percival-music.ca wrote:
Patch appreciated, since we're such OMG stupid idiots to fix stuff
ourselves.
I'd have sent a patch if I knew where the mao the code is :-)
Oh wait, I just found it. Patch attached.
... in fact, rather than
-
From: Valentin Villenave v.villen...@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: lilypond-user lilypond-user@gnu.org
Sent: Saturday, October 10, 2009 6:23 PM
Subject: Re: Problems with Lilypond Tool/JEdit
On Sat, Oct 10, 2009 at 7:10 PM, Graham Percival
gra...@percival-music.ca
On Sat, Oct 10, 2009 at 7:49 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
I installed both Neil's and Graham's 2.13.4 releases under Windows Vista and
AFAICR the default directory was LilyPond as usual. I certainly didn't
change anything and they went into a directory named Program
28 matches
Mail list logo
