From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: rusi Newsgroups: gmane.emacs.help Subject: Re: Issues with emacs Date: Fri, 22 Jun 2012 19:28:19 -0700 (PDT) Organization: http://groups.google.com Message-ID: <83c8afcc-bf74-4dcc-bb3f-8e24766ebf30@oe8g2000pbb.googlegroups.com> References: <87vcijcqqj.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1340420415 7238 80.91.229.3 (23 Jun 2012 03:00:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 23 Jun 2012 03:00:15 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jun 23 05:00:15 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SiGa4-0005xn-NG for geh-help-gnu-emacs@m.gmane.org; Sat, 23 Jun 2012 05:00:12 +0200 Original-Received: from localhost ([::1]:44399 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SiGa4-0003yL-HS for geh-help-gnu-emacs@m.gmane.org; Fri, 22 Jun 2012 23:00:12 -0400 Original-Path: usenet.stanford.edu!postnews.google.com!oe8g2000pbb.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 42 Original-NNTP-Posting-Host: 116.74.129.67 Original-X-Trace: posting.google.com 1340420265 23184 127.0.0.1 (23 Jun 2012 02:57:45 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 23 Jun 2012 02:57:45 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: oe8g2000pbb.googlegroups.com; posting-host=116.74.129.67; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0.1,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:192990 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:85386 Archived-At: On Jun 22, 8:26=A0pm, "Pascal J. Bourguignon" wrote: > rusi writes: > > On Jun 18, 7:32=A0am, S Boucher wrote: > >> I've been using emacs since as far back as 18.59.=A0 Still use it dail= y. > > >> However, I often wonder where Emacs is heading. > > > Ive been collecting some posts on this list that seemingly are > > questions about emacs but in fact point to deficiencies. Does one, > > two, hundred deficiencies make for a 'dying breed?' =A0Perhaps not and > > the question of S Boucher needs to be dealt with more conceptually/ > > philosophically. =A0Unfortunately such a discussion invariably > > degenerates into flaming/trolling. =A0So heres my bottom up list > > Some are contradictory. =A0Eg. reproaching lisp-2 and wanting more CL > support (of course, they're not made by the same people). > > lisp-2 is a good thing IMO. =A0http://www.nhplace.com/kent/Papers/Technic= al-Issues.html Thanks for that link... whether it actually says that lisp-2 is better is another matter > > What's bad, is that the promise of having different embedded languages > in emacs failed so far. =A0IMO because of lack of lexical binding/closure= s > (but this is resolved in emacs-24), and to a lesser degree, lack of a > usable namespace system (in this case, the obarray mechanism is there to > be used by language implementors). =A0But with emacs-24, it could be > possible to implement a scheme, a javascript and finish the emacs-cl > implementation, java, etc, so that people could use and program emacs in > their favorite programming language. Yes this is one of the important issues. If emacs were programmable in one of today's popular languages its developer-base would leap up. I believe however that trying to implement everything within emacs (elisp) itself is a much more ambitious project than simply providing bridges to existing implementations (eg python via pymacs)