Hi.
On Feb 2, 2008 6:23 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Please fork it. We're all adults, and know how to use killfiles.
If
the traffic warrants it, I'll be happy to reactivate xemacs-design. I
don't want this private. Be aware that there *may* be *some* money
available for such work. Google SoC is one obvious avenue for those
with social or professional connections to university CS programs, and
there are also some private sector possibilities for specific features.
Are there any plans for having a multi-threaded XEmacs? That would
require fundamental changes in the elisp to make operations on it
thread safe and reentrant.
A very simple use case I have experienced is when opening large
files. Users would usually start reading from the top, if the reading
was async-threaded, a lazy loading of the file could have been
achieved. Well, with such support, XEmacs can become a good general
purpose programmable engine!
-dky
--
Contents reflect my personal views only!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta