all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jimmy Wong <wyuenho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dev@rjt.dev, casouri@gmail.com, 63086@debbugs.gnu.org
Subject: bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock
Date: Wed, 26 Apr 2023 14:44:51 +0100	[thread overview]
Message-ID: <d05bb2fc-adbf-4ab0-b711-5e7c29af9738@Spark> (raw)
In-Reply-To: <83edo6u5kj.fsf@gnu.org>

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

There hasn’t been any new releases since then, should emacs rely on devel packages?
On 26 Apr 2023 at 2:37 PM +0100, Eli Zaretskii <eliz@gnu.org>, wrote:
> > Date: Wed, 26 Apr 2023 14:26:09 +0100
> > From: Jimmy Wong <wyuenho@gmail.com>
> > Cc: Yuan Fu <casouri@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
> > 63086@debbugs.gnu.org
> >
> > I’m using tree-sitter-go 0.19.1 from Macports.
>
> That version was released 2 years ago. Maybe go-ts-mode.el relies on
> some newer functionality, or on some bug that was fixed since then?

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

  reply	other threads:[~2023-04-26 13:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 10:00 bug#63086: 29.0.90; go-ts-mode treesit-query-error during jit-lock Jimmy Yuen Ho Wong
2023-04-26 10:36 ` Eli Zaretskii
2023-04-26 11:07   ` Jimmy Wong
2023-04-26 12:38     ` Randy Taylor
2023-04-26 13:26       ` Jimmy Wong
2023-04-26 13:38         ` Eli Zaretskii
2023-04-26 13:44           ` Jimmy Wong [this message]
2023-04-26 14:05             ` Randy Taylor
2023-04-26 15:40               ` Randy Taylor
2023-04-27  6:36                 ` Jimmy Wong
2023-04-28  0:16               ` Dmitry Gutov
2023-04-28  1:35                 ` Randy Taylor
2023-04-28 10:05                   ` Dmitry Gutov
2023-05-02  0:29                     ` Randy Taylor
2023-05-03 21:58                       ` Dmitry Gutov

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=d05bb2fc-adbf-4ab0-b711-5e7c29af9738@Spark \
    --to=wyuenho@gmail.com \
    --cc=63086@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=dev@rjt.dev \
    --cc=eliz@gnu.org \
    /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.