From: Karl Fogel <kfogel@red-bean.com>
To: Fren Zeee <frenzeee@gmail.com>
Cc: Stephen Berman <stephen.berman@gmx.net>, emacs-devel@gnu.org
Subject: Re: What is emacs architecture ?
Date: Wed, 07 Jul 2010 18:32:59 -0400 [thread overview]
Message-ID: <87lj9morc4.fsf@kslab.red-bean.com> (raw)
In-Reply-To: <AANLkTimjug0gsOd9vRYtk3b9DFp-NgyS_O8S3TwA3Ql4@mail.gmail.com> (Fren Zeee's message of "Wed, 7 Jul 2010 15:28:42 -0700")
Fren Zeee <frenzeee@gmail.com> writes:
>If it were truly a valuable document, someone _here_ would have
>definitely pursued it, read it and likely enhanced the ideas.
>
>I am not asking at the moment of the architecture of the whole of
>elisp code of packages but the basic architecture in C ie primitives ,
>the operation of the lisp stack for the diassembled code and so on.
>Where is the documentation of the lisp assembled code in elisp.pdf ?
>Jim Blandy's article touches everything a little superficially.
>
>Where do you get the very minimal of the emacs code ? For anyone to
>contribute to emacs, there has to be some very minimal code to be read
>and understood and also documenting the journey for future reference
>when the person starts forgetting.
I don't know -- I was taught this stuff (mostly by Jim Blandy, years
ago, in person :-) ). But I think the general way is to pick a bug, try
to fix it, and ask a lot of questions. At the end of that process, you
might be able to write the document you're looking for.
Wish I had a better answer for you...
next prev parent reply other threads:[~2010-07-07 22:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 5:50 What is emacs architecture ? Fren Zeee
2010-07-07 6:07 ` Masatake YAMATO
2010-07-07 15:26 ` Karl Fogel
2010-07-07 15:36 ` Drew Adams
2010-07-07 17:30 ` Stephen Berman
2010-07-07 20:02 ` Karl Fogel
2010-07-07 22:28 ` Fren Zeee
2010-07-07 22:32 ` Karl Fogel [this message]
2010-07-08 3:27 ` Stephen J. Turnbull
2010-07-08 4:16 ` Jeff Clough
2010-07-19 4:49 ` Fren Zeee
2010-07-08 7:06 ` Eli Zaretskii
2010-07-08 7:40 ` Thien-Thi Nguyen
2010-07-08 17:37 ` Karl Fogel
2010-07-19 4:35 ` Fren Zeee
2010-07-19 14:43 ` Óscar Fuentes
2010-07-19 17:12 ` Chad Brown
2010-07-19 22:04 ` Fren Zeee
2010-07-19 22:39 ` Chad Brown
2010-07-20 2:10 ` Stephen J. Turnbull
2010-07-20 2:58 ` Óscar Fuentes
2010-07-20 5:19 ` Stephen J. Turnbull
2010-07-20 12:53 ` Óscar Fuentes
2010-07-20 3:00 ` Miles Bader
2010-07-20 3:24 ` Óscar Fuentes
2010-07-20 5:13 ` Miles Bader
2010-07-20 12:42 ` Óscar Fuentes
2010-07-20 5:21 ` Stephen J. Turnbull
2010-07-20 6:21 ` Fren Zeee
2010-07-20 8:23 ` Stephen J. Turnbull
2010-07-20 8:59 ` Andreas Schwab
2010-07-21 3:25 ` Fren Zeee
2010-07-21 7:51 ` Andreas Schwab
2010-07-21 3:28 ` Fren Zeee
2010-07-21 14:49 ` David Robinow
2010-07-20 8:48 ` Andreas Schwab
2010-07-07 18:15 ` Fren Zeee
2010-07-08 0:09 ` Stephen J. Turnbull
2010-07-08 6:42 ` Eli Zaretskii
2010-07-08 8:22 ` Stephen J. Turnbull
2010-07-08 9:44 ` Eli Zaretskii
2010-07-07 18:51 ` Fren Zeee
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=87lj9morc4.fsf@kslab.red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=frenzeee@gmail.com \
--cc=stephen.berman@gmx.net \
/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).