From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.bugs
Subject: bug#74412: 31.0.50; Treesit-outline conflict with outli in Emacs 31
Date: Tue, 19 Nov 2024 17:37:31 +0200
Message-ID: <86r077tetg.fsf@gnu.org>
References: <9e9fcc46-e6ca-42e6-bb0e-6770ae65f150@gmail.com>
 <86h684vi6l.fsf@gnu.org> <7a42b50d-39f1-4628-a1d6-eb036946ee8a@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="26400"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: 74412@debbugs.gnu.org
To: Taka Obsid <liaotx2@gmail.com>, Yuan Fu <casouri@gmail.com>
Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 19 16:38:39 2024
Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>
Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>)
	id 1tDQJF-0006Zu-Od
	for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 19 Nov 2024 16:38:34 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <bug-gnu-emacs-bounces@gnu.org>)
	id 1tDQIw-0005sy-6M; Tue, 19 Nov 2024 10:38:14 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1tDQIl-0005rv-Pe
 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2024 10:38:04 -0500
Original-Received: from debbugs.gnu.org ([2001:470:142:5::43])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1tDQIl-0000lE-GN
 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2024 10:38:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
 d=debbugs.gnu.org; s=debbugs-gnu-org; 
 h=MIME-version:References:In-Reply-To:From:Date:To:Subject;
 bh=SDtqvS+VGTO9okKaQg3tMIGENSpTH6x2vNMt6Z/NLEY=; 
 b=pXrB0GIzAbgx0NJvQrdSmH2WQiHjal5CdYPG4ZbM8WXuemipBw5Ny/gm9r6kR8UBHdtDwnlG3HZ2652nCYOQGN99ws/a86twUY/1+13aMdPRcR57sNxpgnnBU50mOa4ehpdoOnLcksIqCKuhi9JKrP44GnQpU7+QF32dPDbbilMgLmfBRypj4DpnnaEOgS0hhseFbhT2t0afqY3QvOop5odXyhFsE651UWi6bg2Hzlya10ffRSvmosY21smjVpWP36CtMDiC5JCEP5H27KtdZA9Mmv/vcm4o2jXlfUcLcvYhZ2Mj/aBSdtMd91WX0qCvOSwIbmVBbU5qn2Ubg8qd/g==;
Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1tDQIk-00040i-BE
 for bug-gnu-emacs@gnu.org; Tue, 19 Nov 2024 10:38:02 -0500
X-Loop: help-debbugs@gnu.org
Resent-From: Eli Zaretskii <eliz@gnu.org>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@gnu.org
Resent-Date: Tue, 19 Nov 2024 15:38:02 +0000
Resent-Message-ID: <handler.74412.B74412.173203066115375@debbugs.gnu.org>
Resent-Sender: help-debbugs@gnu.org
X-GNU-PR-Message: followup 74412
X-GNU-PR-Package: emacs
Original-Received: via spool by 74412-submit@debbugs.gnu.org id=B74412.173203066115375
 (code B ref 74412); Tue, 19 Nov 2024 15:38:02 +0000
Original-Received: (at 74412) by debbugs.gnu.org; 19 Nov 2024 15:37:41 +0000
Original-Received: from localhost ([127.0.0.1]:43693 helo=debbugs.gnu.org)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
 id 1tDQIP-0003zu-6g
 for submit@debbugs.gnu.org; Tue, 19 Nov 2024 10:37:41 -0500
Original-Received: from eggs.gnu.org ([209.51.188.92]:43282)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@gnu.org>) id 1tDQIN-0003zh-0e
 for 74412@debbugs.gnu.org; Tue, 19 Nov 2024 10:37:39 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1tDQIH-0000gx-Pg; Tue, 19 Nov 2024 10:37:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From:
 Date; bh=SDtqvS+VGTO9okKaQg3tMIGENSpTH6x2vNMt6Z/NLEY=; b=a35f8WMfK/LAHBJZeT39
 mEWH300s4sEuwXDHdgu60K4fIVR+MvlLAbQgpV2bDX48LNhLy7IVPYSRMIx35Nr2goS4hRZ9Mn2vv
 ptiXjcxMTLj/N/Z/XP4kiAlUWtBi0zc8brH2yFhCMv4hyuEyN2M9igXw2mwwsB+elXcHFhqhPRVFo
 KEoFPVA+a3lK3OlQlv4RFqeQucfo3KvNxQGD5McMeHMJw/SHffOiXyh8h6Ftc0FK2mnxf/xU/gbiq
 3NxdxMyKHBaIKj5AUMDJJMMkMz0pf2AJFGBgXeedcVU7W2NdOvP4aqxCBJlYfWbQyTlwS87JBfi+Z
 dxa4XF659zhSLQ==;
In-Reply-To: <7a42b50d-39f1-4628-a1d6-eb036946ee8a@gmail.com> (message from
 Taka Obsid on Tue, 19 Nov 2024 09:47:34 +0800)
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
X-BeenThere: bug-gnu-emacs@gnu.org
List-Id: "Bug reports for GNU Emacs,
 the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-gnu-emacs>
List-Post: <mailto:bug-gnu-emacs@gnu.org>
List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe>
Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org
Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.bugs:295640
Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/295640>

> Date: Tue, 19 Nov 2024 09:47:34 +0800
> Cc: 74412@debbugs.gnu.org
> From: Taka Obsid <liaotx2@gmail.com>
> 
> Yes, I have reported it in https://github.com/jdtsmith/outli/issues/17 and the developer
> recommended me to file this bug report. This is what he said:
> 
> > This seems to be a new conflict with Emacs 31, and potentially a problem with treesit-outline. 
> > Can you please file an Emacs bug report and link it here?

Yuan, could you please take a look?

> 在 2024/11/18 20:29, Eli Zaretskii 写道:
> 
>  Date: Mon, 18 Nov 2024 10:59:00 +0800
> From: Taka Obsid <liaotx2@gmail.com>
> 
> Hi, I'm using `java-ts-mode' and https://github.com/jdtsmith/outli.
> 
> While I tried to `revert-buffer' in a java file, it reports
> `outline-map-region: Wrong type argument: number-or-marker-p, nil'.
> 
> The backtrace is:
> 
> ```bt
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> #f(compiled-function () #<bytecode -0x1964e0de811a96ab>)()
> outline-map-region(#f(compiled-function () #<bytecode 
> -0x1964e0de811a96ab>) 1 31382)
> outline--hidden-headings-paths()
> outline-revert-buffer-restore-visibility()
> #f(compiled-function (f) #<bytecode 
> 0x6badcbe8273644b>)(outline-revert-buffer-restore-visibility)
> run-hook-wrapped(#f(compiled-function (f) #<bytecode 0x6badcbe8273644b>) 
> outline-revert-buffer-restore-visibility)
> revert-buffer(t)
> funcall-interactively(revert-buffer t)
> call-interactively(revert-buffer record nil)
> command-execute(revert-buffer record)
> execute-extended-command(nil "revert-buffer" "rev")
> funcall-interactively(execute-extended-command nil "revert-buffer" "rev")
> call-interactively(execute-extended-command nil nil)
> command-execute(execute-extended-command)
> ```
> 
> To repreduce it:
> 
> 1. start Emacs with `java-ts-mode' and `outli' installed;
> 
> 2. go to a java file;
> 
> 3. `M-x outli-mode';
> 
> 4. `M-x revert-buffer'.
> 
> The `outline-search-function' is `#'treesit-outline-search' and while I
> set it to `nil', I can successfully revert the buffer.
> 
> 
> ```
> emacs -q --eval "(progn
> (add-to-list 'load-path \"/path/to/java-ts-mode/\")
> (add-to-list 'load-path \"/path/to/outli/\")
> (require 'java-ts-mode)
> (require 'outli))"
> ```
> 
> 
> Thanks, this seems to be a problem in the outli package?  Because the
> error is signaled by one of its functions (a hook it places on
> revert-buffer-function, I guess?).
> 
> Did you report this to the developer of outli?  If not, I suggest to
> report it there first.