Am 2015-11-12 11:22, schrieb Urs Liska:
Hi devs,
do I read the docs right in that additional include paths *have* to be
specified on the command line, with one or multiple --include options?
I think so.
Has noone asked until now for being able to have LilyPond look for an
environment variable to add include paths?
I asked for it in the German user forum some time ago
http://www.lilypondforum.de/index.php?topic=1693 because I like the way
TeX uses the environment variable TEXINPUTS.
I think many users will have their default toolboxes they use in all
projects, and it would make life somewhat easier (even if editors may
offer tools to create the command line automatically).
I use Frescobaldi, Makefiles or aliases in the .bashrc but an
environment variable would be the best fitting solution IMO.
Any opinions?
So my opinion: Please yes! Of course one should keep the -I option. One
would have to think which file is used if several files of the same name
are included.
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
