From: Richard Stallman <rms@gnu.org>
Cc: <emacs-devel@gnu.org>
Subject: Re: Documentation for the code
Date: Sun, 30 Jun 2002 14:53:17 -0600 (MDT) [thread overview]
Message-ID: <200206302053.g5UKrHR05624@aztec.santafe.edu> (raw)
In-Reply-To: <001001c21f67$4b2f9fa0$a3ac4bd8@freddy> (yffchik@student.math.uwaterloo.ca)
I am a newbie to emacs dev and I have trouble trying to find
the documentation (to see the overall design and stuff), things
in the info dir sounds more like user manuals than code
documentation.
There is a little internal documentation for the editor at the end of
the Emacs Lisp Manual.
prev parent reply other threads:[~2002-06-30 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 12:20 Documentation for the code Freddy Chik
2002-06-29 12:31 ` Paul Stoeber
2002-06-29 13:05 ` Freddy Chik
2002-06-30 20:53 ` Richard Stallman [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=200206302053.g5UKrHR05624@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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).