From: Juri Linkov <juri@linkov.net>
To: Yuan Fu <casouri@gmail.com>
Cc: "74412@debbugs.gnu.org" <74412@debbugs.gnu.org>,
"liaotx2@gmail.com" <liaotx2@gmail.com>,
Daan Ro <daanturo@gmail.com>
Subject: bug#74412: 31.0.50; Treesit-outline conflict with outli in Emacs 31
Date: Wed, 20 Nov 2024 20:25:59 +0200 [thread overview]
Message-ID: <87bjy9wymg.fsf@mail.linkov.net> (raw)
In-Reply-To: <EA496E38-B53D-4EDC-A972-DD693E36FEF1@getmailspring.com> (Daan Ro's message of "Thu, 21 Nov 2024 00:51:12 +0700")
Yuan, what do you think about adding a new option
that will allow disabling some features?
>>> Personally I also find treesit's decision to set outline variables
>>> somewhat intrusive. I have to advice `treesit-major-mode-setup` to
>>> disable that. If only there is an easier way to do it like the
>>> attached patch.
>>>
>>> +(defcustom treesit-enable-outline-settings t
>>> + "Non-nil means Tree sitter-based outline settings are enabled."
>>> + :type 'boolean
>>> + :version "31.1")
>>
>> Should such an option be more general and allow
>> disabling some other features too?
>>
>> There is already 'treesit-font-lock-recompute-features'.
>> So a new option could have a similar name, e.g.
>> 'treesit-disable-features' that the users could set to e.g.
>>
>> (setopt treesit-disable-features '(outline imenu))
>> So a new option could have a similar name, e.g.
>> 'treesit-disable-features' that the users could set to e.g.
>>
>> (setopt treesit-disable-features '(outline imenu))
>
> That's much better, indeed.
next prev parent reply other threads:[~2024-11-20 18:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 2:59 bug#74412: 31.0.50; Treesit-outline conflict with outli in Emacs 31 Taka Obsid
2024-11-18 12:29 ` Eli Zaretskii
2024-11-19 1:47 ` Taka Obsid
2024-11-19 15:37 ` Eli Zaretskii
2024-11-19 18:09 ` Juri Linkov
2024-11-20 3:34 ` Taka Obsid
2024-11-20 7:15 ` Juri Linkov
2024-11-20 14:06 ` Taka Obsid
2024-11-20 17:21 ` Juri Linkov
2024-11-20 18:23 ` Juri Linkov
2024-11-21 1:48 ` Taka Obsid
2024-11-21 6:51 ` Eli Zaretskii
2024-11-20 17:06 ` Daan Ro
2024-11-20 17:18 ` Juri Linkov
2024-11-20 17:51 ` Daan Ro
2024-11-20 18:25 ` Juri Linkov [this message]
2024-11-20 18:53 ` Eli Zaretskii
2024-11-20 18:50 ` Eli Zaretskii
2024-11-21 8:16 ` Daan Ro
2024-11-21 9:07 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bjy9wymg.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=74412@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=daanturo@gmail.com \
--cc=liaotx2@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).