Syntax highlighting for non-treesitter filetypes

[aorith]

Hi!

I'm not sure what is the root cause, but with this new structure of placing the configuration under plugin/ + the main branch of treesitter, files that previously had syntax highlighting after opening it, now need an implicit :e or :set ft=<lang> to work.

For example, nginx configuration files, either autodetected or with an modeline # vim: ft=nginx.

Of course if I add it to the ensure_languages treesitter configuration and provided there is a parser for the language it works, but previously if I'm not mistaken the vim regex syntax took place.

At the end, I'm a bit lost on how to properly enable it for languages not listed in the treesitter config. I've tested it with the current 0.11 configuration of MiniMax without modifications, and if my eyes do not lie to me I think that I see the highlight for a split millisecond upon opening a file.

<3 mini

[echasnovski]

For example, nginx configuration files, either autodetected or with an modeline # vim: ft=nginx.

Of course if I add it to the ensure_languages treesitter configuration and provided there is a parser for the language it works, but previously if I'm not mistaken the vim regex syntax took place.

I am not sure I can reproduce this on fresh install of MiniMax. For example, doing something like NVIM_APPNAME=nvim-minimax nvim -- nginx.conf shows 'nginx.conf' contents (a single line user www www;) with built-in syntax highlighting. Which is expected, because basic (a.k.a. "legacy") highlighting is explicitly enabled.

Could you, please, provide more details about how you can reproduce this? In particular:

• Do you use clean MiniMax install? I.e. do you have anything else tweaked?
• What Neovim version do you use? Ideally, see it by running :version when inside session where you can reproduce the issue.
• With which file content and name can you see this with?
• How do you open Neovim to reproduce this issue? Is it NVIM_APPNAME=nvim-minimax nvim -- config.nix or do you open plain Neovim and then open the file?

[aorith]

I've just tested it again, and it's really weird, I can reproduce it with a fresh MiniMax install, using neovim v0.11.4 from homebrew (I was about to blame my custom nvim using nix) but only if my terminal emulator is running a light theme (tested in ghostty and alacritty) so I get the light version of miniwinter. I guess the mechanism to switch to the light theme messes things up?

So to reproduce:

1. Terminal with light theme
2. Clean MiniMax install
3. Open it with: NVIM_APPNAME=nvim-minimax nvim -- nginx.conf

EDIT: It also happens if I have an init.lua file with just: vim.cmd.colorscheme("default"), but it does not happen if the init.lua is empty.

[aorith]

I opened an issue on neovim since it's not directly related to the MiniMax distribution, but with the bundled themes on vim and neovim, so sorry for the noise: neovim/neovim#36210

[echasnovski]

That's... A very odd timing: neovim/neovim#36211 :)

[echasnovski]

In the meantime, you can do the following:

• Explicitly set vim.o.background = 'light' before sourcing color scheme.
• Make a PR into 'vim/vim' patching 'syntax/nginx.vim' to have hi def link instead of hi link.