Libraries
Johan Vromans
files.
When running LilyPond manually, I specify library paths with the
--include command line option.
Is it possible to preset include paths with Elysium?
-- Johan
Johan Vromans
Also, is it possible to ignore, or better: hide, included files?
While working on a score I do not want to have to wade through all the
information from included files.
-- Johan
Harmath Dénes
> Johan Vromans <jvro...@squirrel.nl> writes:
>
>> In my LilyPond scores I use many \include directoves for library
>> files.
>>
>> When running LilyPond manually, I specify library paths with the
>> --include command line option.
>>
>> Is it possible to preset include paths with Elysium?
Currently not, but setting custom command line options in the Compiler preference page might be worth considering as a new feature.
> Also, is it possible to ignore, or better: hide, included files?
>
> While working on a score I do not want to have to wade through all the
> information from included files.
>
> -- Johan
What do you mean under "all the information from included files"? Currently, only the Open Model Element dialog shows all variables from all the scores in the library, but it is easily searchable.
Johan Vromans
Thanks for your reply.
Harmath Dénes <harmat...@gmail.com> writes:
>>> Is it possible to preset include paths with Elysium?
>
> Currently not, but setting custom command line options in the Compiler
> preference page might be worth considering as a new feature.
Yes, that would be nice.
I temporarily work aroung by providing my own lilypond script that wraos
around the real lilypond program.
-- Johan
Johan Vromans
>> Also, is it possible to ignore, or better: hide, included files?
>>
>> While working on a score I do not want to have to wade through all the
>> information from included files.
>
> What do you mean under "all the information from included files"?
> Currently, only the Open Model Element dialog shows all variables from
> all the scores in the library, but it is easily searchable.
I have a score with many \include's. Mostly helper definitions, e.g.:
% Paper size.
\include "a4paper.ly"
% Staff size. Currently supported are 14 15 16 17 18 19 20.
\include "staff14.ly"
% Disable line indenting.
\include "noindent.ly"
% Use a sans font for the lyrics.
\include "lyricssans.ly"
% Use popular notation for chords.
\include "popchords.ly"
% Helper modules.
\include "ifdefined.ly"
\include "makeunfold.ly"
In the outline, many \include's show up. It's just '\include' so there's
no reference to which of the many \include's they refer to. It is also
not possible to open the \include'd file from the outline. So IMHO
showing the \include's in the outline is not really useful and I would
prefer the \include's to be hidden from the outline.
-- Johan
Johan Vromans
leadMusic = \relative c'' {
s1
}
leadWords = \lyrics {
foo bar
}
The outline shows:
o leadMusic
o \relative
𝅘𝅥𝅮 { }
o leadWords
o \lyrics
𝅘𝅥𝅮 { }
The last line with the musical note and the { } seems misindented.
-- Johan
Johan Vromans
An internal error occurred during: "Xtext validation".
java.lang.RuntimeException: Please make sure your LilyPond
installation is valid and its location is specified correctly.
Compilation (with ^T) works okay, so I may assume that my LilyPond
installation is valid and its location is specified correctly.
I have the suspicion that the LP binary that is specified for
compilation (I use a workaround script) is not used for validation.
-- Johan
Harmath Dénes
Harmath Dénes
Harmath Dénes
Johan Vromans
> See http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=32, fix to be released soon.
Holding my breath...
Thanks,
Johan
Johan Vromans
> See http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=32, fix to be released soon.
Thanks. Hiding the \includes reduces the clutter in my scores.
I added the command line arguments:
--include=.
--include=$HOME/lib/lilypond/ly
It still doesn't work. Changing to:
--include=.
--include=/home/jv/lib/lilypond/ly
Now compilation (Ctrl-T) works, but syntax validation still throws an
error.
Summary of the trace back:
org.eclipse.emf.common.util.WrappedException: java.lang.RuntimeException: Please make sure your LilyPond installation is valid and its location is specified correctly.
...
Caused by: java.lang.RuntimeException: Please make sure your LilyPond installation is valid and its location is specified correctly.
...
Caused by: org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: java.io.FileNotFoundException: init.ly (No such file or directory)
...
Caused by: java.io.FileNotFoundException: init.ly (No such file or directory)
...
Apperently it is unable to find init.ly. Any ideas?
Thanks,
Johan
Johan Vromans
> During validation, Elysium parses LilyPond initialization files
> (init.ly etc.) which are located relative to the given LilyPond
> executable.
So you keep track of all the peculiar file locations as used by the
different distributions? Impressive...
So if you specified a script outside LilyPond's bin
> directory, validation won't work. Hopefully, when custom command line
> arguments will be supported in the next release, you won't need this
> hacky workaround.
Thanks.
Harmath Dénes
> Harmath Dénes <harmat...@gmail.com> writes:
>
>> See http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=32, fix to be released soon.
>
> Thanks. Hiding the \includes reduces the clutter in my scores.
>
> I added the command line arguments:
>
> --include=.
> --include=$HOME/lib/lilypond/ly
>
> It still doesn't work. Changing to:
>
> --include=.
> --include=/home/jv/lib/lilypond/ly
Unfortunately, shell variables don't work. I don't think there's a way for Java to pick them up...
> Now compilation (Ctrl-T) works, but syntax validation still throws an
> error.
>
> Summary of the trace back:
>
> org.eclipse.emf.common.util.WrappedException: java.lang.RuntimeException: Please make sure your LilyPond installation is valid and its location is specified correctly.
> ...
> Caused by: java.lang.RuntimeException: Please make sure your LilyPond installation is valid and its location is specified correctly.
> ...
> Caused by: org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: java.io.FileNotFoundException: init.ly (No such file or directory)
> ...
> Caused by: java.io.FileNotFoundException: init.ly (No such file or directory)
> ...
>
> Apperently it is unable to find init.ly. Any ideas?
>
> Thanks,
> Johan
Please see the other thread.
Harmath Dénes
> Harmath Dénes <harmat...@gmail.com> writes:
>
>> During validation, Elysium parses LilyPond initialization files
>> (init.ly etc.) which are located relative to the given LilyPond
>> executable.
>
> So you keep track of all the peculiar file locations as used by the
> different distributions? Impressive…
Not exactly. See this issue: http://code.google.com/a/eclipselabs.org/p/elysium/issues/detail?id=23