From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis Anaya Subject: Re: [ANN] New items pushed in into Org Mode Github. Date: Sat, 8 Sep 2012 13:31:39 -0400 Message-ID: References: <87bohgigv4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36155) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TAOsp-00070L-Je for emacs-orgmode@gnu.org; Sat, 08 Sep 2012 13:31:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TAOso-00051M-M1 for emacs-orgmode@gnu.org; Sat, 08 Sep 2012 13:31:51 -0400 Received: from blu0-omc1-s21.blu0.hotmail.com ([65.55.116.32]:41023) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TAOso-00051G-I3 for emacs-orgmode@gnu.org; Sat, 08 Sep 2012 13:31:50 -0400 In-Reply-To: <87bohgigv4.fsf@gmail.com> (Jambunathan K.'s message of "Sat\, 08 Sep 2012 22\:36\:39 +0530") 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: Jambunathan K Cc: emacs-orgmode@gnu.org Jambunathan K writes: Hi: > It is great that you are updating your sources and providing updates on > new features in the mailing list. It would be much better if you could > maintain a .org file in Worg that demoes all the capabilities of > org-e-groff exporter. The org file for the exporter is up to date in terms of features. This was a small fix that I needed to place and it did not created a change in the documentation. (C'mon, I just removed a \n :) ) I should do that on the babel exports. It's on the todo list. > My only concern is that updates that you are providing is getting > fragmented (and not consolidated) as the exporter is continuing to be > improved and solidified. > > ps: Definitely not meant as a criticism. No worries, your point and concern is well taken. I try to keep the code current, I'm not saying that I will always succeed, but I least I try to do it. Before I push anything into Org Mode Github I: 1. Check out the current code from Org Mode. 2. Do a diff for changes. For instance, in this case I noticed that "macro" was removed and I removed it accordingly on the new code. I need to do it for the ChangeLog (that I never get right anyway, but I try). 3. Run regression test. I have an automated regression test script that I run for changes. I got burned once, not to anybody's fault, it happened and highlighted the need for having it. Is there something that you've noticed that I should address? (Now I'm curious...) -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo