Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>>
>> Ah.. I didn't think this was allowed (or at least not recommended). Using
>> \include at anything else than top level is a kind of substitute for macros,
>> and macros is something we don't want..
>
> I guess that cr
[EMAIL PROTECTED] writes:
>
> Ah.. I didn't think this was allowed (or at least not recommended). Using
> \include at anything else than top level is a kind of substitute for macros,
> and macros is something we don't want..
I guess that creating macros with \include is sufficiently painful to
On Friday 26 November 2004 11.54, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Your last comment is very true.. perhaps each true end-of-file could
> > produce an EOF token? Then the error would be caught at the end of the
> > input file instead. Also, some errors related to manual \incl
[EMAIL PROTECTED] writes:
> [moving to lilypond-devel]
> On Friday 26 November 2004 01.58, Han-Wen Nienhuys wrote:
> > [EMAIL PROTECTED] writes:
> > > and then add
> > > \maininput
> > > \EOF
> > > to init.ly? When the input file is incomplete, this would _always_ give
> > > an error like "unexpect
[moving to lilypond-devel]
On Friday 26 November 2004 01.58, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > and then add
> > \maininput
> > \EOF
> > to init.ly? When the input file is incomplete, this would _always_ give
> > an error like "unexpected EOF", I think. Which might be more intu
