all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: john muhl <jm@pub.pink>
Cc: theo@thornhill.no, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: lua-ts-mode
Date: Sat, 29 Jul 2023 13:46:00 +0300	[thread overview]
Message-ID: <838razm1w7.fsf@gnu.org> (raw)
In-Reply-To: <871qgscewi.fsf@pub.pink> (message from john muhl on Thu, 27 Jul 2023 16:52:47 -0500)

> From: john muhl <jm@pub.pink>
> Cc: theo@thornhill.no, emacs-devel@gnu.org
> Date: Thu, 27 Jul 2023 16:52:47 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > It isn't a prerequisite, no.  It just would be nice to be able to
> > support both.
> 
> Fair enough. I gave it a closer look and don’t think it’s possible to
> support even on its own. Try opening a file containing:
> 
>   print(1)
> 
> Enable treesit-explore-mode and see:
> 
>   (call
>    function: (variable name: (identifier))
>    arguments: (ERROR ( (number) ))      ; That ERROR node is erroneous
>    (argument_list (string)))
> 
> Those stray ERRORs are pervasive and all kinds of code end up with them
> in unexpected places. There may be other issues but this one is enough
> to make it unusable. I don’t think this is fixable on the Emacs side.
> 
> Another problem is that in an empty buffer Emacs freezes when you start
> typing. The Azganoth grammar and t-e-m must be enabled for it to freeze.
> This might be fixable in Emacs but wouldn’t change the problem with
> misplaced ERROR nodes.

Thanks, if that grammar is buggy to the degree that we cannot use it
in Emacs, then we don't need to support it, of course.



      reply	other threads:[~2023-07-29 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 16:49 [ELPA] New package: lua-ts-mode john muhl
2023-07-26 17:42 ` Theodor Thornhill
2023-07-27  4:43   ` Eli Zaretskii
2023-07-27 13:34     ` john muhl
2023-07-27 19:06       ` Eli Zaretskii
2023-07-27 21:52         ` john muhl
2023-07-29 10:46           ` Eli Zaretskii [this message]

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=838razm1w7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jm@pub.pink \
    --cc=theo@thornhill.no \
    /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.