Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all of the token groups are covered #159

Closed
dmtrKovalenko opened this issue Jan 1, 2025 · 2 comments
Closed

Not all of the token groups are covered #159

dmtrKovalenko opened this issue Jan 1, 2025 · 2 comments
Labels
autoclosed No activity for more than 7 days with the "waiting for op" label. bug Something isn't working waiting for op This issue is waiting for a response from the original poster

Comments

@dmtrKovalenko
Copy link
Contributor

Description

Here is an example code using tokyonight
image

and here is cyberdream version

image

which makes it a total mess. Same thing usually happen with rust imporst

image

vs cyberdream
image

Neovim version?

NVIM v0.10.3 Build type: Release LuaJIT 2.1.1734355927 Run "nvim -V1 -v" for more info

What should happen?

No response

What happened instead?

I would expect all the different tokens from the poopulare palettes like catppuccin adn tokyonight to have different colors because it sometimes looks clunky.

If you know what exactly is missing I can try to play around with palette options

Your configuration

{
    "scottmckendry/cyberdream.nvim",
    enabled = theme == "cyberdream",
    lazy = false,
    priority = 1000,
    opts = {
      borderless_telescope = false,
      theme = {
        saturation = 0.95,
      },
    },
    init = function()
      vim.cmd "colorscheme cyberdream"
      vim.api.nvim_set_hl(0, "TroubleNormal", { bg = "none", ctermbg = "none" })
      vim.api.nvim_set_hl(0, "TroubleNormalNC", { bg = "none", ctermbg = "none" })
      vim.api.nvim_set_hl(0, "WinSeparator", { fg = "#3c4048", bg = "none" })
      vim.api.nvim_set_hl(0, "IndentBlanklineChar", { fg = "#7b8496" })
      vim.api.nvim_set_hl(0, "TreesitterContext", { bg = "#232429" })
      vim.api.nvim_set_hl(0, "TreesitterContextLineNumber", { bg = "#232429" })
      vim.api.nvim_set_hl(0, "TreesitterContextBottom", { bg = "#232429", underline = true })
    end,
  }
@dmtrKovalenko dmtrKovalenko added the bug Something isn't working label Jan 1, 2025
@scottmckendry
Copy link
Owner

scottmckendry commented Jan 1, 2025

Hey @dmtrKovalenko, thanks for raising this one.

The easiest way to determine the missing/incorrect groups in these situations is to move the cursor over the token and run :Inspect.

:InspectTree does the same, but will render the entire AST in another window.

I suspect most of these are using defautl fallback links. Very few are defined in treesitter.lua so I am more than happy to accept a PR that expands on these.

@scottmckendry
Copy link
Owner

@dmtrKovalenko this should be resolved now - or at least better - for the two examples in your screenshots. Please take a look and let me know what you think. Happy to keep tweaking till we get something suitable 🙂

@scottmckendry scottmckendry added the waiting for op This issue is waiting for a response from the original poster label Jan 4, 2025
@github-actions github-actions bot added the autoclosed No activity for more than 7 days with the "waiting for op" label. label Jan 12, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoclosed No activity for more than 7 days with the "waiting for op" label. bug Something isn't working waiting for op This issue is waiting for a response from the original poster
Projects
None yet
Development

No branches or pull requests

2 participants