[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 391 in lilypond: using relative filepath in \include " foo.ly
From: |
codesite-noreply |
Subject: |
Issue 391 in lilypond: using relative filepath in \include " foo.ly" |
Date: |
Sat, 07 Jul 2007 19:20:59 -0700 |
Issue 391: using relative filepath in \include "foo.ly"
http://code.google.com/p/lilypond/issues/detail?id=391
New issue report by gpermus:
It would be nice if the filenames inside \include "" were relative to
the
file that contained that \include.
(or possibly using a different command like \includeRelative "" )
For example, if we have
piece1/piece1.ly
mydefs/init.ly
mydefs/paper-settings.ly
then inside piece1.ly we could do
\include "../mydefs/init.ly"
but init.ly would *also* need to have
\include "../mydefs/paper-settings.ly"
instead of
\include "paper-settings.ly"
because lilypond looks for the file "foo" relative to the very first
file
in the include change (ie piece1.ly) intead of looking for "foo"
relative
to the file which contained the \include "foo.ly" line (in this case,
init.ly)
%% Bounty offered from Valetin
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low Bounty
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 391 in lilypond: using relative filepath in \include " foo.ly",
codesite-noreply <=