This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # bangalore-clj (3)
- # beginners (73)
- # boot (1)
- # calva (88)
- # cljdoc (13)
- # cljsrn (1)
- # clojure (65)
- # clojure-finland (1)
- # clojure-spec (14)
- # clojure-uk (1)
- # clojurescript (50)
- # core-async (4)
- # datavis (6)
- # duct (2)
- # figwheel-main (1)
- # off-topic (15)
- # pedestal (16)
- # planck (11)
- # re-frame (3)
- # shadow-cljs (19)
- # yada (3)
I have been chasing the craziest thing. I have a file that is a namespace called ace2.legacy.timetrak.timetrak
it goes bonkers when I try to eval the file, calva (snapshot) won't switch namespace to it, (goes to user=>), and evaling functions in it just breeds nonsense. if I move the code to a different namespace (e.g. ace2.legacy.timetrak.ttio), things seem to go sane again.
all of this is code that clojure compiles perfectly, and other similar files in the project seem to work fine. It's weird.
aside from that, the preview version has been a champ on my desktop for about a week now. I don't appreciate that Im not getting hostile messages when a file can't be eval'ed, but other than that, and this, it's going well.
yup, moving all the code to a new filename and new namespace changes it all. very weird
About that craziest thing. Calva has some really naive code for parsing out the ns of the file. It sounds like that is the problem.
I'm on 1.3.65-SNAPSHOT. I pulled the repo (branch pez/repl_jack-in) earlier today and didn't see anything moving since 3/19
Strange. Run it in the debugger and see if you can catch what goes wrong. I might have borked it earlier today.
I'm not sure I understand how to kick up the debugger on calva extension while I'm looking at my directory.
It’s straightforward. Open the root of the project in vscode. Run the build task (`cmd+shift+b`) Watch CLJS and wait for shadow-cljs to build its things and run tests. Then run the build task Watch TS and wait (much shorter) for it to build its things. Then press F5.
ok, so I think I got through that. I'm bascially left with a VSC window debugging the typescript, and I open my mess in the Extension Development host
Dear channel, here’s a new preview build of Calva 2. It has the beginnings of a working jack-in. There are really rough edges to it and it doesn’t allow you to customize the commands used to start the REPL so will not work in all projects. I have tested it (very briefly) on shadow-cljs and leiningen+figwheel projects. It might work for cli/deps as well, but that is untested.
If you pull in my branch from upstream, @hoppy, you should be able to build it using the latest jack-in changes. What’s new is that we now use the
cljs.reader for parsing edn files, which is premium edn parsing, and a lot better than that
jsedn stuff we used before.
somebody must have changed the font in the repl window, my eyes aren't bleeding anymore
I notice when I unzip my package and yours and diff them, it appears that your npm is getting some newer stuff out of the ether than mine.
and I'd be interested in understanding why it works when I'm debugging it, but not when I install a .vsix I made on the same system. Stumped.
We build the style sheets with node-sass. And that is since very recent. Might be something around that.
@hoppy, can you post the first lines of that
ace2.legacy.timetrak.timetrak file? Or, if it’s open source, just post a link. 😃
go to definition doesn't seem to work (I believe it does work in cider). I get this error message. do you know what information is missing @pez? https://memset.se/8333/9ac59bb9e9a22ab6842576eeb564cabfd29ae585
tried it in cider, it almost works, and if nothing else it gets all information needed : >
something I didn't consider is that since vs code is top 2 best editors for c# in unity; if you manage to get calva + arcadia working properly it would probably be a really good development experience
When I eval inline and get an exception, is there a way to view more of the output? It's currently truncating the useful info. I can eval in the terminal repl and get the whole thing, just wondering if there was a way to do it inline.
@dave.dixon , that's really annoying, and we'll fix it. I'd say it is high priority, but can't give an ETA. As we are preparing for releasing a much improved REPL window, that displays more helpful stack traces, maybe it would be a good idea to use that one for when inline evals render exceptions...
note that some knucklehead (probably me) ended up with clj-time.core in there twice, which I initially thought was contributing. But it wasn't
Yeah, so that is definitely stupid Calva code for figuring out the ns that makes that fail. We must fix that, @mseddon
Might be worth looking at the fireplace regex, I've found it to be surprisingly reliable.
Interesting. I don't recall touching that, but the regex does look more solid now than it used to. Well, please stay on the lookout for similar problems.