Re: Backslashes in @warning
Le 22/10/2022 à 16:45, Jean Abou Samra a écrit : I'm going to create an issue for that. https://gitlab.com/lilypond/lilypond/-/issues/6443
LilyPond 2.23.80
We are happy to announce the release of LilyPond 2.23.80. This is the first release candidate towards the next stable version 2.24.0 expected in December. Please test your scores with this version and report back the experience as well as any problems you encounter. Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.23/Documentation/learning/installing signature.asc Description: This is a digitally signed message part
Re: Backslashes in @warning
>> 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.
Werner
Re: Backslashes in @warning
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.
Labels for ties and slurs
We have many issues related to ties and to slurs. Would anybody mind creating two GitLab labels ~"Ties" and ~"Slurs" for these? It would ease searching for defects in those specific areas.
Re: Backslashes in @warning
Le 22/10/2022 à 14:21, Werner LEMBERG a écrit :
You just have to "escape" it, like in texidocs:
@code{\\textMark} et @code{\\textEndMark}
I'll prepare a MR later today for text.itely.
If I do that, the backslash does appear in HTML, but there are two
backslashes in the PDF.
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
```
and use it as follows.
```
@warning{This is a warning with the @bscode{foo} command.}
```
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.
