From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: frenzeee@gmail.com, emacs-devel@gnu.org
Subject: Re: What is emacs architecture ?
Date: Thu, 08 Jul 2010 12:44:58 +0300 [thread overview]
Message-ID: <83mxu271et.fsf@gnu.org> (raw)
In-Reply-To: <87bpaijscj.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: frenzeee@gmail.com,
> emacs-devel@gnu.org
> Date: Thu, 08 Jul 2010 17:22:20 +0900
>
> Eli Zaretskii writes:
>
> > > http://www.xemacs.org/Documentation/21.5/html/internals.html
> > >
> > > It's not intensively maintained, and obviously is going to differ from
> > > GNU Emacs in many details.
> >
> > In too many details, I'm afraid.
>
> *At the level* we're talking about (UML diagrams!), it doesn't really
> matter if *redisplay* is *implemented* differently. The problems
> encountered are the same, and it fits into the LISP read-eval-print
> loop in basically the same way. (Ie, it's not actually a R-E-P loop,
> it's based on a GUI event loop with the R being "receive event" and P
> being "redisplay", and the E has to take account of being event-
> driven.) I could be wrong, but it's my understanding that it is that
> kind of thing that the OP wants to get a handle on.
I'm not sure. The general ideas are the same, that's true, but they
typically occupy only the first few sentences. Once you get past
that, you get differences in names of structures, functions, and even
file names, let alone basic mechanisms that implement the same general
ideas. So if one wants to look up the details in the code, one
cannot, and the detailed descriptions of the algorithms don't match
what Emacs does in many cases.
> Nor would it hurt the OP to see concepts that Emacs has rejected
> (extents and specifiers, for example), not to mention some of the
> things Emacs is currently in the process of thinking about adding
> (loadable modules) and even some of the things we've kinda horked and
> hopefully y'all will do better ("native" widgets).
I agree, but that should hardly be recommended as the first reading.
IMO, anyway.
next prev parent reply other threads:[~2010-07-08 9:44 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mxu271et.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=frenzeee@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 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.