Am Mo., 4. Jan. 2021 um 08:18 Uhr schrieb Michael Käppler <[email protected]>: > > Am 03.01.2021 um 19:44 schrieb Thomas Morley: > > Am So., 3. Jan. 2021 um 18:28 Uhr schrieb Michael Käppler > > <[email protected]>: > >> Am 03.01.2021 um 16:34 schrieb Thomas Morley: > >>> ailing file with us? :) > >>> Attached. > >>> Although not really familar with texinfo I aimed at doing it as > >>> minimal as possible. Likely I miss something ... > >> '\input texinfo' at the beginning....? > > Thanks, works! > > A meaningful error-message would have been helpfull... > With '\input texinfo' you are tellng TeX that it should load all definitions > from 'texinfo.tex' needed for compiling Texinfo files. > Without that, TeX will understand basically nothing you wrote in your > file, beginning > with the different escape characters ('\' in plain TeX vs. '@' in Texinfo) > So in this case it is pretty hard to give a meaningful error message, > not saying that > TeX would be great in this domain otherwise... ;) > > Note that it will load the 'texinfo.tex' from your TeX distribution by > default, which may probably be > a different version that the bundled one from lilypond/tex. This can be > very important for testing. > You can force TeX to use another texinfo.tex by setting the > environmental variable 'TEXINPUTS', > e.g. by doing > export TEXINPUTS=your-path-to-lilypond/tex > before calling TeX. > > (using 'export' will set it for the whole shell session, however. Normally, > doing 'TEXINPUTS=your-path-to-lilypond/tex xetex foo.texi' should also work, > I'm not sure how this is with 'texi2pdf', which is basically a shell script) > > (Werner, feel free to correct me or provide more insights in this topic...) > > Cheers, > Michael > > > > Cheers, > > Harm >
Thanks for the detailed explanations, very helpfull Cheers, Harm
