From: a.phillip.garcia@gmail.com (A. P. Garcia)
Subject: [TUHS] Unix taste (Re: terminal - just for fun)
Date: Sun, 3 Aug 2014 03:00:11 -0500 [thread overview]
Message-ID: <CAFCBnZvOpCMM1--w8DOKgf-jekkLZ4ro1iTRT13zNeNg33HfYg@mail.gmail.com> (raw)
In-Reply-To: <20140803004800.A747818C0A7@mercury.lcs.mit.edu>
On Aug 2, 2014 7:48 PM, "Noel Chiappa" <jnc at mercury.lcs.mit.edu> wrote:
<snip>
> Well, there is a companion 'compiler' which converts extension source into
> the intermediate form (byte-code) which is interpreted by the editor. But
> it's even smaller (67KB!) and as fast as the editor itself.
>
> > I was pleasantly surprised that it does have one, and that it's a c
> > derivative ... "Extensible and modifiable" doesn't always mean the
same
> > thing to everyone, and well, you're a kernel hacker.
>
> Take a quick look at a source file, e.g. one of mine:
>
> http://ana-3.lcs.mit.edu/~jnc/tech/cmd.e
>
> and you'll see i) what it's like (except for a few new editing-specific
> keywords, such as 'on <key>' in function definitions, it's pretty much C),
> and ii) it will give you a sense of the kind of things one writes in it,
and
> how easy it is to do so.
>
> The underlying run-time basically just provides buffer, display, etc
> primitives, and pretty much all the actual editor commands are written in
the
> 'extension' languge, even simple things like 'forward character' (^F),
etc.
> The complete manual is available online, the run-time system is described
> here:
>
> http://www.lugaru.com/man/Primitives.and.EEL.Subroutines.html
>
> Epsilon comes (as of a few versions back, I haven't bothered to upgrade)
with
> about 22K lines of source, which is the bulk of the actual editor; that
turns
> into about 190KB of intermediate code.
the spirit of emacs without the bloat :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140803/0b7b3198/attachment.html>
next prev parent reply other threads:[~2014-08-03 8:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 0:48 Noel Chiappa
2014-08-02 21:18 ` Noel Chiappa
2014-08-02 23:44 ` A. P. Garcia
2014-08-03 2:18 ` [TUHS] EMACS clones (was: Unix taste (Re: terminal - just for fun)) Greg 'groggy' Lehey
2014-08-03 8:00 ` A. P. Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 22:24 [TUHS] Unix taste (Re: terminal - just for fun) Norman Wilson
2014-08-06 22:19 Norman Wilson
2014-08-04 20:21 Norman Wilson
2014-08-04 22:24 ` A. P. Garcia
2014-08-05 2:41 ` Andy Kosela
2014-08-05 3:32 ` Warner Losh
2014-08-04 2:54 Norman Wilson
2014-08-04 3:11 ` Lyndon Nerenberg
2014-08-04 7:04 ` Dave Horsfall
2014-08-04 9:12 ` Steve Nickolas
2014-08-03 16:48 Noel Chiappa
2014-08-03 17:09 ` John Cowan
2014-08-03 11:49 Noel Chiappa
2014-08-03 12:14 ` Steve Nickolas
2014-08-03 16:26 ` John Cowan
2014-08-04 13:59 ` Tim Bradshaw
2014-08-04 14:53 ` A. P. Garcia
2014-08-02 16:47 Noel Chiappa
2014-08-02 18:51 ` Ian King
2014-08-02 14:28 Doug McIlroy
2014-08-02 14:00 ` Larry McVoy
2014-08-02 15:51 ` Steve Nickolas
2014-08-02 16:07 ` John Cowan
2014-08-02 17:28 ` Benjamin Huntsman
2014-08-02 19:50 ` Dave Horsfall
2014-08-02 16:04 ` Diomidis Spinellis
2014-08-02 16:03 ` Larry McVoy
2014-08-02 19:36 ` Dave Horsfall
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=CAFCBnZvOpCMM1--w8DOKgf-jekkLZ4ro1iTRT13zNeNg33HfYg@mail.gmail.com \
--to=a.phillip.garcia@gmail.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.
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 NNTP newsgroup(s).