From: Ken Raeburn <raeburn@raeburn.org>
Subject: Re: Simulating a multithreaded Emacs with creative lisp..
Date: Thu, 07 Feb 2002 17:23:20 -0500 [thread overview]
Message-ID: <tx13d0dgcdj.fsf@raeburn.org> (raw)
In-Reply-To: <200202030440.g134edG01976@aztec.santafe.edu> (Richard Stallman's message of "Sat, 2 Feb 2002 21:40:39 -0700 (MST)")
> One of the major problems with Emacs is that it is not
> multithreaded. If you call a synchronous function your entire
> Emacs is locked up until it finishes.
> That is true. It would be very useful to make Emacs multithreaded,
> but it's a big job. So we are waiting for someone to do it.
Guile supports multiple threads, at least on some platforms. It's why
I started on that bit of Emacs hacking in the first place -- the
possibility that someday I might be able to edit files while Gnus is
fetching and sorting my mail, without rewriting Gnus from scratch and
without running multiple Emacsen. It does have interesting
implications for dynamic variable bindings, and lots of other fun
issues, but I won't get into that right now.
Unfortunately, I haven't had enough time for this work in quite a
while.
With the Emacs repository open, perhaps I could set up a branch there
now, for other people to work on? It would take me a little time to
re-synchronize so that CVS merging can work smoothly, but I'd like to
get it out there. It'll be a long-term project, I think, so we'll
need some strategy for keeping it synchronized now and then with the
main trunk, but I can send some notes on what I've been doing so far.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
parent reply other threads:[~2002-02-07 22:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200202030440.g134edG01976@aztec.santafe.edu>]
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=tx13d0dgcdj.fsf@raeburn.org \
--to=raeburn@raeburn.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).