Ah, yes ... I will rewrite this, when I'm in my machine again
Cheers, Jan-Peter
Am 07.01.2012 um 09:42 schrieb David Kastrup :
> Jan-Peter Voigt writes:
>
>> Am 06.01.2012 10:17, schrieb Jan-Peter Voigt:
>>> Am 06.01.2012 09:35, schrieb Jan-Peter Voigt:
Hello David,
the \sour
Hello Carl, Hello David,
thanks for your replies!
I will read through those threads next week. This might help me understand what
is happening under the hood.
The basic include is working as expected. But I think it would be a nice
feature if one could search for files to include using scheme.
On 1/6/12 7:28 AM, "David Kastrup" wrote:
>
>Now I don't want to repeat old mistakes, but I don't really have the
>time for an extended investigation. So if somebody gives me all the
>data in a manner that does not require all too much thinking on my side,
>I might try putting that kind of funct
Jan-Peter Voigt writes:
> Here are the two functions I implemented ... still a bit clumsy, but
> it works for now ... if you are interested *how* and *why* to use
> them, don't hesitate to mail me!
If anybody is game for digging up the old discussion: I don't think it
makes sense to require a us
Am 06.01.2012 10:17, schrieb Jan-Peter Voigt:
Am 06.01.2012 09:35, schrieb Jan-Peter Voigt:
Hello David,
the \sourcefilename hint is helpful! Thank you!
If I use this in my function and do a ly:parser-clone, the location
is up to date:
...
Now I will look, if this is working also with
ly:par
Am 06.01.2012 09:35, schrieb Jan-Peter Voigt:
Hello David,
the \sourcefilename hint is helpful! Thank you!
If I use this in my function and do a ly:parser-clone, the location is
up to date:
...
Now I will look, if this is working also with ly:parser-include-string
while resetting filename and
with the location name and
only includes the file if they match. (This should not work, if you
have set some output-suffix!)
This is a usable solution to me. But I would like to have the correct
location info available, while parsing the included file.
Is it possible to create an arbitrary "in
o me. But I would like to have the correct
location info available, while parsing the included file.
Is it possible to create an arbitrary "include"-music-function? This
would make it possible, to (for example) include all files in a
directory or matching