[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Verbatim content (inline-special-block)
From: |
Max Nikulin |
Subject: |
Verbatim content (inline-special-block) |
Date: |
Thu, 11 Apr 2024 18:03:03 +0700 |
User-agent: |
Mozilla Thunderbird |
Ihor Radchenko. Re: Experimental public branch for inline special
blocks. Tue, 09 Apr 2024 08:52:38 +0000.
https://list.orgmode.org/875xwqj4tl.fsf@localhost
- 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 controlled by some optional parameter like
@kbd[:verbatim t]{ unlike =code=, ... }
Certainly parsing of normal Org markup should be suppressed,
however I am less sure concerning @markup{}. In the following example
text inside @param{} may be emphasized:
@code{def calculate(@param{expr}, @param{env})}
"@" inside such object may be escaped as @{@}. An alternatively is a
parameter like :parse that can have values like "markup", "custom",
"verbatim". This case "verbatim" disabled parsing of @objects().