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

final keyword syntax highlight should be different than type highlight #116

Open
Chaitanyabsprip opened this issue Dec 12, 2020 · 7 comments

Comments

@Chaitanyabsprip
Copy link

image

@Kavantix
Copy link
Contributor

Kavantix commented Feb 8, 2021

Which theme are you using because this might be cause by the theme you are using, which perhaps does not support dart yet

@Chaitanyabsprip
Copy link
Author

I was using ayu at the time.

@Kavantix
Copy link
Contributor

Kavantix commented Feb 8, 2021

So I guess you switched?
Does it work with your current theme?

@Chaitanyabsprip
Copy link
Author

it does work with my current theme, I am using horizon. But the highlighting part is done by treesitter as I am on development version of neovim.

@imambungo
Copy link

imambungo commented Feb 2, 2022

+1, class should have a unique color.

1 color for class, 1 color for function, 1 for string, white or default color for property. I don't care about the others.

Currently keywords like late, const, final, class, extends, @override have the same color as class.

I rather have all other keywords have the same color than the class color mixed with some keywords.

Good lord have mercy:
image

@AdrienLemaire
Copy link
Contributor

AdrienLemaire commented Jul 28, 2022

I'm getting the same syntax coloration as @imambungo using base16-tomorrow-night.

Thanks @Chaitanyabsprip for the tip, I uninstalled dart-vim-plugin to use coc-flutter with nvim-treesitter, and it looks better.

@AdrienLemaire
Copy link
Contributor

I still have syntax coloration issues for type hints at the end of lines

I wish these hints would be in gray too.

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