all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chad Brown <yandros@MIT.EDU>
To: Fren Zeee <frenzeee@gmail.com>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Common vs Emacs Lisp (was: Re: return)
Date: Fri, 3 Dec 2010 19:04:13 -0800	[thread overview]
Message-ID: <13199CAD-97D4-4B3B-969E-788713D4C1A2@mit.edu> (raw)
In-Reply-To: <AANLkTinMyOdmHOqej8GwAVzc_n1MCnyitnyWAOmOc07f@mail.gmail.com>

On Dec 3, 2010, at 6:36 PM, Fren Zeee wrote:
> 
> Why not just throw the whole elisp and use CL to run emacs with
> lexical scoping ?
> 
> What particular advantages do there accrue from the dyn scoped elisp
> and by incrementally making fixes to this dinosaur ?

Conservatively, I'll say at least 10,000 programmer-hours of existing, heavily
used (by emacs standards) elisp libraries, systems, programs, etc.

There are/have been projects that recreate emacs in Scheme, Common 
Lisp, and Tcl (that I know of).  None of them have done very well when
forced head-to-head with Emacs (Tcl doing the best, due to environment).

I suspect that I'd get widespread agreement from emacs developers to
a statement like the following:

	Common Lisp contains some good stuff that I'd like to see in Emacs 
	and a large amount of stuff that I'd never want to see in Emacs, even
	if it meant giving up the former.

..and that assumes that someone else magically does the work.

For CL in particular, it looks like Climacs could use some help.

*Chad


  reply	other threads:[~2010-12-04  3:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26  8:57 return Lars Magne Ingebrigtsen
2010-11-26  9:19 ` return Tassilo Horn
2010-12-04  2:36   ` return Fren Zeee
2010-12-04  3:04     ` Chad Brown [this message]
2010-12-04 19:48       ` Common vs Emacs Lisp (was: Re: return) Fren Zeee
2010-12-05 10:20         ` Chad Brown
2010-12-04  6:18     ` return Stephen J. Turnbull
2010-12-04  6:49       ` return Leo
2010-11-26  9:24 ` return Miles Bader
2010-11-26  9:36   ` return Lars Magne Ingebrigtsen
2010-11-26  9:54     ` return Miles Bader
2010-11-26 10:13       ` return Lars Magne Ingebrigtsen
2010-11-26  9:44   ` return Tassilo Horn
2010-11-26 14:59 ` return Stefan Monnier
2010-11-26 15:45   ` return Lars Magne Ingebrigtsen
2010-11-26 18:40     ` return Stefan Monnier
2010-11-27  1:31       ` return Lars Magne Ingebrigtsen
2010-11-27  2:49         ` return Stefan Monnier
2010-11-27  3:06           ` return Lars Magne Ingebrigtsen
2010-12-03 18:41             ` return Chong Yidong
2010-12-03 18:43               ` return Miles Bader
2010-12-03 19:46                 ` return Chong Yidong
2010-12-03 21:26                   ` return Chong Yidong
2010-12-03 22:29                     ` return Stefan Monnier
2010-12-03 23:00                       ` return Chong Yidong
2010-12-04  1:35                         ` return Stefan Monnier
2010-12-04  3:23                           ` return Chong Yidong
2010-12-06 16:13                         ` return Davis Herring
2010-12-06 17:15                           ` return Chong Yidong
2010-12-03 22:44                     ` return Chong Yidong
2010-12-04  9:22                       ` return Helmut Eller

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=13199CAD-97D4-4B3B-969E-788713D4C1A2@mit.edu \
    --to=yandros@mit.edu \
    --cc=emacs-devel@gnu.org \
    --cc=frenzeee@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.