public
Description: redit will be an editor written in Ruby with extensibility in mind.
Homepage: http://goto.cwru.edu/
Clone URL: git://github.com/jleedev/redit.git
mrdomino (author)
Tue Nov 18 16:58:09 -0800 2008
commit  2245d02d5cf3e514a805fa80b1f439a145099554
tree    2dcd66c20bc687d825eb79ebf7775c08754c573b
parent  faf41d24dcaa6f625b2557564e53a87058fa9fc4
redit /
name age message
file AUTHORS Mon Nov 03 21:49:36 -0800 2008 Added me to AUTHORS. [Josh Lee]
file COPYING Mon Nov 03 21:48:45 -0800 2008 license! [mrdomino]
file HACKING Mon Nov 17 08:05:23 -0800 2008 cat HACKING >> README; make HACKING into HACKING [mrdomino]
file README Loading commit data...
directory bin/ Mon Nov 17 07:28:25 -0800 2008 Made bin/redit actually run. [jleedev]
directory lib/
directory test/ Mon Nov 03 21:46:36 -0800 2008 all of the tests [mrdomino]
README
redit is an editor written in Ruby with extensibility in mind.

We are a couple of Vim hackers who have never quite managed to acclimate
ourselves to Emacs, and who, like most, have developed a distaste for
Vim script.

Our general strategy here is going to be to start mostly from scratch,
with an awareness of how we want our editor to behave but mostly
disregarding the implementation details of Vim, Emacs, or anything else
currently used to edit text.

One strategy for building a text editor is to recapitulate the evolution
of text editors in miniature---that is, build from a line editor to a
visual editor to a GUI editor to a semantic object-aware editor. This
gets enterprisey very quickly.

We are going to take a slightly different tack: roughly, we will grow in
two dimensions, progressing in the direction of usability and visual
fluency on the one hand and in the direction of object-awareness on the
other. The resulting program should then be beautiful, usable, and
powerful, or else incomplete.