You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Note:** The package `clojure-mode-extra-font-locking` provides such additional
300
+
font-locking for Clojure built-ins.
301
+
302
+
As you might imagine one problem with this font-locking approach is that because
303
+
it's based on regular expressions you'll get some false positives here and there
304
+
(there's no namespace information, and no way for `clojure-mode` to know what
305
+
var a symbol resolves to). That's why `clojure-mode`'s font-locking defaults are
306
+
conservative and minimalistic.
307
+
308
+
Precise font-locking requires additional data that can obtained from a running
309
+
REPL (that's how CIDER's [dynamic font-locking](https://docs.cider.mx/cider/config/syntax_highlighting.html) works) or from static code analysis.
310
+
311
+
When it comes to definitions, `clojure-mode` employs a simple heuristic and will treat every symbol named `def`something as a built-in keyword. Still, you'll need to
312
+
teach `clojure-mode` manually how to handle the docstrings of non built-in definition forms. Here's an example:
313
+
314
+
```emacs-lisp
315
+
(put '>defn 'clojure-doc-string-elt 2)
316
+
```
317
+
318
+
**Note:** The `clojure-doc-string-elt` attribute is processed by the function `clojure-font-lock-syntactic-face-function`.
319
+
261
320
## Refactoring support
262
321
263
322
The available refactorings were originally created and maintained by the
0 commit comments