This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-04
Channels
- # architecture (27)
- # bangalore-clj (4)
- # beginners (22)
- # boot (35)
- # cider (26)
- # cljs-dev (2)
- # cljsrn (3)
- # clojure (156)
- # clojure-austria (3)
- # clojure-dev (9)
- # clojure-italy (25)
- # clojure-nl (10)
- # clojure-poland (5)
- # clojure-sanfrancisco (1)
- # clojure-spec (6)
- # clojure-uk (64)
- # clojurescript (169)
- # core-async (13)
- # cursive (13)
- # datomic (63)
- # dirac (50)
- # duct (21)
- # editors (1)
- # emacs (6)
- # events (1)
- # fulcro (1)
- # java (22)
- # keechma (14)
- # leiningen (2)
- # luminus (4)
- # off-topic (23)
- # onyx (4)
- # parinfer (5)
- # pedestal (4)
- # re-frame (6)
- # reagent (4)
- # ring-swagger (7)
- # rum (4)
- # shadow-cljs (84)
- # specter (5)
- # sql (36)
- # tools-deps (76)
- # uncomplicate (3)
- # yada (4)
@gastove I’m certain that the latest master
should work properly. The bug was in orchard
, btw. Maybe the auto-deployment failed or something like this.
@bhauman just responded on your ticket but (setq cider-font-lock-dynamically nil)
and see if that speeds up your buffer
@bozhidar okay, got it, thanks 🙂 I'll either install latest master or watch for the next cider
release 👍
@gastove I just checked on clojars and I see the version of orchard
there is the right one. I wonder if some reason your snapshot deps are out of date.
Ah, now I understand what happened. As orchard
is not a normal dependency for cider-nrepl
, but an inlined one, I also need to cut a new snapshot release of cider-nrepl
manually.
> @bhauman just responded on your ticket but (setq cider-font-lock-dynamically nil)
and see if that speeds up your buffer
@dpsutton is probably right, there’s also some font-locking for reader conditionals that can also cause such problems. I wonder why the problem becomes worse with time, though. My guess is that we’re not invalidating some ns data (which we use for font-locking) and it grows huge.
i was in a 1800 line file and it was terrible. i turned it off and it was night and day. i think this is a buffer size issue not cljc issue
Hmm, I wonder why, though. The generated font-locking rules should be just as effective as the static ones, and most people haven’t complained about this.
Anyways, I’m certain that part of the code can be optimized. It almost hasn’t changed since @malabarba “retired”.
for sure. i'd be interested in tracking down what's going on. also figuring out imortant locals are. for instance, if you shadow a name with a let binding, does cider-find-var
understand that new context
Currently CIDER has not idea about locals outside the debugger, but many people have asked for this to be improved.