unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tony Day <tonyday567@gmail.com>
To: emacs devel <emacs-devel@gnu.org>
Subject: emacs roadmap
Date: Mon, 17 Dec 2012 09:25:39 +1100	[thread overview]
Message-ID: <m262414ot8.fsf@gmail.com> (raw)

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:

- Is multi-threading coming to emacs 25?
- Is there realistic support for replacing elisp with guile?  Is that
  considered possible even?
- If elisp is the future, what type of changes are envisaged?  
  - double escape regex fix? 
  - lexical closures (to support no namespaces)?
  - first-class print for functions?

More generally, when can we get turtles all the way down and enjoy the
return of the symbolic machine?



             reply	other threads:[~2012-12-16 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 22:25 Tony Day [this message]
2012-12-16 22:37 ` emacs roadmap Noah Lavine
2012-12-18  0:02   ` Tony Day
2012-12-17  2:36 ` Stefan Monnier
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

  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=m262414ot8.fsf@gmail.com \
    --to=tonyday567@gmail.com \
    --cc=emacs-devel@gnu.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).