This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-30
Channels
- # aws (4)
- # beginners (143)
- # boot (37)
- # cider (31)
- # cljs-dev (53)
- # clojure (303)
- # clojure-conj (5)
- # clojure-dev (106)
- # clojure-dusseldorf (2)
- # clojure-greece (3)
- # clojure-italy (23)
- # clojure-spec (83)
- # clojure-uk (7)
- # clojurescript (328)
- # core-async (25)
- # cursive (2)
- # datascript (2)
- # datomic (3)
- # emacs (10)
- # hoplon (1)
- # jobs (2)
- # lein-figwheel (1)
- # leiningen (13)
- # luminus (6)
- # off-topic (38)
- # onyx (2)
- # parinfer (13)
- # pedestal (2)
- # portkey (5)
- # re-frame (11)
- # reagent (2)
- # shadow-cljs (61)
- # specter (6)
- # unrepl (60)
- # vim (4)
@tanzoniteblack I have this in my code
;; Workaround
(eval-after-load 'clojure-mode
'(unless (keymap-parent clojure-mode-map)
(set-keymap-parent clojure-mode-map prog-mode-map)))
don't know if useful
The prog-mode bit wasn't actually my problem
I've had issues in the past with rainbow-identifiers where a mode dynamically updates font faces in a way that clobbers rainbow-identifiers, and that's what I thought was happening here with clojure-mode. But...it just randomly started working again, so who knows
but thanks for the tip
just read prog-mode
there and I thought of throwing it out 😄
@tanzoniteblack There were some font-locking changes in clojure-mode
recently that might have interfered with rainbown-delimiters
mode. We just fixed those. If you’ve been updating frequently from MELPA that might explain your issues.
I think I should stop reading all the Emacs conversation here. Often I feel like a dedicated support or something. 😄
Lol, it's appreciated! I have cider fixed to melpa stable, but I don't think clojure mode is, so that might be it