unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jorge Javier Araya Navarro <jorge@esavara.cr>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: tree-sitter and emacs-devel
Date: Thu, 2 Apr 2020 10:12:19 -0600	[thread overview]
Message-ID: <CAAxewyi=Sv+GYVW9tmjuBMkheM+FgADU8yH8H0M7z-EOLSiWTA@mail.gmail.com> (raw)
In-Reply-To: <jwvmu7top9u.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

I'll stick with emacs-devel anyway and keep contributing to
emacs-tree-sitter too jaja.

it is demoralizing indeed, but it is more not bringing Emacs to the XXI
century. We can do incremental changes after testing how this thing works
—not need to discuss what is and what is not a premature optimization—,
Emacs maintainers can help by making sure major GNU/Linux distributions
ship Emacs with dynamic module feature turned on so the work done on this
side can be rapidly adopted by the community; what's done wrong can be
revisited later.

El jue., 2 de abril de 2020 10:02, Stefan Monnier <monnier@iro.umontreal.ca>
escribió:

> 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.
>
> The worst part for me is to realize that I was mostly on the side of the
> backseat drivers :-(
>
>
>         Stefan
>
>
>

[-- Attachment #2: Type: text/html, Size: 1642 bytes --]

  reply	other threads:[~2020-04-02 16:12 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 [this message]
2020-04-02 16:24 ` Eli Zaretskii
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='CAAxewyi=Sv+GYVW9tmjuBMkheM+FgADU8yH8H0M7z-EOLSiWTA@mail.gmail.com' \
    --to=jorge@esavara.cr \
    --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).