jint_lzxy_

@Saafo Does #1305 resolve this issue for u? I can't seem to reproduce it anymore with Nvim 0.10 lol

> Sorry for the late reply, currently I'm busy with internship work so I have little time to participate in discussions. And best of luck with ur internship lol!

> But I see that the issue that prevents me from using nvim as a basic text editor still exist. Once there's some issues with nvim-treesitter, I cannot use nvim...

> The LSP servers, linters and formatters can actually be installed in system-wide on most systems, which means they are executable everywhere and maybe we just don't need mason at...

> Maybe ask user whether to install stuffs manually or by mason, store the choice and enable mason if that is `true`? Yeah that's what I meant by "optional," but...

> Maybe we can add an option as "platform" in our custom `lazy.nvim` loader and utilized the `enabled` flag in `lazy.nvim`? If `platform = {"XXX OS" = false}` is not...

After some consideration, I've decided to create a plugin that automates the control of those "bridging plugins" (like `mason-null-ls.nvim`). I'll share the link to the Reddit post here once it's...

@nullchilly Sure! In fact, I plan to open a PR upstream after this PR is merged. The plan is to adjust those treesitter highlights according to the [color palette document](https://github.com/catppuccin/nvim#overwriting-colors)...

I'm placing the "what's changed" table here to help me better store & track the changes I've made. Perhaps it can also help facilitate some discussions 👍 Sometimes builtin constants...

[Track the latest commits here!](https://github.com/Jint-lzxy/nvim)