unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Sundar Vasan <vr.sundar@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	tiefeng wu <icebergwtf@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Learning emacs sources
Date: Thu, 30 Jul 2009 00:19:29 +0200	[thread overview]
Message-ID: <e01d8a50907291519p7ac10d83s652850ae2f5144ca@mail.gmail.com> (raw)
In-Reply-To: <63acfd6c0907291506o36f1563ena3e951f491c28c85@mail.gmail.com>

On Thu, Jul 30, 2009 at 12:06 AM, Sundar Vasan<vr.sundar@gmail.com> wrote:
> On Tue, Jul 28, 2009 at 8:22 PM, Chong Yidong<cyd@stupidchicken.com> wrote:
>> Reading the source in one go is probably not feasible.  If you are
>> interested in how one particular part of Emacs works, a good strategy is
>> to read the relevant part of the Lisp manual, try to formulate a set of
>> specific questions, then ask this mailing list.
>>
>
> Are there any simple bugs that I could work on? That would give me a
> lot more focus than just looking randomly.
>
> Adding/updating docs is something else that I was thinking about as a
> good way to start (esp since I can look at it from a newbie
> perspective as I'm fairly new to emacs). That would also help me learn
> more about emacs. But I'm not sure where to begin. Any suggestions?


Do you know about the bug database:

    http://emacsbugs.donarmstrong.com/

Even if you can't solve the bugs right now, looking at them and trying
to understand might perhaps be something that fits your mind.

Another thing to look at (that is quite a bit complicated though) is
CEDET that is on its way into Emacs. There are plenty of things to do.




  reply	other threads:[~2009-07-29 22:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  2:28 Learning emacs sources tiefeng wu
2009-07-29  3:22 ` Chong Yidong
2009-07-29  4:08   ` Stephen J. Turnbull
2009-07-29 10:23     ` tiefeng wu
2009-07-29 20:59     ` Sean Sieger
2009-07-30  2:45       ` Stephen J. Turnbull
2009-07-29 22:06   ` Sundar Vasan
2009-07-29 22:19     ` Lennart Borgman [this message]
2009-07-30 17:23       ` Sundar Vasan

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=e01d8a50907291519p7ac10d83s652850ae2f5144ca@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=icebergwtf@gmail.com \
    --cc=vr.sundar@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.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).