all messages for Emacs-related lists mirrored at yhetil.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: emacs-tree-sitter and Emacs
Date: Mon, 30 Mar 2020 11:00:05 -0600	[thread overview]
Message-ID: <CAAxewyjYPYXnfO4jG37fx1cPoY_DhwckCGXzs6BzvzjGCF=54w@mail.gmail.com> (raw)
In-Reply-To: <jwvh7y6q6w8.fsf-monnier+emacs@gnu.org>

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

I see, so in your opinion having a central engine won't be a bad
architecture design for Emacs despite major modes having their own engine.

I wonder: is possible for any other package to "take the wheel" from major
modes when it comes to indentation or a better approach would be offering
facilities for package authors and maintainers to outsource their
indentation to this central tree-sitter-based indentation engine?

I'm trying to picture how this would look like.

El lun., 30 de mar. de 2020 a la(s) 08:11, Stefan Monnier (
monnier@iro.umontreal.ca) escribió:

> > First off, in the issue tracker we have a ticket open for making this
> > project available on GNU ELPA, Ubolonton seems willing to make that
> > a reality
>
> That would be neat.
>
> > but this package has some special requirements that would make
> > impossible to submit it to GNU ELPA or MELPA, for instance, we need to
> > ship with grammars for some languages that require compiling and AFAIK
> > there is no way to build external dependencies in *ELPA.[1]
>
> Indeed, the GNU ELPA infrastructure is too weak to support such a thing
> right now, but that's a problem we need to fix anyway, so it just means
> we should work on it.
>
> > Finally, I'm planning to tackle indentation for my next pull request.
> > It come as a surprise that Emacs has no "central" indentation engine
> > but that instead each major mode ships with its own indentation
> > engine.
>
> It's not so surprising if you think about it: indentation requires
> parsing, so "a central indentation engine" requires something like
> tree-sitter ;-)
>
> SMIE is the closest there is so far (contrary to tree-sitter it uses
> a very simple parsing strategy, which is just barely sufficient for
> "typical" indentation cases).
>
> CC-mode has another engine, which is used for several languages.
>
> And finally, there's `wisi` on GNU ELPA, it aims to be very generic and
> pretty flexible, but AFAIK it's only used by `ada-mode` so far.
>
>
>         Stefan
>
>

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

  reply	other threads:[~2020-03-30 17:00 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  3:23 emacs-tree-sitter and Emacs Jorge Javier Araya Navarro
2020-03-30 13:07 ` Eli Zaretskii
2020-03-30 14:00   ` Stefan Monnier
2020-04-01  0:08     ` Stephen Leake
2020-04-01  0:27   ` Stephen Leake
2020-04-01 13:20     ` Eli Zaretskii
2020-04-01 19:51       ` Stephen Leake
2020-04-02 14:03         ` Eli Zaretskii
2020-04-02 14:27           ` Michael Welsh Duggan
2020-04-02 15:15             ` Eli Zaretskii
2020-04-02 15:24               ` Michael Welsh Duggan
2020-04-02 16:10                 ` Eli Zaretskii
2020-04-02 16:19                   ` Michael Welsh Duggan
2020-04-02 17:18                     ` Yuan Fu
2020-04-02 17:39                       ` Stefan Monnier
2020-04-02 18:17                         ` Yuan Fu
2020-04-02 18:26                           ` Stefan Monnier
2020-04-03  2:16                           ` Stephen Leake
2020-04-02 18:29                       ` Eli Zaretskii
2020-04-02 18:27                     ` Eli Zaretskii
2020-04-02 18:50                       ` Michael Welsh Duggan
2020-04-02 19:03                         ` Eli Zaretskii
2020-04-02 19:39                           ` 조성빈
2020-04-03  6:37                             ` Eli Zaretskii
2020-04-03 17:27                               ` Stephen Leake
2020-04-02 19:48                           ` Stefan Monnier
2020-04-03  2:06               ` Stephen Leake
2020-04-03  7:33                 ` Eli Zaretskii
2020-04-03 17:24                   ` Stephen Leake
2020-04-03 18:39                     ` Eli Zaretskii
2020-04-02 15:33             ` martin rudalics
2020-04-03  1:55           ` Stephen Leake
2020-04-03  4:47             ` Jorge Javier Araya Navarro
2020-04-03  7:32             ` Eli Zaretskii
2020-04-03 17:05               ` Stephen Leake
2020-04-03 18:19                 ` Eli Zaretskii
2020-04-04  0:00                   ` Stephen Leake
2020-04-01 13:28     ` Stefan Monnier
2020-03-30 14:11 ` Stefan Monnier
2020-03-30 17:00   ` Jorge Javier Araya Navarro [this message]
2020-03-30 17:07     ` Dmitry Gutov
2020-03-30 17:09       ` Jorge Javier Araya Navarro
2020-03-30 17:22     ` Stefan Monnier
2020-03-30 17:34       ` Jorge Javier Araya Navarro
2020-03-30 17:50       ` Stefan Monnier
2020-04-01  0:30       ` Stephen Leake

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAxewyjYPYXnfO4jG37fx1cPoY_DhwckCGXzs6BzvzjGCF=54w@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.