> ... there's no python interface to libkpathsea other than kpsewhich
Jin-Hwan Cho <[EMAIL PROTECTED]> is working on an interface; you
might contact him.
Werner
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo
Mats Bengtsson writes:
> I don't know what objections you have to use kpathsea.
I've got a general dislike for its magic and there's no python
interface to libkpathsea other than kpsewhich. There's not much
choice, I'm using that for now, latex documents only.
Jan.
--
Jan Nieuwenhuizen <[EMAI
- If I use \input for an ordinary TeX file, I get an error.
(One solution is to only react to \input{*.ly})
This is hairier. You want \input{foo.texi}, \input{foo.lytex} too.
You also don't want to ask kpathsea, or inore \inputs that cannot be
found. I'm not too fond of something like \lyincl
Mats Bengtsson writes:
> For the moment, I notice the following problems:
> - The generated file goes to stdout instead of myfile.latex
Fixed. It started out as a filter (filter-lilypond-book).
> - If I use \input for an ordinary TeX file, I get an error.
>(One solution is to only react to
Now I get a bit further, but there are more errors.
I have attached a small example file to play with, if you
don't have any at hand.
For the moment, I notice the following problems:
- The generated file goes to stdout instead of myfile.latex
- If I use \input for an ordinary TeX file, I get an err
[EMAIL PROTECTED] writes:
> I tried a minimal example of lilypond-book on a LaTeX file and
> immediately got the following error:
fixed in CVS, hopefully.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Bug-lily
I tried a minimal example of lilypond-book on a LaTeX file and
immediately got the following error:
Traceback (most recent call last):
File "/space/bin/lilypond-book", line 881, in ?
main ()
File "/space/bin/lilypond-book", line 879, in main
do_file (files[0])
File "/space/bin/lilypon
