From: Ihor Radchenko <yantar92@posteo.net>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>,
"Philip Kaludercic" <philipk@posteo.net>,
"Christopher Dimech" <dimech@gmx.com>,
"Help Emacs Orgmode" <emacs-orgmode@gnu.org>,
"Help Gnu Emacs" <help-gnu-emacs@gnu.org>
Subject: Re: org-mode for package documentation
Date: Mon, 29 May 2023 07:54:20 +0000 [thread overview]
Message-ID: <87pm6jtvwz.fsf@localhost> (raw)
In-Reply-To: <877csszoy6.fsf@gmail.com>
Payas Relekar <relekarpayas@gmail.com> writes:
> IIRC, Richard Stallman said he'd be amenable to it, _provided that_ Org
> fulfilled all the requisite functionality from Texinfo.
Correct. We need to add more flexible markup. The idea was to add
something similar to special blocks, but inline. Currently, ox-texinfo
is approaching the extended markup with macros. See doc/doc-setup.org.
> Ihor (org maintainer) was also receptive, but I don't remember if/how
> much progress happened towards the goal.
We discussed possible syntax of inline custom markup to be added. See
https://orgmode.org/list/87bkqx4jyg.fsf@localhost Someone is to go ahead
and try to implement it. It might be me in future, but I am prioritizing
working on some other new features in Org for now.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-29 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 11:14 org-mode for package documentation Payas Relekar
2023-05-29 7:54 ` Ihor Radchenko [this message]
2023-05-29 7:55 ` Philip Kaludercic
2023-05-29 8:26 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2023-04-28 18:42 Christopher Dimech
2023-04-28 21:08 ` Philip Kaludercic
2023-05-27 17:18 ` Björn Bidar
2023-05-28 11:08 ` Philip Kaludercic
2023-06-06 16:49 ` David Masterson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm6jtvwz.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bjorn.bidar@thaodan.de \
--cc=dimech@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=philipk@posteo.net \
--cc=relekarpayas@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.