From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Bastien Guerry <bzg@gnu.org>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Hopes of making orgmanual.org the official manual?
Date: Thu, 12 Jan 2017 20:51:57 +0100 [thread overview]
Message-ID: <87eg08awf6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY3R60dJBz3KR6DH+XhacsHDeA-B0O6xnAEm7Nrk542LfQ@mail.gmail.com> (Kaushal Modi's message of "Thu, 12 Jan 2017 18:58:16 +0000")
Hello,
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Are there plans to have the orgmanual.org (
> http://orgmode.org/cgit.cgi/org-mode.git/tree/contrib/orgmanual.org)
> completely replace the texinfo version at some point?
The first step is to have orgmanual.org generate org.texi. We're not
there yet because there is no 1:1 correspondence between constructs used
in org.texi and Org syntax.
> I believe that orgmanual.org was synchronized with the texinfo version
> when it was checked in.
No, it wasn't even compiling when it landed in contrib/. Now, it exports
correctly. The process is slow, though, due to the sheer number of
macros (900+) and some code blocks at the end that can be removed.
> But I fear that if this switching to org manual step is
> delayed, there might not be enough motivation to keep orgmanual.org
> maintained.
Note that orgmanual.org is not maintained so far. A starting point would
be to try to update a small part of the manual and report what is
missing in "ox-texinfo.el".
As a side note, I think we could use some free (i.e., noop in
"ox-texinfo.el") emphasis markers, e.g. "+...+", for additional syntax,
e.g., @key{...}, or @kbd{...}.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-12 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:58 Hopes of making orgmanual.org the official manual? Kaushal Modi
2017-01-12 19:51 ` Nicolas Goaziou [this message]
2017-01-12 20:39 ` Nicolas Goaziou
2017-01-12 20:15 ` Eric Abrahamsen
2017-01-12 20:21 ` Nicolas Goaziou
2017-01-12 20:25 ` Eric Abrahamsen
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=87eg08awf6.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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.