lily4jedit-user

[lily4jedit-user] LilyPondTool refuses to honour PATH

[John M. <joh...@gm...>]

Hello,

I would like to make LilyPondTool find all LilyPond binaries only by
relying on the PATH, so as long as I don't excessively play with PATH I
run the same LilyPond version whether I call lilypond or convert-ly from
JEdit or from a terminal.  For this purpose, I set as empty the field
"Path to LilyPond binary" in LPT settings.

However, it seems impossible to make this work, as I get error messages
that say "Cannot run program "/lilypond"", or when I try to run
convert-ly from the toolbar button "Cannot run program "/python"".

Even worse, if I set the correct path to my LilyPond installation in LPT
settings, that is "usr/local/bin", I get an error "Cannot run program
"/usr/local/bin/python"" when trying to run convert-ly from the toolbar.

By the way, I don't understand why LilyPondTool forces using Python to
call convert-ly, which is not the good way to go if LilyPond was
installed from a package on lilypond.org, because in this case
convert-ly is a wrapper written in shell on GNU/Linux.

Note that I don't want to mess with making symlinks; I think that LPT
should work almost out-of-the-box (i.e. works immediately after having
configured LPT settings), and for this purpose honouring the PATH and
shebangs of different wrapper scripts (which differ depending on whether
LilyPond has been installed by local compilation, the distro package
manager or lilypond.org package) is the good way to go.

Best,
John

Re: [lily4jedit-user] LilyPondTool refuses to honour PATH

[Valentin V. <v.v...@gm...>]

2009/12/26 John Mandereau <joh...@gm...>:
> I would like to make LilyPondTool find all LilyPond binaries only by
> relying on the PATH, so as long as I don't excessively play with PATH I
> run the same LilyPond version whether I call lilypond or convert-ly from
> JEdit or from a terminal.  For this purpose, I set as empty the field
> "Path to LilyPond binary" in LPT settings.

Another way that I always wanted to investigate would be to have a
post-install script that would automatically setup LilyPondTool
correctly (and possibly even some custom jEdit options such as
perspective settings). Bertalan once suggested that it could be made
optional (such as a "auto-configure" menu item).

Cheers (and Merry Xmas),
Valentin

Re: [lily4jedit-user] LilyPondTool refuses to honour PATH

[John M. <joh...@gm...>]

Le samedi 26 décembre 2009 à 19:37 +0100, Valentin Villenave a écrit :
> Another way that I always wanted to investigate would be to have a
> post-install script that would automatically setup LilyPondTool
> correctly (and possibly even some custom jEdit options such as
> perspective settings). Bertalan once suggested that it could be made
> optional (such as a "auto-configure" menu item).

Very good idea; however, this might orthogonal to allowing make LPT rely
on the PATH to run LilyPond binaries.

Best,
John

Re: [lily4jedit-user] LilyPondTool refuses to honour PATH

[Bertalan F. (LilyPondTool) <lil...@or...>]

I agree, though unfortunately I very rarely run linux, so usually I have 
no idea about these bugs.
Historically convert-ly had to be run using python, and it must be run 
like that on windows.

Bert

John Mandereau wrote:
> Hello,
>
> I would like to make LilyPondTool find all LilyPond binaries only by
> relying on the PATH, so as long as I don't excessively play with PATH I
> run the same LilyPond version whether I call lilypond or convert-ly from
> JEdit or from a terminal.  For this purpose, I set as empty the field
> "Path to LilyPond binary" in LPT settings.
>
> However, it seems impossible to make this work, as I get error messages
> that say "Cannot run program "/lilypond"", or when I try to run
> convert-ly from the toolbar button "Cannot run program "/python"".
>
> Even worse, if I set the correct path to my LilyPond installation in LPT
> settings, that is "usr/local/bin", I get an error "Cannot run program
> "/usr/local/bin/python"" when trying to run convert-ly from the toolbar.
>
> By the way, I don't understand why LilyPondTool forces using Python to
> call convert-ly, which is not the good way to go if LilyPond was
> installed from a package on lilypond.org, because in this case
> convert-ly is a wrapper written in shell on GNU/Linux.
>
> Note that I don't want to mess with making symlinks; I think that LPT
> should work almost out-of-the-box (i.e. works immediately after having
> configured LPT settings), and for this purpose honouring the PATH and
> shebangs of different wrapper scripts (which differ depending on whether
> LilyPond has been installed by local compilation, the distro package
> manager or lilypond.org package) is the good way to go.
>
> Best,
> John
>   
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> ------------------------------------------------------------------------
>
> _______________________________________________
> Lily4jedit-user mailing list
> Lil...@li...
> https://lists.sourceforge.net/lists/listinfo/lily4jedit-user
>   

Re: [lily4jedit-user] LilyPondTool refuses to honour PATH

[John M. <joh...@gm...>]

Le dimanche 27 décembre 2009 à 23:06 +0100, Bertalan Fodor
(LilyPondTool) a écrit :
> I agree, though unfortunately I very rarely run linux, so usually I
> have no idea about these bugs. 
> Historically convert-ly had to be run using python, and it must be run
> like that on windows.

I thought that PATH and PATHEXT tuning, plus the association of .py
files with the Python interpreter shipped with Lilyond, were done by
LilyPond installer on Windows, which would be enough to make lilypond
and convert-ly executables like on a Unix OS.  Anyway, current LPT
behavior is certainly more robust, as those three settings can be easily
altered in a way that breaks at least the Python scripts.

I hope my error reports are precise enough to make it possible to solve
this issue by just looking at Java/JEdit reference manuals.  If nobody
else is going to fix this, I might have a look in several months after
having learnt a bit of Java (I'm not a frequent LPT user, I was asking
this from a question on Lily French-speaking list).

Best,
John

Re: [lily4jedit-user] LilyPondTool refuses to honour PATH

[Bertalan F. (LilyPondTool) <lil...@or...>]

I committed a fix for this. Current limitation is you can't set python 
path differently if you really need to run .py scripts and it assumes 
that if a script ends with .py then it must be run using python.

John Mandereau wrote:
> Le dimanche 27 décembre 2009 à 23:06 +0100, Bertalan Fodor
> (LilyPondTool) a écrit :
>   
>> I agree, though unfortunately I very rarely run linux, so usually I
>> have no idea about these bugs. 
>> Historically convert-ly had to be run using python, and it must be run
>> like that on windows.
>>     
>
> I thought that PATH and PATHEXT tuning, plus the association of .py
> files with the Python interpreter shipped with Lilyond, were done by
> LilyPond installer on Windows, which would be enough to make lilypond
> and convert-ly executables like on a Unix OS.  Anyway, current LPT
> behavior is certainly more robust, as those three settings can be easily
> altered in a way that breaks at least the Python scripts.
>
> I hope my error reports are precise enough to make it possible to solve
> this issue by just looking at Java/JEdit reference manuals.  If nobody
> else is going to fix this, I might have a look in several months after
> having learnt a bit of Java (I'm not a frequent LPT user, I was asking
> this from a question on Lily French-speaking list).
>
> Best,
> John
>