This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # aws (11)
- # babashka (10)
- # beginners (49)
- # calva (32)
- # cljsrn (3)
- # clojure (123)
- # clojure-australia (1)
- # clojure-dev (2)
- # clojure-europe (27)
- # clojure-spec (1)
- # clojurescript (22)
- # clojutre (1)
- # code-reviews (1)
- # conjure (3)
- # editors (32)
- # emacs (3)
- # graalvm (12)
- # kaocha (1)
- # lsp (1)
- # malli (2)
- # off-topic (1)
- # schema (2)
- # shadow-cljs (32)
- # spacemacs (6)
- # tools-deps (4)
I've been working on Tutkain, a Sublime Text package for interactive Clojure development, for the past year and a half. Now that Sublime Text 4 (https://www.sublimetext.com) is out, if you're interested, you can try it out without having to buy a license. Tutkain's website (replete with incomplete documentation) is here: https://tutkain.flowthing.me/ You can use Tutkain to connect to a Clojure, shadow-cljs, or Babashka socket REPL and evaluate code from the editor. Tutkain has support for auto-completion and looking up function and spec-naming keyword information. It also sports a vaguely Cursive-like clojure.test integration. Tutkain is more like Clover, Chlorine, or inf-clojure than Calva or CIDER. It has zero dependencies on both the client (the Sublime Text package) and the server (the Clojure, ClojureScript or Babashka runtime). It uses different channels for evaluations and editor tooling, which means it won't get in your way if you want to do things like start nested REPLs. In general, Tutkain is heavily REPL-oriented. My hope is that you can use it to come up with ways to use the REPL to maximum effect, instead of having to implement bespoke capabilities into Tutkain itself for every imaginable use case. Note that Tutkain is still in alpha, so breaking changes are possible. If you end up trying it out, I'd really appreciate it if you could let me know how it goes. Tutkain (unsurprisingly) hasn't had a lot of users so far, so I could really use another set of eyes on it to iron out the bugs.
Thanks, Colin! And thanks also for Cursive, which I used for many years before embarking on this fool's errand. 🙂
I think everyone (including me) underestimates the amount of work in making an editor 🙂
I have no doubt. I sometimes feel I could almost do that with Tutkain, and it has a fraction of the features. 😛
The clojure.test integration is this really dumb thing at the moment: https://github.com/eerohele/Tutkain/blob/master/clojure/src/tutkain/test.clj
The diffing itself uses ST's built-in diff thing, so it's not very good when the results get medium-to-large.
I see, you’re using pprint. The issue I always have is how to format the data structures so the diff makes sense.
Yes, could probably try to come up with something more clever for that. I'm not sure I want to put in a lot of effort to the clojure.test integration, though. I guess I'm considering going for a more REPL-oriented approach (Stu's transcriptor lib and that kind of thing).
Yeah, fair enough. I still think you’ll want diffs when things don’t match what you expected, though.
Yeah, definitely. I'm thinking folks can then either use clojure.data/diff or something like deep-diff2 if they want to, though.
Which is to say: I'm copping out because I don't think I'm smart enough to come up with a really good diffing solution myself. 😛
Hehe, well, for what it's worth, I always thought the test result diffing was one of the best parts of Cursive. 🙂
Great work, @U4ZDX466T! Indeed, by being REPL-oriented it really seems closer to Chlorine and Clover. Great to see more push on trying to use REPL to the maximum effect too 🙂
BTW, @U0567Q30W, I've been using
nubank/matcher-combinators for tests, and it's really sweet for the thing you described (if I undestood correctly 😄)
It's sad that sublime does not support js for plug-ins, otherwise we could reuse the same base library for this plug-in also :)