This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (3)
- # beginners (35)
- # boot (87)
- # cider (84)
- # cljs-dev (6)
- # clojure (70)
- # clojure-austin (3)
- # clojure-italy (11)
- # clojure-japan (6)
- # clojure-korea (16)
- # clojure-russia (87)
- # clojurebridge (1)
- # clojurescript (122)
- # core-async (112)
- # cursive (2)
- # datomic (46)
- # editors (6)
- # jobs (2)
- # ldnclj (8)
- # re-frame (1)
- # reagent (1)
anyone using latest CIDER started seeing messages like this?
error in process filter: some namespaces are in a bad state: (and then a list of nses and vars)
but when i go to recompile those nses, theres’ no actual problem
@robert-stuttaford: that’s coming from the clojure analyser
are you using clj-refactor?
I had a similar thing with clj-refactor. 1.0.5
robert-stuttaford: Yes, that's not cider. I get that from clj-refactor sometimes, but it could be from other things like a linter/analyser
BTW my problem with clj-refactor was to do with custom reader tags I.E., a
data_readers.clj file in the classpath that clj-refactor’s call to the analyser was not taking into account. That was fixed in
1.1.0 I believe.
aha. thank you guys. i’m on the latest clj-refactor, i believe
@robert-stuttaford: Not the same issue I had, but it’s possible that refactor-nrepl’s call to the analyser fails here >> https://github.com/clojure-emacs/refactor-nrepl/blob/master/src/refactor_nrepl/analyzer.clj#L61
it appears that this error can safely be ignored?
Difficult to debug without the full stacktrace
of course, it does stop clj-refactor from working. i’ve already fixed that by restarting the jvm once or twice
Yes, it can be ignored… but you mightn’t get the refactor-nrepl functionality
oh - are you a clj-refactor maintainer, andrewmcveigh ?
no I’m not
@benedek: you around
ah you’re talking a little like one 😁
@andrewmcveigh: deffo has some code in it 😉
most likely coming from refactor-nrepl and it signals that we can’t analyze some of your namespaces
ok. i had one where it said it couldn’t resolve the var ‘let'
which tells me something odd is going on
that it practically stops those clj-refactor features which are refactor-nrepl based like find usages, rename symbol, extract fn etc
yeah – all the cool ones
ok. now that i know where it’s coming from, the next time i have it, i’ll try to file an Issue on the GH project
-ing huge thank you to you and your co-conspirators for making and improving it
i ❤️ the threading keybinds a little too much
great, i’ll try report issues first though
btw magnars currently hacking on create function stub based on example
fe so it understands higher order fns. vanilla emacslisp too so you don’t need the middleware
man the clj-refactor wiki page is dangerous. i end up spending more time than i should noodling around with cool toys
trying to integrate just one or two at a time
@benedek: can’t be that hard to port the reader/analyser to elisp, right? 😉
np, was starting to get out of my depth.
@andrewmcveigh: nah man we just need to get CIDER infrastructure to use TANAL output >:D
@arrdem: well, it was mainly a joke… 😁 but deadly serious 👿
@andrewmcveigh: so one thing we joked about a while back was using TANAL to do real syntax highlighting. TANAL knows what textual symbols are locals globals and soforth, as well as which are which so you could write a syntax highlighter that eats a dumped locals table from TANAL and then does fairly advanced colorization beyond what we have now.
Was discussing the basics of that kinda thing today… my answer was that I wouldn’t care enough to write it.
The potential slowdown wouldn’t be worth the little gain to me.
so many things in JS are so absurd, that I simply cannot write more than 100 lines of code without going into a nervous breakdown
I assume the answer is no, but: is there any way to get
cider-find-var to take me to the
.cljx file instead of the generated
I agree, but I’m writing a patch for a library whose maintainers have stated they won’t move to cljc until 1.7 has been out for “at least a year” 😞