From: Philip Kaludercic <philipk@posteo.net>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 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: Sun, 28 May 2023 11:08:07 +0000 [thread overview]
Message-ID: <87bki4zpbc.fsf@posteo.net> (raw)
In-Reply-To: <87leh97kwl.fsf@thaodan.de> ("Björn Bidar"'s message of "Sat, 27 May 2023 20:18:34 +0300")
Björn Bidar <bjorn.bidar@thaodan.de> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Christopher Dimech <dimech@gmx.com> writes:
>>
>>> Dear Compeers,
>>>
>>> Some months ago there had been a discussion about using org-mode
>>> to produce package documentation. Which would allow the use of
>>> Latex3 (e.g. use of colour, floating images).
>>
>> Where/when did this happen? Could you provide a few pointers?
>
> I don't know exactly but when use-package was merged into Emacs there
> were discussions if keeping the documentation in org-mode format is
> fine.
>
> From what I understood it is possible.
Using org-mode to generate TeXinfo manuals is already possible, due to
the ox-texinfo backend, but I haven't been personally that satisfied
with the quality of the output, due to the lack of (easy) support for
the fine distinctions in markup that texinfo provides. That is why the
use-package documentation had to be translated from org-mode to texinfo,
which was part of the reason the process of merging took so long.
next prev parent reply other threads:[~2023-05-28 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 18:42 org-mode for package documentation Christopher Dimech
2023-04-28 21:08 ` Philip Kaludercic
2023-05-27 17:18 ` Björn Bidar
2023-05-28 11:08 ` Philip Kaludercic [this message]
2023-06-06 16:49 ` David Masterson
-- strict thread matches above, loose matches on Subject: below --
2023-05-28 11:14 Payas Relekar
2023-05-29 7:54 ` Ihor Radchenko
2023-05-29 7:55 ` Philip Kaludercic
2023-05-29 8:26 ` Ihor Radchenko
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=87bki4zpbc.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=bjorn.bidar@thaodan.de \
--cc=dimech@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@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).