This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-13
Channels
- # adventofcode (4)
- # announcements (1)
- # babashka (7)
- # beginners (51)
- # calva (18)
- # cider (15)
- # clj-kondo (1)
- # cljsrn (6)
- # clojure (99)
- # clojure-dev (31)
- # clojure-europe (5)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-nl (14)
- # clojure-seattle (8)
- # clojure-spec (6)
- # clojure-uk (2)
- # clojurescript (23)
- # conjure (3)
- # css (6)
- # data-science (3)
- # datomic (19)
- # events (6)
- # fulcro (13)
- # graalvm (5)
- # honeysql (24)
- # inf-clojure (19)
- # music (10)
- # off-topic (28)
- # pathom (10)
- # rdf (15)
- # re-frame (11)
- # releases (4)
- # sci (1)
- # shadow-cljs (18)
I've bumped it up to 1000 now, but according to my settings is was already set to 100. But I was getting more like 8.
How would one go about to use an add-tap
to add the cider repl to the tap set? I find this amazingly handy in reveal, but I don't always have it running.
@cdimara Just saw your message on discord and responded there. 🙂 Basically that's characters, not lines. For everyone else - https://docs.cider.mx/cider/1.0/repl/configuration.html#auto-trimming-the-repl-buffer
I have this in my emacs config:
;; Highlight particular macros similar to built-in stuff
;; For example, highlight ghostwheel's `>defn' similar
;; the same way as built-in `defn'
(add-hook 'clojure-mode-hook
'(lambda ()
;; Set some new syntax-highlighting rules.
(font-lock-add-keywords nil
;; So many escape codes! But we're really just saying:
;; Match the '(' character.
;; Match and group the string '>defn'.
;; Match some whitespace. \\s-+
;; Match and group some word characters. \\w+
'(("(\\(>defn\\)\\s-+\\(\\w+\\)"
;; The first regexp group is a keyword.
(1 font-lock-keyword-face)
;; The second regexp group is a name.
(2 font-lock-function-name-face))))))
I can't get the docstring highlight (yet) though
The docstring parsing is in clojure-mode
's clojure-font-lock-syntactic-face-function
.
Right, so is there a way to override the rules so >defn
is treated the same as defn
for example?
Ah, seems to work. Thanks (indentation is off, but that's a separate issue)
Is there any way to extend the parser without this hacky method?