From: Ihor Radchenko <yantar92@posteo.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "Payas Relekar" <relekarpayas@gmail.com>,
"Björn Bidar" <bjorn.bidar@thaodan.de>,
"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 08:26:06 +0000 [thread overview]
Message-ID: <87a5xnwnkx.fsf@localhost> (raw)
In-Reply-To: <87mt1n372h.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
>> 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.
>
> My general question is what advantage this would provide over just using
> TeXinfo in the first place, if the required complexity of the markup has
> to be the same as for TeXinfo in the first place?
Check out the original thread where RMS officially suggested that Org
can be used instead of texinfo.
In short, Org provides much more configurable export output. You can
customize it using Elisp or within Org document itself. You can generate
parts of documentation using output of src blocks. You can fine-tune
specific export output formats using inline export blocks. etc ...
--
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 8:27 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
2023-05-29 7:55 ` Philip Kaludercic
2023-05-29 8:26 ` Ihor Radchenko [this message]
-- 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
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=87a5xnwnkx.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 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).