all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: wkirschbaum@gmail.com, 72863@debbugs.gnu.org, mail@ssbb.me
Subject: bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code
Date: Sun, 08 Sep 2024 08:54:11 +0300	[thread overview]
Message-ID: <86seuawv0c.fsf@gnu.org> (raw)
In-Reply-To: <6B5BA7D6-743D-4B12-903B-2852423A3C00@gmail.com> (message from Yuan Fu on Sat, 7 Sep 2024 22:44:53 -0700)

> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 7 Sep 2024 22:44:53 -0700
> Cc: Wilhelm Kirschbaum <wkirschbaum@gmail.com>,
>  Eli Zaretskii <eliz@gnu.org>,
>  72863@debbugs.gnu.org
> 
> Meanwhile, I want to push the fix for the other bug I discovered to emacs-30. Eli, I wrote a debugging function that prints parser states, naturally this function isn’t called anywhere so there’ll be a compiler warning, what should I do in this case?

Why would there be a compiler warning?  What kind of warning?





  reply	other threads:[~2024-09-08  5:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29  2:57 bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code mail
2024-08-29  5:09 ` Eli Zaretskii
2024-08-29  6:13   ` Wilhelm Kirschbaum
2024-08-29  6:14   ` Yuan Fu
2024-09-04  6:39     ` Wilhelm Kirschbaum
2024-09-04  7:42       ` mail
2024-09-05  4:32         ` Yuan Fu
2024-09-08  5:44           ` Yuan Fu
2024-09-08  5:54             ` Eli Zaretskii [this message]
2024-09-08  5:57               ` Yuan Fu
2024-09-08  7:02                 ` Eli Zaretskii
2024-09-08  7:48                   ` Yuan Fu
2024-09-11  3:45                     ` Yuan Fu
2024-09-11 19:22                       ` mail
2024-09-12  7:47                         ` Yuan Fu
2024-09-16  6:58                           ` Wilhelm Kirschbaum

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=86seuawv0c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72863@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=mail@ssbb.me \
    --cc=wkirschbaum@gmail.com \
    /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.