markup commands leaks (Re: Scheme question on strict substitution)

[Nicolas Sceaux]

Han-Wen Nienhuys <address@hidden> writes:

> Nicolas Sceaux escreveu:
>>> [Issue 162]
>>> Yes, but this introduces a new problem. Putting stuff into lily module
>>> from a .ly file means that definitions from one .ly file will leak
>>> into another, which is also a problem.
>> 
>> I don't understand: what leaks into what?
>
> if you do 
>
>   lilypond file1.ly file2.ly
>
> then if file1 modifies the (lily) module ,  this will also affect how 
> file2 is processed. Of course, the order of processing should not affect
> the end result.  

Defining the markups in a markup-init.ly file triggers some issues. Some
.scm files loaded from lily.scm use make-COMMAND-markup functions. So
the built-in markup commands need to be defined or imported in the
(lily) module.

One solution could be to make the make-command-markup macro define the
commands in the (lily) module when it is called from it (ie in the
define-markup-commands.scm file loaded from lily.scm), but when it is
called from a user .ly file, define the commands in an other module.

This could be a (user-markup) module, #:used by the anonymous modules
created when parsing a .ly file. That (user-markup) module would be
cleaned between two main ly file processing --I don't know yet how--
to avoid the side-effects.

But I may be missing something more straightforward?

nicolas