From: Yuan Fu <casouri@gmail.com>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 58755@debbugs.gnu.org
Subject: bug#58755: 29.0.50; Font locking not enabling for ts-mode
Date: Mon, 24 Oct 2022 13:16:43 -0700 [thread overview]
Message-ID: <18A2D8C1-3F7D-4D23-8BC9-A368A8C95A92@gmail.com> (raw)
In-Reply-To: <877d0p65nr.fsf@thornhill.no>
> On Oct 24, 2022, at 12:29 AM, Theodor Thornhill <theo@thornhill.no> wrote:
>
> Yuan Fu <casouri@gmail.com> writes:
>
>>> On Oct 23, 2022, at 11:43 PM, Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org> wrote:
>>>
>>> Hi Yuan!
>>>
>>> It seems we cannot really enable font-lock without setting the
>>> font-lock-defaults to some non-nil value.
>>>
>>> I'm not really sure why the 'treesit-font-lock-enable' isn't sufficient,
>>> but here's a patch that at least makes ts-mode usable again :)
>>>
>>> Thanks,
>>> Theo
>>
>> Hey Theo, sorry for the trouble… Yeah font-lock-mode looks at font-lock-default’s value when turning on and won’t do anything if it’s value is nil. I thought we are going to install a new scheme soon so I didn’t change the code. I’ll fix ts-mode and push.
>>
>
> No worries. Did we decide upon something there?
>
> Theo
No, not yet. I still think a central variable has more merits and less problems than minor modes as they are now. We’ll need discussion and more good ideas :-)
Yuan
prev parent reply other threads:[~2022-10-24 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 6:43 bug#58755: 29.0.50; Font locking not enabling for ts-mode Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-24 7:15 ` Yuan Fu
2022-10-24 7:29 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-24 20:16 ` Yuan Fu [this message]
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=18A2D8C1-3F7D-4D23-8BC9-A368A8C95A92@gmail.com \
--to=casouri@gmail.com \
--cc=58755@debbugs.gnu.org \
--cc=theo@thornhill.no \
/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).