This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-27
Channels
- # aws-lambda (3)
- # beginners (3)
- # boot (327)
- # capetown (2)
- # cider (156)
- # cljs-dev (368)
- # cljsjs (13)
- # cljsrn (53)
- # clojure (403)
- # clojure-czech (5)
- # clojure-dev (4)
- # clojure-greece (2)
- # clojure-russia (72)
- # clojure-spec (12)
- # clojure-uk (129)
- # clojurescript (156)
- # core-async (1)
- # cursive (33)
- # datomic (35)
- # emacs (10)
- # events (1)
- # hoplon (4)
- # jobs-discuss (3)
- # klipse (1)
- # lein-figwheel (14)
- # leiningen (5)
- # luminus (5)
- # off-topic (15)
- # om (69)
- # om-next (2)
- # onyx (2)
- # parinfer (15)
- # perun (12)
- # re-frame (30)
- # reagent (7)
- # ring-swagger (8)
- # spacemacs (10)
- # specter (6)
- # untangled (69)
- # yada (13)
does anyone use indirect buffers? so when I try to edit code in indirect buffer, it suddenly highlights all parens in the parent buffer. and I don’t know how to clear that
I do occasionally, don't recall having that problem. You might try evil-search-highlight-persist-remove-all
, whatever that's bound to for you (I use :
for it...maybe it's ;
by default?)
I don’t think it’s evil-search-highlight… it lights up ALL parens, like the forms are horridly corrupt. I don’t ever see such thing since I have strict parens enabled, but with indirect buffers it happens. strangely I couldn’t reproduce it in emacs-lisp mode. but in clojurescript and clojure it does shit like that ;(