GNU bug report logs - #73264
tree-sitter shows jit-lock-function error when i delete some code

Previous Next

Package: emacs;

Reported by: vinurs <hi <at> vinurs.me>

Date: Sun, 15 Sep 2024 06:07:02 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #13 received at 73264-done <at> debbugs.gnu.org (full text, mbox):

From: Yuan Fu <casouri <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 73264-done <at> debbugs.gnu.org, vinurs <hi <at> vinurs.me>
Subject: Re: bug#73264: tree-sitter shows jit-lock-function error when i
 delete some code
Date: Sun, 15 Sep 2024 00:44:10 -0700

> On Sep 14, 2024, at 11:36 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
>> Date: Sun, 15 Sep 2024 14:06:22 +0800
>> From: vinurs <hi <at> vinurs.me>
>> 
>> I am using the latest emacs-30
>> https://github.com/emacs-mirror/emacs/commit/81347c1aaf25b27e78e8beee4bc818ad2c4e1b71
>> 
>> The min configuration is as follows:
>> 
>> (add-to-list 'treesit-extra-load-path (expand-file-name "tree-sitter/" user-emacs-directory))
>> 
>> (add-to-list 'load-path "~/.emacs.d/site-lisp/clojure-ts-mode”)
>> 
>> (require 'clojure-ts-mode)
>> 
>> ;; debug
>> 
>> (setq debug-on-quit t)
>> 
>> and I only use clojure-ts-mode package
>> 
>> cd ~/.emacs.d/site-lisp
>> 
>> git clone https://github.com/clojure-emacs/clojure-ts-mode.git
>> 
>> Then, after opening Emacs, Open the elong.clj file, go to line 115, select the entire
>> build-inventory-check-failure-response function, and then delete this function. You'll notice that the remaining
>> code is no longer highlighted. Then I found the following error output in the Message buffer:
>> 
>> Error during redisplay: (jit-lock-function 4221) signaled (wrong-type-argument number-or-marker-p nil) [2
>> times
> 
> Thanks.
> 
> Since clojure-ts-mode is not part of Emacs, please report this to the
> developers of clojure-ts-mode instead.
> 
> I'm therefore closing this bug.  If the developers of clojure-ts-mode
> conclude that the underlying problem is in core Emacs, we can reopen
> this bug with the details of their analysis and conclusions.

(Cough cough) Actually that’s my fault. But I’ve now fixed it on emacs-30 and added some more tests. Thanks for the report!

Yuan



This bug report was last modified 247 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.