From: Tony Day <zygomega@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs devel <emacs-devel@gnu.org>
Subject: Re: emacs roadmap
Date: Tue, 18 Dec 2012 12:36:07 +1100 [thread overview]
Message-ID: <09655BCF-9C06-4ABC-904A-FCE78028E28C@gmail.com> (raw)
In-Reply-To: <jwv7goh76n0.fsf-monnier+emacs@gnu.org>
> Lexical closures are supported natively since Emacs-24. Namespaces are
> another beast altogether, and there's not much on the horizon there either.
Ok, so now I understand defvar, lol. Not much use of lexical scoping in the wild - this was all I could find: http://github.com/nicferrier/elnode
>> - first-class print for functions?
>
> Not sure what that would be.
>
ELISP> (defun foo()
'(1 2 3))
ELISP> (as-string 'foo)
(defun foo()
'(1 2 3))
Would be very useful for debugging.
>> 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.
Tounge was slightly in cheek. What annoys me 100 times a day is having to switch away from the emacs environment to a browser and I was imagining that the technical difficulties involved in getting a decent browser rendering might coincide with the point at which C is needed to get closer to the *nix machine metal. I'm half hoping that things like guile 2 pushing lisp further down the chain might one day lead to an emacs os (a personal preference not a recommendation).
next prev parent reply other threads:[~2012-12-18 1: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
2012-12-18 1:36 ` Tony Day [this message]
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=09655BCF-9C06-4ABC-904A-FCE78028E28C@gmail.com \
--to=zygomega@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).