-
Notifications
You must be signed in to change notification settings - Fork 42
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
New Github style? #9
Comments
Have they changed? |
there's a new official dark mode is that what this is referring to? |
No that is not what I meant. I was talking about the current default Github style. |
Did the colours on the light theme change? |
If anyone wants to do a 2020 fork, go ahead (but rename the fork once you have so people can install both at the same time). |
Well that's something specific I can comment on! If you're comparing a particular file between this scheme and GitHub.com, then almost any file will look at least a little different, and that has always been the case. I don't know that that counts as GitHub having changed. I make no claim that if you took a screenshot like this a year ago it would have looked identical. In any case, the goal is to use the GitHub colours and make a pleasing highlight, so I would absolutely have stopped there when trying to improve Python before. The colour palette hasn't changed that I know of, and that's what I was referring to above. GitHub has always used different code highlighting from Vim, and therefore different syntax groups. It's possible their new highlighting does more with Python than it used to using a tree sitter backend, so I'd recommend trying using the Neovim tree sitter stuff to get more semantic highlights. If you want to improve the Python syntax, again I would welcome a PR! |
looks like there's a fork to update some colours to the 2020 pallet: master...carlweis:master but that won't fix differences between highlighting groups.... |
Hi there, very nice theme. Are there plans to update it to reflect Github's style as of 2020?
The text was updated successfully, but these errors were encountered: