@mauricio.szabo Has anyone reported that completion (built-in, not Compliment-based) seems to have stopped working in one of the recent Chlorine updates?
Not really, is it not completing? Or any error?
Like, anything being printed on the console?
No errors. Just not offering much in the way of completion. I decided to restart Atom and restart my REPL (which had been running for maybe a week) and it seems to be behaving better now so maybe something had gotten messed up in my REPL.
I'll keep an eye on it, but mostly what was missing was when I typed <somealias>/
I wasn't getting functions from that namespace.
Well, sometimes I'm seeing some issues with some versions of Clojure and some JVMs. I still didn't find the right way to reproduce the error, but there are moments when I can't autocomplete str/repla
- it autocompletes replace
but not replace-first
, and so on...
but it's kinda rare, so I though it was a problem I was facing only when programming the package (because of the "use Chlorine to evaluate itself over Shadow-CLJS using Clojure" sometimes strange things occur...)
'k... then I'll try to pay attention and see whether it fails again in some way... and see if I can repro and let you know.
Mostly it just works seamlessly so I almost forget I'm using it 🙂
Great to know 🙂. I'll check here if I can reproduce. You're using clj
, no compliment, no clojure.tools.namespace, right?
then run same REPL for a week 🙂
Correct, "spartan tooling"
No nREPL, no Orchard, no Compliment, no refresh 🙂
It looks like this REPL had "only" been running since Friday afternoon, but I think I'd seen the problem last week too -- but maybe my REPL was borked and that was why I restarted it last week?
(I run the same "everything" REPL for days and days, and it has the add-lib
branch of t.d.a. so I can dynamically load dependencies from other projects if I'm working on stuff other than my regular "work" stuff...)