From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alessandro Piras Newsgroups: gmane.emacs.help Subject: Re: About Emacs Modernisation Project Date: Mon, 31 May 2010 20:41:04 +0100 Organization: news.babsi.de for www.open-news-network.org Message-ID: <8639x7x3jj.fsf@gmail.com> References: <143c6d28-4423-4e43-9fc5-c0fb3340043b@c11g2000vbe.googlegroups.com> <0e994fe3-6dde-449f-879d-6701c7a195a9@e28g2000vbd.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1291824495 5739 80.91.229.12 (8 Dec 2010 16:08:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2010 16:08: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 Wed Dec 08 17:08:10 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PQMYs-0002hC-ND for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 17:08:10 +0100 Original-Received: from localhost ([127.0.0.1]:32801 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQMYr-0000MG-S8 for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 11:08:10 -0500 Original-Path: usenet.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!news2.euro.net!newsfeed.freenet.ag!news.babsi.de!open-news-network.org!news2.open-news-network.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 39 Original-NNTP-Posting-Host: NTM2MTZjNzQ2NTY0NWY1ZjVlZGE1NTUyMTdkYzFiNmFhMmY1N2FiNmYzMTdhZmRjZTg3YTMzOWI0ZTNmZGViYw== Original-X-Trace: news2.open-news-network.org eJwNzMERwDAIA8GWEoMEKccG1H8J8ft2DsaXFU7QIWi/qoq2NqOiTMmeztEiZrJ9Fh8/LQyoPnnVzXWQOpXLYhfKZRH38/UPJUgb1Q== (31 May 2010 19:29:46 GMT) Original-X-Complaints-To: abuse@open-news-network.org Original-NNTP-Posting-Date: Mon, 31 May 2010 19:29:46 +0000 (UTC) X-User-ID: NTM2MTZjNzQ2NTY0NWY1ZmE5NDBjZGY2MTFkNTc4MWEzOTc5ZjllZTU2MGQzYWUwYjBjYWI5YjU0NWMzZGUxMGVlZWJmMTFkYjJhNWUyZDM= Cancel-Lock: sha1:aJSVXxwhgg6x9tuFFlnCUNd1BK4= sha1:S7X6HpEFYLiU+CIpozuyGuk3s+c= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (windows-nt) Original-Xref: usenet.stanford.edu gnu.emacs.help:178498 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:75584 Archived-At: LanX writes: > Hi > > I doubt that Python would be a good choice, Perl for instance has much > more in common with LISP. > > And I doubt that eLISP is the reason why many people have problems > with emacs, it's more that many "modern" GUI mechanisms and > terminologies are not default in emacs, which frustrates newbies. > > > IMHO an alternative (but compatible ) eLISP-dialect simply allowing to > swap parens and functionnames and to write "message(...)" instead of > "(message...)" would increase the acceptance immidiately. Sounds Like M-expressions. It has been tried in the past in the Lisp world, without much success. Most programmers realize after few time the sweetness of S-expressions and macros. I think it would just lead to a small amount of M-expressions code that would be soon refactored as S-expressions.. Not worth the effort I suspect. > > (just think of how the different syntaxes of VBScript and JScript run > on the same engine) > > But the biggest issue are the data structures, most "modern" script > languages have extensive support for _dynamic_ "hashes" and "arrays", > but not for "linked lists" which is the main structure in elisp. > > No real idea how this could be solved... > > cheers > Rolf > > PS: forgot to mention this Slasheritis in regexes, IIRC Xemacs has > already rawstrings while GnuEmacs users are forced to escape every > regex symbol at least twice... __ Alessandro