From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Verbatim content (inline-special-block)
Date: Fri, 12 Apr 2024 17:55:01 +0700 [thread overview]
Message-ID: <uvb3u7$o1r$1@ciao.gmane.io> (raw)
In-Reply-To: <877ch4ys1a.fsf@localhost>
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=, ... }
>
> I do not like this idea - this will make the attribute list a part of
> the Org markup spec,
I see you point and I agree that it is valid concern. On the other hand
I do not have strong opinion what variant is better.
> 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 *text* inside}
>
> This way, instead of @code{}, we should use @code~{...} or even
> @~{...}/@={...} (mnemonics for ~...~ and =...=)
I consider @foo={}-like variants as unnecessary complications of the
inline special block feature. The idea of composition is better from my
point of view. With this approach it is enough to have non-conflicting
syntax for non-parsed fragments. I am against making @code{} a special
name with suppressed markup parsing. The price of composition in
comparison with @foo={} is more verbose markup.
By the way, Org has src_lang{...} syntax for almost non-parsed fragments
(neglecting requirement of balanced curly brackets that is an issue).
Actually "=" in @foo={} is a kind of special argument distinct from ones
specified inside [] and {}.
>> @code{def calculate(@param{expr}, @param{env})}
[...]
> Also, the reason why Texinfo users do @param in @code is the lack of
> automatic syntax highlighting, unlike in Org mode.
Is ox-texinfo able to convert syntax highlighting to native texinfo markup?
So if @markup{} is not allowed in verbatim content then it is another
feature loosely related to custom inline blocks.
next prev parent reply other threads:[~2024-04-12 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 10:49 inline-special-block: part2 Max Nikulin
2024-04-11 11:03 ` Verbatim content (inline-special-block) Max Nikulin
2024-04-11 12:58 ` Ihor Radchenko
2024-04-12 10:55 ` Max Nikulin [this message]
2024-04-12 17:53 ` Ihor Radchenko
2024-04-11 11:08 ` Link to the repository (Re: inline-special-block: part2) Max Nikulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='uvb3u7$o1r$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).