Max Nikulin writes:
>> It may be enough to have @kbd{@code{...}} - it is not like Texinfo has a
>> concept of truly verbatim text like in Org.
>>
>> Alternatively, we may allow two classes of inline markup:
>> @foo{parsed *text* inside}
>> and
>> @foo={verbatim *text* inside}/@foo~{verbatim *tex
On 11/04/2024 19:58, Ihor Radchenko wrote:
Max Nikulin writes:
@code{ unlike =code=, we can have leading and trailing spaces }
@code{ @foo{is not interpreted inside}}
I think, it should be controlled by some optional parameter like
@kbd[:verbatim t]{ unlike =code=, ... }
Max Nikulin writes:
>> - We should be able to define special markup for code, where the
>> contents is not parsed. Something like
>>
>> @code{ unlike =code=, we can have leading and trailing spaces }
>> @code{ @foo{is not interpreted inside}}
>
> I think, it should be contr
