emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	Marcelo de Moraes Serpa <celoserpa@gmail.com>
Subject: Re: Development workflow
Date: Thu, 28 Jul 2011 09:26:23 +0200	[thread overview]
Message-ID: <87hb667rqc.fsf@altern.org> (raw)
In-Reply-To: <81ei1bqb2e.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 28 Jul 2011 10:02:57 +0530")

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

      parent reply	other threads:[~2011-07-28  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 23:16 Development workflow Marcelo de Moraes Serpa
2011-07-28  4:32 ` Jambunathan K
     [not found]   ` <CACHMzOEiR=ogrjE6HeyT2zGhGqhKk6uPT8xKsckMhFE+kf5biA@mail.gmail.com>
2011-07-28  5:18     ` Fwd: " Marcelo de Moraes Serpa
2011-07-28  7:21       ` Bastien
2011-07-28  7:26   ` Bastien [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hb667rqc.fsf@altern.org \
    --to=bzg@altern.org \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).