From: robert.thorpe@antenova.com (Rob Thorpe)
Subject: Re: Emacs C source, suggested reading order
Date: 23 Jan 2004 19:25:50 -0800 [thread overview]
Message-ID: <1a61f7e5.0401231925.74ca10f1@posting.google.com> (raw)
In-Reply-To: m3u12mqlnh.fsf@localhost.localdomain
joao <joao@nospam.net> wrote in message news:<m3u12mqlnh.fsf@localhost.localdomain>...
> Hi all,
>
> I wanted to write some emacs lisp code to display the contents of registers,
> where I've saved several window configurations. I was thinking of a list of
> registers identified by a, b, c, ..., with, for each one, the names of the
> buffers/files displayed in each window.
>
> Unfortunately the Elisp Manual states clearly that
>
> Primitives to look inside of window configurations would
> make sense, but none are implemented. It is not clear they
> are useful enough to be worth implementing.
>
> So I guess it's time to start reading that Emacs C source code, so I can add
> the primitive I need. I've found the window config functions in window.c, but
> obviously there's a lot to understand in this (big) source.
>
> Does anyone have a suggested reading order in all these C source files ? are
> there some useful comments buried inside any particular file ? things like
> description/explanation of how lisp objects/functions are implemented in C ? or
> the interface between lisp and C ?
>
> Suggestions welcome. Otherwise I'll start with emacs.c :-)
Start with lisp.h, then read emacs.c or eval.c
I can't advise you further than that since I haven't got further myself!
next prev parent reply other threads:[~2004-01-24 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 23:40 Emacs C source, suggested reading order joao
2004-01-24 3:25 ` Rob Thorpe [this message]
2004-01-24 10:59 ` Eli Zaretskii
[not found] ` <mailman.1268.1074942248.928.help-gnu-emacs@gnu.org>
2004-01-24 13:20 ` joao
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=1a61f7e5.0401231925.74ca10f1@posting.google.com \
--to=robert.thorpe@antenova.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.