From: NULL <nullx002@gmail.com>
To: emacs-orgmode-request@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Emacs-orgmode Digest, Vol 131, Issue 15
Date: Wed, 18 Jan 2017 22:43:27 +0530 [thread overview]
Message-ID: <87tw8wl2a0.fsf@gmail.com> (raw)
In-Reply-To: <mailman.123.1484326819.2741.emacs-orgmode@gnu.org> (emacs-orgmode-request@gnu.org's message of "Fri, 13 Jan 2017 12:00:19 -0500")
emacs-orgmode-request@gnu.org writes:
>
> Message: 1
> Date: Thu, 12 Jan 2017 18:58:16 +0000
> From: Kaushal Modi <kaushal.modi@gmail.com>
> To: emacs-org list <emacs-orgmode@gnu.org>, Bastien Guerry
> <bzg@gnu.org>
> Subject: [O] Hopes of making orgmanual.org the official manual?
> Message-ID:
> <CAFyQvY3R60dJBz3KR6DH+XhacsHDeA-B0O6xnAEm7Nrk542LfQ@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello all,
>
> 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?
>
> I believe that orgmanual.org was synchronized with the texinfo version when
> it was checked in. But I fear that if this switching to org manual step is
> delayed, there might not be enough motivation to keep orgmanual.org
> maintained.
>
> --
>
> Kaushal Modi
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.gnu.org/archive/html/emacs-orgmode/attachments/20170112/857ec112/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 12 Jan 2017 20:51:57 +0100
> From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> To: Kaushal Modi <kaushal.modi@gmail.com>
> Cc: emacs-org list <emacs-orgmode@gnu.org>, Bastien Guerry
> <bzg@gnu.org>
> Subject: Re: [O] Hopes of making orgmanual.org the official manual?
> Message-ID: <87eg08awf6.fsf@nicolasgoaziou.fr>
> Content-Type: text/plain
>
> 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
>
would love orgmode.org as manual. org manual in org!!
--
~nullx002 (somewhere on pale blue dot)
github.com/nullx002
bitbucket.org/nullx002
twitter.com/nullx002
parent reply other threads:[~2017-01-18 17:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.123.1484326819.2741.emacs-orgmode@gnu.org>]
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=87tw8wl2a0.fsf@gmail.com \
--to=nullx002@gmail.com \
--cc=emacs-orgmode-request@gnu.org \
--cc=emacs-orgmode@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).