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

C# colors don't match #86

Open
Nekketsu opened this issue Sep 14, 2022 · 6 comments
Open

C# colors don't match #86

Nekketsu opened this issue Sep 14, 2022 · 6 comments

Comments

@Nekketsu
Copy link

Nekketsu commented Sep 14, 2022

This image is from VSCode:
image

This image is from Mofiqul/vscode.nvim:
image

As you can see, most of the pink colors in the plugin are blue in VSCode. Is it posible to fix it?

@redfoggg
Copy link

redfoggg commented Oct 10, 2022

I think it is possible to fix this with not that much of an effort, if I get some free time I will try to do it.

@Nekketsu
Copy link
Author

Nekketsu commented Oct 23, 2022

Any news about it?
Could you please give me a hint or how to solve it by overriding the group_overrides?
I tried something like this, but it seems that is not working:

    group_overrides = {
        -- this supports the same val table as vim.api.nvim_set_hl
        -- use colors from this colorscheme by requiring vscode.colors!
        -- Cursor = { fg=c.vscDarkBlue, bg=c.vscLightGreen, bold=true },
        ["@keyword"] = { fg = c.vscBlue, bg = c.vscNone },
        ["@include"] = { fg = c.vscBlue, bg = c.vscNone },
        ["@keyword.return"] = { fg = c.vscPink, bg = c.vscNone }
    }

@Nekketsu
Copy link
Author

It is working. I had to change the order in which I load the colorscheme and the plugin config. First set colorscheme to vscode, and then load plugin configuration and the overrides:

-- require('config.vscode')
require('config.colorscheme')
require('config.vscode')

@bryankenote
Copy link
Contributor

This seems to have improved recently. Maybe #181? Are there any differences that still exist that can be documented here?

@johannesrld
Copy link
Contributor

I can take a look later to see what can be improved, there are still some differences between the original vscode theme and this theme that I haven't fixed, but some of them require custom scheme highlight queries (for example C# and Javascripts => for arrow functions is highlighted as a keyword in vscode but if you want that in neovim you'd have to make custom scheme queries)

@johannesrld
Copy link
Contributor

Also vscode itself is rather inconsistent with its highlighting, in the above example the IrcClient constructor function in C# is highlighted with the same green that types and classes are highlighted with, however in typescript and javascript the constructor() function is highlighted with the same blue that non-control flow keywords are highlighted with, currently vscode.nvim (intentionally) highlights constructors with blue instead of green. There isn't really any way to solve this without introducing a bunch of extra definitions for different languages, which I don't think is a good use of anyones time (and honestly I value consistency over being a 100% faithful recreation)

There are also places where I think VSCodes original highlighting is just straight up stupid like with CSS selectors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants