From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: tiefeng wu <icebergwtf@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Learning emacs sources
Date: Wed, 29 Jul 2009 13:08:23 +0900 [thread overview]
Message-ID: <87ws5s9lmw.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <8763dc5g2s.fsf@cyd.mit.edu>
Chong Yidong writes:
> tiefeng wu <icebergwtf@gmail.com> writes:
>
> > I'm interesting to know implementation of emacs. I downloaded source
> > of version 22.3, but honestly, source files are too complicated for
> > me.
> >
> > Any introduce view of emacs structure design or any advise will be
> > appreciated.
>
> 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.
If you want to understand the design overview, then
http://www.gnu.org/software/emacs/emacs-paper.html
(the basic textbook for "Emacs 101", authored by Richard Stallman) and
http://www.xemacs.org/Documentation/21.5/html/internals_14.html
(somewhat more implementation-specific and up-to-date) are good
summaries. For internals from the inside out the latter is a good
place to start. You will find that implementation details are
somewhat divergent from (GNU) Emacs, but important things like naming
conventions (eg, 'why do identifiers start with "Q", "S", "V", or
"F"?') and the relation of the Emacs event loop to the traditional
read-eval-print loop are gathered in one convenient place here. When
you start recognizing divergences between the XEmacs docs and the
Emacs implementation, you can be pretty sure you've understood enough
to switch to just reading Emacs source. :-)
next prev parent reply other threads:[~2009-07-29 4:08 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ws5s9lmw.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=icebergwtf@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.