On Sun, Feb 04, 2024 at 04:18:27PM +, Werner LEMBERG wrote:
> Indeed, because it is not too an exotic feature. In LilyPond, we have
> a bunch of smaller files that get included in a master document; every
> file comprises a section of the document and essentially starts with
>
> ```
> @unmacr
>>You can undefine a macro FOO with ‘@unmacro FOO’. It is not an
>>error to undefine a macro that is already undefined. For
>>example:
>>
>> @unmacro foo
>>
>> However, this doesn't work.
>
> I don't know if this is a regression as the code for this error
> message existed as fa
On Thu, Feb 01, 2024 at 12:37:29PM +, Werner LEMBERG wrote:
>
> In the texinfo manual of version 7.1 I can find the following about
> `@unmacro`:
>
>
>You can undefine a macro FOO with ‘@unmacro FOO’. It is not an
>error to undefine a macro that is already undefined. For example:
>
In the texinfo manual of version 7.1 I can find the following about
`@unmacro`:
You can undefine a macro FOO with ‘@unmacro FOO’. It is not an
error to undefine a macro that is already undefined. For example:
@unmacro foo
However, this doesn't work. This input document
``` u.te
