From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Hopes of making orgmanual.org the official manual? Date: Thu, 12 Jan 2017 20:51:57 +0100 Message-ID: <87eg08awf6.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cRlPv-0002Gh-PB for emacs-orgmode@gnu.org; Thu, 12 Jan 2017 14:52:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cRlPu-0003nB-Vr for emacs-orgmode@gnu.org; Thu, 12 Jan 2017 14:52:11 -0500 In-Reply-To: (Kaushal Modi's message of "Thu, 12 Jan 2017 18:58:16 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Kaushal Modi Cc: Bastien Guerry , emacs-org list Hello, Kaushal Modi 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