J L escreveu:
> Hi,
>
> Following a little bit of investigation, the changes I propose are given
> below. Sorry, I couldn't get a diff off git (no git installed here, and
> installing might be troublesome), so my 'hack' will be presented at the
> end of this mail.
>
> All this really does, is it
J L escreveu:
> Anyways, I'll be looking into adding some sort of way to make the
> registry entries for python-interpreter becoming optional (of course, it
> will be on by default, for all the windows users who wouldn't know
> better). I'm guessing that the file that the installer is build from i
Hi,
Following a little bit of investigation, the changes I propose are given
below. Sorry, I couldn't get a diff off git (no git installed here, and
installing might be troublesome), so my 'hack' will be presented at the end
of this mail.
All this really does, is it makes 'registering the li
PROTECTED]>
To: J L <[EMAIL PROTECTED]>
CC: lilypond-devel@gnu.org
Subject: Re: Windows Releases
Date: Tue, 20 Feb 2007 13:32:48 +0100
MIME-Version: 1.0
Received: from iris.s3.kth.se ([130.237.43.24]) by
bay0-mc1-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue,
Don't talk nonsense! It works perfectly well to run commands like
convert-ly -e myfile.ly
from the command prompt.
Wow, sorry. I never thought that. It seems that I must update my knowledge.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.o
I was thinking a bit more. Installing and uninstalling LilyPond itself
should remain separate from jEdit. So there should be one installer that
separately installs the two.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu
Bertalan Fodor wrote:
Putting these into the path would also not help.
- you can not run convert-ly.py
Don't talk nonsense! It works perfectly well to run commands like
convert-ly -e myfile.ly
from the command prompt.
- you must use python convert-ly.py - But if you do, you must say:
python "
Putting these into the path would also not help.
- you can not run convert-ly.py
- you must use python convert-ly.py - But if you do, you must say:
python "c:\program files\lilypond\usr\bin\convert-ly.py" So you didn't
gain much.
Still I don't see it is useful.
Perhaps we should look at the p
Bertalan Fodor wrote:
Of course it should, but probably not the current \bin\ folder
Why? On Windows platforms people rarely use the PATH to run programs.
Since midi2ly, lilypond-book and the other utility scripts are not available
via any graphical interface. Of course, your immediate
Of course it should, but probably not the current \bin\ folder
Why? On Windows platforms people rarely use the PATH to run programs.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-deve
Of course it should, but probably not the current \bin\ folder but
a folder that only contains wrapper scripts to lilypond, lilypond-book,
midi2ly, ... which call the real programs from a directory that's not in
the PATH. This is the way it's done in the Linux installers.
/Mats
Bertalan Fo
I don't think that lilypond path should be in the PATH.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
As has already been stated. the Python bundled with LilyPond is
sufficiently functional to handle all the Python scripts such as midi2ly,
convert-ly, lilypond-book, ...
If you find any problem with any of these scripts, please send a bug report.
I guess your real problem is that you have installe
Hi,
On Wed, 21 Feb 2007, J L wrote:
> LilyPond's bundled python is useless (unless something has changed in
> the past 6 months), so I don't see why it is still bundled.
Maybe it is bundled, because LilyPond _needs_ Python? And Windows users
are typically too clueless to install all needed dep
J L escreveu:
> Hi,
>
> It's been a while since I've had much to do with LilyPond, but it seems
> that the installer is STILL fiddling with the registry in terms of python.
>
> What I would like to see:
> 1. Could the "call registry_python" line in the lilypond.nsh (or
> whatever) file used for g
LilyPond's bundled python is useless (unless something has changed in
the past 6 months), so I don't see why it is still bundled.
It is needed an perfectly good to run convert-ly.
Bert
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http:/
Hi,
It's been a while since I've had much to do with LilyPond, but it seems that
the installer is STILL fiddling with the registry in terms of python.
What I would like to see:
1. Could the "call registry_python" line in the lilypond.nsh (or whatever)
file used for generating the installer be
17 matches
Mail list logo
