Le 22/10/2022 à 16:42, Werner LEMBERG a écrit :
We could define a macro `@bscode`, to be used in `@warning` only. Add
the following to `common-macros.itely`
```
@macro bscode{TEXT}
@code{\\\TEXT\}
@end macro
```
Honestly, if there isn't a way to fix @warning globally, I think it
is simpler just not to use it here.
I'll do a patch for that.
IIRC, there are more `@warning` boxes that contain backslashes in
`@code`. If you are going to work on that, I suggest to handle them
all.
Oh dear. While investigating that, I found this instance:
https://lilypond.org/doc/v2.23/Documentation/notation/the-midi-block.html
which was fine in 2.22:
https://lilypond.org/doc/v2.22/Documentation/notation/the-midi-block.html
So we have a doc build regression. We need to figure out when this
started getting wrong…
I'm going to create an issue for that.
