unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Kyle M. Lee" <mail2kyle@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Is there an emacs c code document ?
Date: Mon, 07 Apr 2008 12:10:30 -0400	[thread overview]
Message-ID: <jwvd4p1wsz6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87myo6dovy.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 07 Apr 2008 17:56:33 +0900")

>> Hi all, I am very interested in emacs internal implementation,
>> especially the c code. And I have gotten the cvs emacs 23
>> code. I googled with "emacs internal", found nothing valuable. So
>> I asked this question, are there some nice documents or guide about
>> the emacs internal implementation ?

> The XEmacs Internals Manual
> http://www.xemacs.org/Documentation/21.5/html/internals.html may be of
> some use for general coding conventions and techniques.  The Mule code
> is quite different, as are the internal console APIs.  But the coding
> conventions for the Lisp engine are pretty similar.

There is also the "the craft of text editing" book
(http://www.finseth.com/craft/), which is very old and doesn't describe
Emacs's code, but can still be relevant in giving an idea of the
general organization.

And if you have detailed questions, this mailing list may answer them,
of course.


        Stefan




  reply	other threads:[~2008-04-07 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  5:01 Is there an emacs c code document ? Kyle M. Lee
2008-04-07  7:33 ` Jason Rumney
2008-04-07  8:56 ` Stephen J. Turnbull
2008-04-07 16:10   ` Stefan Monnier [this message]
2008-04-08  1:50     ` Kyle M. Lee
2008-04-07 19:14 ` Eli Zaretskii
2008-04-08  2:31   ` Kyle M. Lee

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=jwvd4p1wsz6.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=mail2kyle@gmail.com \
    --cc=stephen@xemacs.org \
    /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).