emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#60305: closed (Help with hideshow)


From: GNU bug Tracking System
Subject: bug#60305: closed (Help with hideshow)
Date: Sun, 25 Dec 2022 17:59:03 +0000

Your message dated Sun, 25 Dec 2022 09:58:48 -0800
with message-id <6776FADF-9563-4D5C-95E3-50ABEEDB60C7@gmail.com>
and subject line Re: bug#60305: Help with hideshow
has caused the debbugs.gnu.org bug report #60305,
regarding Help with hideshow
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60305: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60305
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Help with hideshow Date: Sun, 25 Dec 2022 01:24:44 -0800
Is anyone familiar with hideshow? I tried to add tree-sitter support for it but 
didn’t quite make it. 

I just generalized some defun functions so that one can define a “thing” with a 
regexp that matches node types. So now it should be relatively straightforward 
for each major mode to define a “block” thing, like they do for defun, and a 
hideshow-treesitter bridge can use treesit-thing-at-point, 
treesit-beginning-of-thing, etc, to support hideshow.

It would be great if someone familiar with hideshow would like to give it a 
try, or educate me how to set hs-special-modes-alist.

On the separate note, I wonder if the hideshow support can go on the release 
branch.

Thanks,
Yuan


--- End Message ---
--- Begin Message --- Subject: Re: bug#60305: Help with hideshow Date: Sun, 25 Dec 2022 09:58:48 -0800
Oops, this some how got sent to debbugs, I’ll resend to emacs-devel.

> On Dec 25, 2022, at 1:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sun, 25 Dec 2022 01:24:44 -0800
>> 
>> On the separate note, I wonder if the hideshow support can go on the release 
>> branch.
> 
> It depends on what it will look like.  If the addition of that doesn't
> touch hideshow code used without tree-sitter, and if the tree-sitter
> support is opt-in, I think we can have it on the release branch -- if
> you manage to do this soon enough.  (I'm planning on a complete
> feature freeze on the release branch in a week or so.)

In that case, going on master is probably better. Hideshow isn’t that critical 
or game-changing.

Yuan

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]