-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Only namespaces containing prefixes are fontlocked in the ns form #280
Comments
It's pretty hard to deal with this using regular expressions. Fixes welcome, but it's low on my todo list. |
Bear in mind that single-segment namespaces are strongly advised-against as they cause issues with AOT and JVM interop. |
@cichli That's debatable bbatsov/clojure-style-guide#100 |
Ah, was not aware that it did not actually cause problems in practice (although I seem to remember reading that how packageless classes are dealt with is JVM-dependent?). It definitely can cause serious, hard-to-debug, issues in clojurescript though:
|
You might want to mention this in the style guide issue. :-) On 11 March 2015 at 19:06, Michael Griffiths notifications@github.com
Best Regards, |
Is there any alternative font-locking mechanism for emacs that can be used when the context is hard to capture with a regex? |
You can use anything for the font-locking, but I've rarely seen modes that aren't 100% regexp based. The use of a parser or a live process obviously adds extra deps and people generally prefer simpler solutions. |
I guess I should point out that there are no single-segment namespaces in the OP. There is no support for syntax highlighting of libspecs in In the image in OP one can argue whether the prefix, |
This happens most often in prefix vectors but applies everywhere
The text was updated successfully, but these errors were encountered: