[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Org mode and Emacs (was: Convert README.org to plain text README whi
From: |
Ihor Radchenko |
Subject: |
Re: Org mode and Emacs (was: Convert README.org to plain text README while installing package) |
Date: |
Wed, 15 Jun 2022 13:58:36 +0800 |
Forwarding a relevant message from emacs-devel on examples of markup
nesting in texinfo:
Eli Zaretskii <eliz@gnu.org> writes:
> From: Ihor Radchenko <yantar92@gmail.com>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Can someone please prepare a small example texi file containing examples
> >> of various texi features that are commonly needed and possibly also
> >> demonstrating some concrete instances of problems that exist in texinfo?
> >
> > Given that you already produced a list of markups, is such an example
> > still wanted?
>
> It would certainly help with development. For example, I did not look
> close into allowed markup nesting. File with tricky examples will be
> helpful as a benchmark for any attempted implementation.
I'm afraid that would take someone who knows more than I do about Org,
because I don't have a clear idea what examples to provide to be
useful for this purpose. In general the Texinfo manual has examples
of every Texinfo feature, of course. But it is a large manual.
Specifically wrt nested markups, the most frequent ones I can think
off the top of my head are:
. @var inside @code
. @key inside @kbd
. any in-line markup inside @w
. @r, which is "escape to regular typeface" and can be used inside
any markup that produces other typefaces
HTH