From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@altern.org>
Subject: Re: Development workflow
Date: Thu, 28 Jul 2011 09:26:23 +0200
Message-ID: <87hb667rqc.fsf@altern.org>
References: <CACHMzOEqHt6hvR8RGmOS7cx_iv0vgbXFFHb7YmD+AYs+wk9fQw@mail.gmail.com>
	<81ei1bqb2e.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:36029)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1QmLd0-0005Gv-EY
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 04:07:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1QmLcz-0001AS-0U
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 04:07:34 -0400
Received: from mail-ww0-f49.google.com ([74.125.82.49]:64734)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1QmLcy-0001AF-Oq
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 04:07:32 -0400
Received: by wwf22 with SMTP id 22so1744737wwf.30
	for <emacs-orgmode@gnu.org>; Thu, 28 Jul 2011 01:07:31 -0700 (PDT)
In-Reply-To: <81ei1bqb2e.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 28
	Jul 2011 10:02:57 +0530")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <kjambunathan@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>, Marcelo de Moraes Serpa <celoserpa@gmail.com>

Hi Marcelo,

Jambunathan K <kjambunathan@gmail.com> writes:

> You don't have to compile your elisp files at all and as a developer I
> would even venture to say you shouldn't.

I also recommend not compiling your .el files, you will have more
useful debug traces (setq edebug-on-error t).

I would suggest reading the documentation of Edebug in the Elisp info
file.  M-x edebug-defun RET on functions will let you go through the
functions' evaluation step by step and understand better what they do
right (and wrong).

Also, please use git branches and send patch with git format-patch.

If you have comments about the code while reading through, please 
share them freely -- a longstanding wish of mine is to organize a 
live code review with core Org hackers:

  http://scientopia.org/blogs/goodmath/2011/07/06/things-everyone-should-do-code-review/

Good luck!

-- 
 Bastien