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

Feature: Semantic highlighting #49

Open
AraneusRota opened this issue Aug 24, 2023 · 0 comments · May be fixed by #50
Open

Feature: Semantic highlighting #49

AraneusRota opened this issue Aug 24, 2023 · 0 comments · May be fixed by #50

Comments

@AraneusRota
Copy link

Implement IntelliJ's semantic highlighting for all symbols and keywords.

Further links:
https://blog.jetbrains.com/pycharm/2017/01/make-sense-of-your-variables-at-a-glance-with-semantic-highlighting/
https://plugins.jetbrains.com/docs/intellij/syntax-highlighting-and-error-highlighting.html#semantic-highlighting

AraneusRota added a commit to AraneusRota/clj-extras-plugin that referenced this issue Aug 24, 2023
Works for all symbols and keywords. Namespaces are treated as separate highlighted elements. For symbols that was the behaviour by default and for keywords the ns range had to be manually added.
@AraneusRota AraneusRota linked a pull request Aug 24, 2023 that will close this issue
AraneusRota added a commit to AraneusRota/clj-extras-plugin that referenced this issue Mar 29, 2024
Works for all symbols and keywords. Namespaces are treated as separate highlighted elements. For symbols that was the behaviour by default and for keywords the ns range had to be manually added.
AraneusRota added a commit to AraneusRota/clj-extras-plugin that referenced this issue Apr 25, 2024
Works for all symbols and keywords. Namespaces are treated as separate highlighted elements. For symbols that was the behaviour by default and for keywords the ns range had to be manually added.
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

Successfully merging a pull request may close this issue.

1 participant