all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66223@debbugs.gnu.org
Subject: bug#66223: treesit-major-mode-setup should not call font-lock-mode
Date: Wed, 27 Sep 2023 21:55:24 -0700	[thread overview]
Message-ID: <457CAAB8-124C-4369-BA1E-A0EE7EA98AF2@gmail.com> (raw)
In-Reply-To: <41F82630-B664-4195-BA0D-A1701C6C9CB7@gnu.org>



> On Sep 27, 2023, at 8:40 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> On September 28, 2023 2:23:41 AM GMT+02:00, Yuan Fu <casouri@gmail.com> wrote:
>> 
>> 
>>> On Sep 27, 2023, at 1:51 AM, Dmitry Gutov <dmitry@gutov.dev> wrote:
>>> 
>>> On 27/09/2023 10:21, Yuan Fu wrote:
>>>> Makes sense. We can remove that line in master, and see if anything comes up. I don’t remember why I added it, I don’t think there was any particular reason.
>>> 
>>> If we have to start on master, so be it. I'd like to see the fix in emacs-29, though (at least eventually).
>> 
>> Yeah, let’s test this out on master for a while and apply it to emacs-29 if no one comes up and complain. It seems to me that 29.2 is still a while away.
> 
> Actually, it isn't: I was thinking about starting a pretest soon.

Thanks for the heads up. We’ll need to remember to add that change before the pretest is cut, then.

Yuan




  reply	other threads:[~2023-09-28  4:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  0:17 bug#66223: treesit-major-mode-setup should not call font-lock-mode Dmitry Gutov
2023-09-27  7:21 ` Yuan Fu
2023-09-27  8:51   ` Dmitry Gutov
2023-09-27 11:15     ` Stefan Kangas
2023-09-27 19:42       ` Dmitry Gutov
2023-09-28  0:23     ` Yuan Fu
2023-09-28  3:40       ` Eli Zaretskii
2023-09-28  4:55         ` Yuan Fu [this message]
2023-10-08 23:03       ` Yuan Fu
2023-10-08 23:05         ` Dmitry Gutov
2023-10-09  5:04           ` Yuan Fu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=457CAAB8-124C-4369-BA1E-A0EE7EA98AF2@gmail.com \
    --to=casouri@gmail.com \
    --cc=66223@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.