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

[James Lowe]

Federico

Sorry I wasn't concentrating *at all*!

Ignore my reply.

I'll test with lilypond-invoke-editor.

and let you know.

James

On Tue, 24 Jul 2018 12:17:45 +0100 (BST), "James Lowe" <address@hidden> wrote:

> Federico
> 
> On Mon, 23 Jul 2018 18:20:53 +0200, Federico Bruni <address@hidden> wrote:
> 
> > 
> > 
> > Il giorno lun 23 lug 2018 alle 10:36, James Lowe <address@hidden> 
> > ha scritto:
> > > Federico,
> > > 
> > > On Mon, 23 Jul 2018 09:13:09 +0200, Federico Bruni 
> > > <address@hidden> wrote:
> > > 
> > >>  Hi all
> > >> 
> > >>  The lilypond-invoke-editor installed in Windows returns the 
> > >> following
> > >>  error:
> > >> 
> > >>   > guile.exe 'C:\Program Files
> > >>  (x86)\LilyPond\usr\bin\lilypond-invoke-editor'
> > >>  textedit://C:/Users/test/Documents/test.ly:10:9:10
> > >>  lilypond-invoke-editor (GNU LilyPond) 2.19.82
> > >>  ERROR: no code for module (scm editor)
> > >> 
> > >>  It seems it cannot find the editor.scm file?
> > >> 
> > >>  The file is in 'C:\Program Files
> > >>  (x86)\LilyPond\usr\share\lilypond\current\scm'.
> > >>  How can I tell Windows where to find it?
> > >> 
> > >>  I'm using Windows 10.
> > > 
> > > I believe we set the path to the bin dir
> > > 
> > 
> > Hi James
> > 
> > "We set" means what? AFAIK the Windows installation does not add any 
> > path to the system environment variables, if this is what you meant.
> > I had to manually add the bin/ directory to the Path in order to launch 
> > lilypond.exe without the prefix.
> 
> Yes you are correct. I forgot that we changed that many moons ago.
> 
> > 
> > 
> > > 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.
> 
> OK so I installed Windows 10, downloaded the latest dev binary, installed it 
> and tried it myself.
> 
> It seems to work for me.
> 
> --snip--
> 
> Microsoft Windows [Version 10.0.17134.167]
> (c) 2018 Microsoft Corporation. All rights reserved.
> 
> C:\Users\Joe user>cd Desktop
> 
> C:\Users\Joe user\Desktop>path
> PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;%path;C:\Program
>  Files (x86)\LilyPond\usr\bin;C:\Program Files (x86)\LilyPond
> 
> C:\Users\Joe user\Desktop>lilypond test.ly
> GNU LilyPond 2.19.82
> Processing `test.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `./tmp-lilypond-2A4lvz'...
> Converting to `test.pdf'...
> Deleting `./tmp-lilypond-2A4lvz'...
> Success: compilation successfully completed
> 
> C:\Users\Joe user\Desktop>
> 
> --snip--
> 
> I was not sure if perhaps it was one of those many 'spaces in path' or 'using 
> remote drive' issues that I remember someone reporting but could not get any 
> problems compiling.
> 
> Anything more you can give me to try to reproduce?
> 
> Regards
> 
> James