From: Eli Zaretskii <eliz@gnu.org>
To: Emanuele Santoro <manu@santoro.tk>
Cc: emacs-devel@gnu.org
Subject: Re: Exploring the GNU Emacs codebase
Date: Fri, 08 Jul 2016 21:33:37 +0300 [thread overview]
Message-ID: <837fcwhtdq.fsf@gnu.org> (raw)
In-Reply-To: <577FDC2C.1000700@santoro.tk> (message from Emanuele Santoro on Fri, 8 Jul 2016 19:00:28 +0200)
> From: Emanuele Santoro <manu@santoro.tk>
> Date: Fri, 8 Jul 2016 19:00:28 +0200
>
> I was wondering if there is some more documentation (besides the README
> file) in order to understand the internals of Emacs.
>
> My main area of interest at the moment is how GNU Emacs manages
> buffers.
The ELisp manual has a chapter on internals. But most of that is in
code comments; for buffers, see src/buffer.c and src/buffer.h.
prev parent reply other threads:[~2016-07-08 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 17:00 Exploring the GNU Emacs codebase Emanuele Santoro
2016-07-08 18:06 ` Phillip Lord
2016-07-08 18:33 ` Eli Zaretskii [this message]
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=837fcwhtdq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manu@santoro.tk \
/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).