unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: U'll Be King Of The Stars <ullbeking@andrewnesbit.org>
To: emacs-devel@gnu.org
Subject: Minimal functional Emacs
Date: Thu, 4 Mar 2021 22:38:11 +0000	[thread overview]
Message-ID: <5afa7c70-fef0-0112-af2d-1958507d8892@andrewnesbit.org> (raw)

Hello all!

Please skip to "My question..." below the "====" line if you're not
interested in personal or background context.

I have been following this list on and off for more than twenty years.
Text editors interest me very much.

My "rite of passage" projects when I was a much younger and
inexperienced developer was to analyze the source code of different
editors and to write my own text editors.  Of course all roads led me
back to Emacs ;-)

I read the C core and the Elisp layer on top of this many times.
Personally I believe it's a masterpiece of software engineering.  Not
only this, but I learned a lot about how I would write requirements and
specifications for text editors[*].

Sources for this education include the GNU Emacs source code, reading
mailing lists and Usenet groups, Craig Finseth's book, and reading about
other Emacs editors, including their source code where available, e.g.,
Edwin and Hemlock.

======================================================================

My question...

I want to perform an experiment on text editor requirements and
specifications.  The first part would be to create a minimal working
editor based on GNU Emacs.  It would include the C core, the Elisp layer
(implementation of the Elisp manual), and few modes.  It would include
Fundamental mode and not many else, expect for those that support the
core specifications.

Has anybody done this before?

If "yes", please could you provide a link?

If the answer is "unknown", then I guess there is no secret except to
understand the Emacs build process and modify this.  Is this the right
direction?  This is documented well, e.g., in the Elisp manual.

After I've achieved this, I expect that the next stages will become
easier to tease out.  [*]Part of this involves documenting the
requirements and specifications I mentioned above.

Hints or tips would be greatly appreciated.  Thank you!!

Kind regards,

Andrew



             reply	other threads:[~2021-03-04 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 22:38 U'll Be King Of The Stars [this message]
2021-03-05  6:42 ` Minimal functional Emacs Eli Zaretskii
2021-03-05 11:47 ` Thien-Thi Nguyen
2021-03-05 13:46   ` emacs22 migration to VMS (was: Minimal functional Emacs) andrés ramírez
2021-03-05 18:21     ` emacs22 migration to VMS Thien-Thi Nguyen
2021-03-05 15:24   ` Minimal functional Emacs Stefan Monnier

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=5afa7c70-fef0-0112-af2d-1958507d8892@andrewnesbit.org \
    --to=ullbeking@andrewnesbit.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).