-
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
Simple way to disable builtin method/prop highlighting #60
Comments
Perhaps a more flexible approach is to avoid linking these highlight groups directly in the syntax files, but instead cluster them into a small number of categories that are easy to link in
Then specific implementation syntax files could add their own things to these (for node.js, Personally, I could then comment out all
|
I am going to refactor this part. Some info for you. |
Awesome, for now I'll work around it. |
Since the performance issue on neovim. But my idea is beside your suggestion. |
I prefer not to highlight all the known methods and props of built-in objects. Many of them are too generic and conflict with unrelated code, creating pretty things like this:
(Not to mention that sometimes a keyword is highlighted differently based on context, as you can see with
parent
: in one case it is part ofjavascriptGlobals
, in another it is ajavascriptBOMWindowProp
, but really it should not be highlighted at all).I haven't found a setting to disable them. I could comment out all the
/syntax/yajs/*
includes, but that also removes useful things like the global functions themselves (I would like to keep Map, but not Map.get).The text was updated successfully, but these errors were encountered: