unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 74412@debbugs.gnu.org, liaotx2@gmail.com, daanturo@gmail.com
Subject: bug#74412: 31.0.50; Treesit-outline conflict with outli in Emacs 31
Date: Wed, 20 Nov 2024 20:53:07 +0200	[thread overview]
Message-ID: <86h681spnw.fsf@gnu.org> (raw)
In-Reply-To: <87serlzuvi.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 20 Nov 2024 19:18:41 +0200)

> Cc: "74412@debbugs.gnu.org" <74412@debbugs.gnu.org>,
>  "liaotx2@gmail.com" <liaotx2@gmail.com>
> From: Juri Linkov <juri@linkov.net>
> Date: Wed, 20 Nov 2024 19:18:41 +0200
> 
> > 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?

I don't see a need for an option at all.  All tree-sitter based modes
use these search functions, so treesit.el simply acts on their behalf
here.  It makes no sense to let users control how a major mode
customizes outline-minor-mode, because the major mode is supposed to
know how to adapt outlines with its main syntax, and what a heading
means in the context of that mode.





  parent reply	other threads:[~2024-11-20 18:53 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
2024-11-20 18:53     ` Eli Zaretskii [this message]
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=86h681spnw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74412@debbugs.gnu.org \
    --cc=daanturo@gmail.com \
    --cc=juri@linkov.net \
    --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).