unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: tree-sitter and emacs-devel
Date: Thu, 02 Apr 2020 19:24:43 +0300	[thread overview]
Message-ID: <83ftdlyhx0.fsf@gnu.org> (raw)
In-Reply-To: <jwvmu7top9u.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 02 Apr 2020 12:01:38 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 02 Apr 2020 12:01:38 -0400
> 
> FWIW, re-reading over the discussions around emacs-tree-sitter of the
> last few days, I must say I'm not proud: if I were a contributor to
> tree-sitter and/or emacs-tree-sitter, all this squabbling over how
> tree-sitter "should" work (from people who have not been involved in
> either of those and don't have any practical experience of how it
> performs or why it's designed that way) would make me run away screaming
> and promising myself never to come back to that mad house.

I actually think that this discussion brought up several important
issues and topics (and I don't mean my own messages) that should be
considered if such technology is to become part of Emacs (and I very
much hope it will).  Yes, there's quite a bit of noise, as in any
discussion, but that's inevitable.  The alternative is to invent your
own wheel each time, and make all the same mistakes.

I remember a similar situation on the emacs-bidi mailing list 15 years
ago when the bidirectional editing support for Emacs was just a pipe
dream.  Many of the ideas expressed there I tossed, but some are now
part of our implementation, and I'm glad I had the opportunity to hear
them.  I'm also glad that Gerd Moellmann was there to provide his
perspective on what would and what wouldn't be viable, I would have
never arrived at the current design without his guidance, not without
making several grave mistakes anyway.



  parent reply	other threads:[~2020-04-02 16:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 16:01 tree-sitter and emacs-devel Stefan Monnier
2020-04-02 16:12 ` Jorge Javier Araya Navarro
2020-04-02 16:24 ` Eli Zaretskii [this message]
2020-04-02 17:07   ` andres.ramirez
2020-04-03  5:07     ` Jorge Javier Araya Navarro
2020-04-03 13:43   ` Stefan Monnier
2020-04-03 14:12     ` Eli Zaretskii
2020-04-03 15:13       ` Stefan Monnier
2020-04-04  8:15         ` Eli Zaretskii
2020-04-04 18:00           ` Stefan Monnier
2020-04-03 14:57 ` Tuấn-Anh Nguyễn
2020-04-04  1:27   ` Richard Stallman

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=83ftdlyhx0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).