|
From: | Jean Abou Samra |
Subject: | Re: Backslashes in @warning |
Date: | Sat, 22 Oct 2022 15:09:19 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 |
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.
[Prev in Thread] | Current Thread | [Next in Thread] |