From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerhard Subject: Re: Example text and source code in agenda - orgmanual.org typo Date: Wed, 09 Apr 2014 09:40:08 +0200 Message-ID: <5344F958.3030402@gmail.com> References: <534428AD.6000108@gmail.com> <87ioqjvcrk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43751) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXn7H-0007Lh-RL for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:40:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXn7E-0007kL-5U for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:40:15 -0400 Received: from mail-ee0-x230.google.com ([2a00:1450:4013:c00::230]:42470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXn7D-0007kA-TU for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:40:12 -0400 Received: by mail-ee0-f48.google.com with SMTP id b57so1498890eek.35 for ; Wed, 09 Apr 2014 00:40:10 -0700 (PDT) In-Reply-To: <87ioqjvcrk.fsf@gmail.com> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" Hello, Am 08.04.2014 21:31, schrieb Nicolas Goaziou: > ntsd@tsdye.com (Thomas S. Dye) writes: > >> When I was working on the project I hoped the Org mode developers would >> choose to "eat their own dog food" (as Carsten put it to me) and prepare >> the texinfo and other documentation with Org mode source. Of course, >> that hope was based on considerable naivete and an imperfect >> understanding of how Org mode is connected with the rest of the Emacs >> world. > FWIW, I still think it would be good to have our documentation in our > home-made format. > > Of course, there's the problem of backporting documentation fixes coming > from Emacs developers, but we might find volunteers to take care of it. > Also, it doesn't happen very frequently. > > There may be other road blocks that I'm not aware of, but if there is > none, I suggest to think about the feasibility of this project again. > now I know more about the history and status of this project, thanks to your answers. Although it looks to me as a good starting point, It also seems to take quite a bit of knowledge about many things to go on here, so I am not the one who could help. But maybe the volunteers can be found. Regards, Gerhard