From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tony Day <tonyday567@gmail.com>
Cc: emacs devel <emacs-devel@gnu.org>
Subject: Re: emacs roadmap
Date: Sun, 16 Dec 2012 21:36:47 -0500 [thread overview]
Message-ID: <jwv7goh76n0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m262414ot8.fsf@gmail.com> (Tony Day's message of "Mon, 17 Dec 2012 09:25:39 +1100")
> Is there a long term roadmap for Emacs research and development that
> someone could point to? Having done my homework I find nothing out
> there except rumour and myth. For instance:
There isn't a very clear roadmap, indeed.
> - Is multi-threading coming to emacs 25?
Maybe not multi-threading, but I do hope to get some kind of concurrency
in there, yes.
> - Is there realistic support for replacing elisp with guile? Is that
> considered possible even?
Replacing Elisp with another language seems rather unlikely. As for
replacing the Elisp implementation with another one, e.g. based on the
Guile VM, that is indeed possible.
But there's nothing concrete on the horizon.
> - If elisp is the future, what type of changes are envisaged?
> - double escape regex fix?
Would be nice, but again: nothing concrete on the horizon.
> - lexical closures (to support no namespaces)?
Lexical closures are supported natively since Emacs-24. Namespaces are
another beast altogether, and there's not much on the horizon there either.
> - first-class print for functions?
Not sure what that would be.
> More generally, when can we get turtles all the way down and enjoy the
> return of the symbolic machine?
My experience with Lisp machines has been fairly limited, so I'm not
sure what would be the thing that is most sorely missing.
Stefan
next prev parent reply other threads:[~2012-12-17 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 22:25 emacs roadmap Tony Day
2012-12-16 22:37 ` Noah Lavine
2012-12-18 0:02 ` Tony Day
2012-12-17 2:36 ` Stefan Monnier [this message]
2012-12-18 1:36 ` Tony Day
2012-12-18 4:02 ` Stefan Monnier
2012-12-17 18:49 ` Tom Tromey
2012-12-18 0:05 ` Tony Day
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=jwv7goh76n0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=tonyday567@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.