From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: [RFC] Moving "manual.org" into core Date: Mon, 05 Mar 2018 16:23:34 +0000 Message-ID: References: <87bmhooaj9.fsf@nicolasgoaziou.fr> <87y3j8dw45.fsf@bzg.fr> <87lgf8f93b.fsf@nicolasgoaziou.fr> <87lgf89lro.fsf@gnu.org> <87k1uq4n90.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000006b8470566acc057" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54821) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1essu0-0003HU-0x for emacs-orgmode@gnu.org; Mon, 05 Mar 2018 11:23:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1essty-0004T8-OP for emacs-orgmode@gnu.org; Mon, 05 Mar 2018 11:23:52 -0500 In-Reply-To: <87k1uq4n90.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: Bastien , Glenn Morris , Achim Gratz , Org Mode List --00000000000006b8470566acc057 Content-Type: text/plain; charset="UTF-8" On Mon, Mar 5, 2018 at 9:21 AM Nicolas Goaziou wrote: > > > Again, the question is: what problem are we trying to solve? > > Org boasts itself as a format to write, among other things, > documentation. Do you think it is confidence-inspiring if we do not > write our own documentation in our format? See also > . This problem > is now solved. > > Also, no matter how you look at it, doing any non-trivial edit in > "org.texi" is painful. I want to ease that pain for current contributors > (at least me), too. > +1 Editing Org is so much natural than .texi. And by this flow, we are not obsoleting .texi, just having it generate automatically instead of manually. It like writing a higher level language like C or Python instead of tinkering in Assembly. > Also, I'm not suggesting to get rid of "org.texi". I'm suggesting to > generate it from "manual.org" and to avoid as much as possible editing > it manually thereafter. In practice, this change is so small that I do > not understand what all this fuss is about. This should be simple: move > "manual.org" to doc/, overwrite "org.texi", and, when we feel confident > enough, if it ever happens, remove "org.texi" altogether from the > repository, generating it only before bundling a new Org release or > merging it with Emacs. > Exactly. Emacs will anyways ship with org.texi. So moving the manual source to Org in the Org repo shouldn't concern the Emacs repo. -- Kaushal Modi --00000000000006b8470566acc057 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Mar 5,= 2018 at 9:21 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

> Again, the question is: what problem are we trying to solve?

Org boasts itself as a format to write, among other things,
documentation. Do you think it is confidence-inspiring if we do not
write our own documentation in our format? See also
<https://en.wikipedia.org/wiki/Eating_your= _own_dog_food>. This problem
is now solved.

Also, no matter how you look at it, doing any non-trivial edit in
"org.texi" is painful. I want to ease that pain for current contr= ibutors
(at least me), too.

+1 Editing Org is s= o much natural than .texi. And by this flow, we are not obsoleting .texi, j= ust having it generate automatically instead of manually. It like writing a= higher level language like C or Python instead of tinkering in Assembly.
=C2=A0
Also, I'm not suggesting to get rid of "org.texi". I'm su= ggesting to
generate it from "manual.org" and to avoid as much as possible editin= g
it manually thereafter. In practice, this change is so small that I do
not understand what all this fuss is about. This should be simple: move
"ma= nual.org" to doc/, overwrite "org.texi", and, when we fe= el confident
enough, if it ever happens, remove "org.texi" altogether from the=
repository, generating it only before bundling a new Org release or
merging it with Emacs.

Exactly. Emacs w= ill anyways ship with org.texi. So moving the manual source to Org in the O= rg repo shouldn't concern the Emacs repo.
--
=

Kaushal Modi

--00000000000006b8470566acc057--