From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: yyoncho Newsgroups: gmane.emacs.devel Subject: Re: are contributions on other programming languages than C and Emacs lisp bad idea? Date: Sun, 22 Sep 2019 22:01:41 +0300 Message-ID: References: <1427040605.4453251.1569007946448.ref@mail.yahoo.com> <1427040605.4453251.1569007946448@mail.yahoo.com> <865zlmq8ww.fsf@stephe-leake.org> <874l15fway.fsf@yahoo.com.mx> <83d0ftqyy4.fsf@gnu.org> <8736gpfid9.fsf@yahoo.com.mx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000b5abd7059328ef98" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="55364"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Jorge Javier Araya Navarro Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 22 21:02:10 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iC77Z-000EFp-9g for ged-emacs-devel@m.gmane.org; Sun, 22 Sep 2019 21:02:09 +0200 Original-Received: from localhost ([::1]:48384 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iC77X-0004AC-6A for ged-emacs-devel@m.gmane.org; Sun, 22 Sep 2019 15:02:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41195) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iC77O-00049u-VH for emacs-devel@gnu.org; Sun, 22 Sep 2019 15:02:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iC77N-0007u7-Jh for emacs-devel@gnu.org; Sun, 22 Sep 2019 15:01:58 -0400 Original-Received: from mail-lf1-x132.google.com ([2a00:1450:4864:20::132]:41816) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iC77L-0007s3-F1; Sun, 22 Sep 2019 15:01:55 -0400 Original-Received: by mail-lf1-x132.google.com with SMTP id r2so8422614lfn.8; Sun, 22 Sep 2019 12:01:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K68nY4Mzq0ZlC3Je+5LQjUvdnWJA+hjmF2msX2lFL0g=; b=c0j2RDoz0ZNQ75SPdd07Ln2KVofchXKs8KCjh1iblNN1bE8E/h7CE2f6owqQI/+4NS Kg7fLskDWMYmCh4HvbtHcW/lvP9nGc7MWUqf5Ux/ILhE2TZfmYmRAz/aIKaDUVfTVXTk jgry0W6KdkV2Sopf39b15k3Ep4nCgFB+F+zclWLuFiSl+qDdPg1fWOrABHvPrIr4xnUe LfU6lUnFu96GcVywDs8MBAvRoeOsO4SmqtP34FBT4EhAhsTqzA2L+0pam5KHj+09O+sA Vn905AhALhmD0vhfl8wE27sJdrFhmkKwESBJOWUrbnqVH0TQFMAAwniq0iBo4SJJk/oq hYIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K68nY4Mzq0ZlC3Je+5LQjUvdnWJA+hjmF2msX2lFL0g=; b=ShArabuHPcISzovw1xM/u2Je68zJCzYBGF9MfidbSKCql3vjzQMuw3ec593P7ZkPND rn9VnsPVlAZ4ex9D+B//cNnhnqOt2G5csUDkqLYWjEJ/VWZ4OS46XPRRRf6+EZd42WxM NKJyO61FcbBmTJd97Q2+keRLMRtRnqbwl9rDojjabUSvD5d2/kojLduoTDjZ8FHXk1/D SWA+aV6ow7WLirgt9pk2w8/po9pnE4m7DNgB7ONW2HaPwcjC4uIt9hGR0irpVbpeooyY eZJt60QymZIMhCCJV11EJbiMxtGTnmc+hGb+W8v2kQyQZqxCMrWvGHRYc1xkSOPJHX28 GRiw== X-Gm-Message-State: APjAAAXbgYUDdkrhiphKF5te7nnsOgJ2upxzGfRusTxmDE47wP59xQn9 Uqa8pYPml0N1w6iH0n7KtBE0HrhHgynU48hTHms= X-Google-Smtp-Source: APXvYqwD0fw4yjhcTcqNDT/xPZcuJ5B64cC7PO85iBG72QcSPBaE1l9xmZ2K1yc0+mq0ouK+L8Jilw3tAMYQJYQ6ThQ= X-Received: by 2002:ac2:551d:: with SMTP id j29mr14292086lfk.7.1569178913186; Sun, 22 Sep 2019 12:01:53 -0700 (PDT) In-Reply-To: <8736gpfid9.fsf@yahoo.com.mx> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::132 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:240248 Archived-At: --000000000000b5abd7059328ef98 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You might be interested in https://github.com/ubolonton/emacs-tree-sitter/ Thanks, Ivan On Sun, Sep 22, 2019 at 12:30 AM Jorge Javier Araya Navarro < jorgejavieran@yahoo.com.mx> wrote: > > > El s=C3=A1bado 21 de septiembre del 2019 a las 1236 horas, Eli Zaretskii > escribi=C3=B3: > > >> From: Jorge Javier Araya Navarro > >> Date: Sat, 21 Sep 2019 10:28:37 -0600 > >> > >> I'm actually looking to do something like this but for JavaScript, > there are several packages in > >> Rust that can help parsing JavaScript code and I thought this could > become handy and replace the > >> existing parsing written in Emacs Lisp. > > > > Are there any known problems with the ELisp implementation that > > justify reimplementing that in another language? > > None to my knowledge. There is people and projects doing cool stuff like > ecmascript[1] or > javascript_lexer[2] and I thought that leveraging from projects like thos= e > could provide any sort of > advantage to Emacs in speed, code maintenance or user experience. > > I will try to present a dynamic module and see how that goes, after doing > my due research on js.el > > [1]: https://crates.io/crates/ecmascript > [2]: https://crates.io/crates/javascript_lexer > --000000000000b5abd7059328ef98 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You might be interested in=C2=A0https://github.com/ubol= onton/emacs-tree-sitter/=C2=A0

Thanks,
Iva= n

On Sun, Sep 22, 2019 at 12:30 AM Jorge Javier Araya Navarro <jorgejavieran@y= ahoo.com.mx> wrote:


El s=C3=A1bado 21 de septiembre del 2019 a las 1236 horas, Eli Zaretskii es= cribi=C3=B3:

>> From: Jorge Javier Araya Navarro <jorgejavieran@yahoo.com.mx>
>> Date: Sat, 21 Sep 2019 10:28:37 -0600
>>
>> I'm actually looking to do something like this but for JavaScr= ipt, there are several packages in
>> Rust that can help parsing JavaScript code and I thought this coul= d become handy and replace the
>> existing parsing written in Emacs Lisp.
>
> Are there any known problems with the ELisp implementation that
> justify reimplementing that in another language?

None to my knowledge. There is people and projects doing cool stuff like ec= mascript[1] or
javascript_lexer[2] and I thought that leveraging from projects like those = could provide any sort of
advantage to Emacs in speed, code maintenance or user experience.

I will try to present a dynamic module and see how that goes, after doing m= y due research on js.el

[1]: https://crates.io/crates/ecmascript
[2]: https://crates.io/crates/javascript_lexer
--000000000000b5abd7059328ef98--