🚀 go-pugleaf

I'm interested in version 19 from a design perspective.
Actually, it's not version 19, I'm interested in, but
the "perfect emacs".

Specifically, has anyone thought about putting in 
multiple elisp threads. If I write a particularly 
long running elisp program, then it ties up my 
emacs session and doesn't even give me an up to 
date screen to look at. Anyone thought of ways
to get around this.

How does the control-g, abort command work? Is it
different from other keystrokes in that it can 
interrupt the an elisp thread of control? Can
an elisp thread of control then be resumed again?
Could this be considered the beginnings of 
multi-threaded emacs? Ie. a timer could go off
and interuppt an elisp thread and then context
switch to another thread.

This is interesting, but then all of the concurrency
control problems like locking and deadlock come up.
Is there a way to have asynchrony, but insulate the naive
elisp routine writer from this?

Comments?

--
Peter Ham			PO Box 3430	(h)(415) 322-4390
MS Computer Science Student	Stanford, CA	ham@cs.stanford.edu
Stanford University 		94309		(o)(415) 723-2067