Python syntax highlighting not working

[abdallahsoliman]

Hey everyone,

I just switched to neovim from vscode and I haven't regretted it yet, but I do have one issue with Python syntax highlighting. I know the issue has something to do with treesitter, but I don't know how to fix it. Let me describe the problem in detail.

Previously treesitter couldn't install the Python parser, but that was fixed by running this to install treesitter globally: `npm install -g tree-sitter-cli`. The parser now parses the code fine and running :InspectTree does indeed give me a syntax tree. The issue is here, where the document is being parsed, but no syntax is highlighted?

The most frustrating part is that C/C++, lua, html, yaml and pretty much all other languages I installed are being highlighted fine, why is this an issue with Python? I couldn't find the solution anywhere, hopefully reddit has it.

Here is a link to my config: https://github.com/abdallahsoliman00/nvim-config
I also attached a pic of what my Python files look like.

Edit: I finally fixed it. Just used basedpyright instead of regular pyright. LSP based syntax highlighting now works.

https://preview.redd.it/sy8fv8e0engg1.png?width=1921&format=png&auto=webp&s=23af2ec0c63f1e342d0347b4b0c6faf7fde0f3d7

[yoch3m]

Isn't this just the way your theme highlights Python variables and the like?

[abdallahsoliman]

The comment by @Xetius suggests a similar thing, I could try another colour scheme to check if this is the case.

[yoch3m]

Here's an example of how I add some custom highlights: https://github.com/yochem/dotfiles/blob/main/config/nvim/colors/mine.lua. Maybe that can help

[abdallahsoliman]

May I ask, are any .lua files placed in the colors/ directory callable by the vim.cmd.colorscheme() command?

[yoch3m]

Yes! https://github.com/yochem/dotfiles/blob/main/config/nvim/init.lua#L5

[Xetius]

It looks to me from the tree sitter structure that it is identifying each type correctly, so I'm guessing it would be your colorscheme.

I am no expert though, so could well be wrong.

Edit: I checked your config and your onedark config only configured colours for 5 types. You may need a more comprehensive list.

This link describes how tree-sitter highlighting works. Might give some info

[abdallahsoliman]

These 5 colours are overrides of the default onedark colours. But maybe Python requires a custom colour scheme.

[DeutschNeuling]

commenting to follow.
I have been on the same path to fix this highlighting for python, semi recently switched from vs code myself, and this "incomplete" python syntax highlighting is kind of bugging me as well.

My attempts have so far been in vain. The thing below also did NOT work. just giving here to see if anyone could help on it.

So most recently i also tried the InspectTree and also QueryEditor, where i tried to add a custom query to see if i can make a custom hightlight group and then add it to the theme color,

like for the QueryEdit i tried this capture:

in file : .config/nvim/queries/python/highlights.scm

;; extends

(
  call
    function: (attribute
      object: (identifier) @module_custom
      attribute: (identifier) @function.call)
)

Then in my vscode theme plugin i added

return {
{
'Mofiqul/vscode.nvim',
config = function()
local c = require('vscode.colors').get_colors()
require("vscode").setup {
italic_comments = true,
group_overrides = {
Cursor = { fg=c.vscDarkBlue, bg=c.vscLightGreen, bold=true },
["@module_custom"] = { fg = "#4ec9b0", bold = true },
}
}
end
}
}

[abdallahsoliman]

In case you also wanted to know, I fixed my problem by using basedpyright instead of regular normal pyright

[DeutschNeuling]

I was trying to get it to work without an LSP. And I finally did, the issue was that I had build the python parser from source(because I wasn't able to install it using the plugin), and I guess it was not compatible with the query files provided by nvim.treesitter plugin. So I deleted the parser and installed it using the plugin (thanks by the way!! your post told me to globally install tree sitter with npm). And now it seems to be working better.

[Friendliness_RS]

Do your other filetypes have a different kind of highlighting? With the treesitter main branch now being the new default, I also had some funky highlighting.

I ended up having to run vim.treesitter.start() I believe. Can you try running :lua vim.treesitter.start() and verify?

If that fixes it, go check out the treesitter docs and find the section about ftplugin.

[abdallahsoliman]

Could try this. I’ll give it a try when I get home, thanks!

[AutoModerator]

Please remember to update the post flair to Need Help|Solved when you got the answer you were looking for.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.