>> IMHO, this is completely useless. There is not a single hint to
>> the location of the error – why does Guile treat
>> `define-markup-commands.scm` as an 'unknown file'?
>>
>> What am I missing?
>
> That the error does not _occur_ in define-markup-commands.scm?
> define-markup-command is a macro. Apparently it was executed
> successfully but leaving a faulty markup definition that blows up at
> the time interpret-markup tries instantiating the markup in the
> current output definition. Since the macro has already executed
> successfully, substituting different code for the original code, its
> connection to the code that is now blowing up is no longer there.
Hopefully you are not right, and it is rather a problem with missing
byte compilation. Otherwise debugging markup functions would have
become incredibly hard.
Werner
