Re: lilypond-invoke-editor can't find editor.scm in Windows

[Federico Bruni]

Il giorno mar 24 lug 2018 alle 14:46, James Lowe <address@hidden> 
ha scritto:
> >  >
> >  > >
> >  > >
> >  > > > Try setting the path explicitly for the SCM dir.
> >  > > >
> >  > > > You can do it via the UI or using the 'setx' command
> >  > > >
> >  > >
> >  > > I've tried adding the usr/share/scm dir to the path, but didn't 
> > work.
> >  > >
> >  > > Then I skimmed through the lilypond-invoke-editor script and I 
> > figured
> >  > > out that setting the LILYPOND_DATADIR to "C:\Program Files
> >  > > (x86)\LilyPond\usr\share\lilypond\current" would help, but it 
> > didn't.
> >  >
>
>
> see
>
> https://lists.gnu.org/archive/html/lilypond-user/2012-02/msg00102.html
>
> I think this might help.
>
> I was able to get a guile prompt with this workaround (the problem 
> reported here in 2012 still persists in 2018 :( )
>
> e.g
>
> C:\Users\Joe user>set GUILE_LOAD_PATH=..\..\PROGRAM FILES 
> (x86)\LILYPOND\USR\SHARE\GUILE\1.8

I've recently added a comment about this subject here:
https://sourceforge.net/p/testlilyissues/issues/2279/

I did not need setting that variable to launch 'lilypond 
scheme-sandbox' or guile in PowerShell.
If you say that it helped you, maybe it's because you use the command 
prompt while I'm using PowerShell. (The command prompt is too 
"primitive"... PowerShell is a bit better...)

Anyway, setting the GUILE_LOAD_PATH environment variable doesn't help 
at all with my problem.
I can get a guile prompt.
My problem is that I cannot launch the lilypond-invoke-editor script.

If you want to test it in your Windows installation, try opening an 
existing .ly file using a command like:

guile.exe 'C:\Program Files 
(x86)\LilyPond\usr\bin\lilypond-invoke-editor' 
textedit://C:/Users/test/Documents/test.ly:10:9:10