This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-24
Channels
- # aws (2)
- # babashka (27)
- # beginners (97)
- # calva (1)
- # cherry (12)
- # cider (6)
- # clara (12)
- # clj-kondo (24)
- # clj-on-windows (4)
- # cljfx (14)
- # clojure (54)
- # clojure-australia (3)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojure-uk (9)
- # clojurescript (65)
- # conjure (5)
- # cursive (7)
- # datomic (18)
- # emacs (6)
- # helix (2)
- # honeysql (1)
- # jobs (1)
- # joyride (15)
- # kaocha (2)
- # lsp (10)
- # malli (5)
- # nbb (12)
- # observability (5)
- # off-topic (5)
- # reitit (2)
- # releases (4)
- # ring (1)
- # sci (17)
- # shadow-cljs (34)
- # testing (29)
- # tools-deps (45)
- # vim (7)
- # xtdb (6)
Does joyride (or calva not sure which) facilitate repl-initiated communication? Eg. the runtime decides to send a message to calva/joyride, and somewhere in calva/joyride we can write handler code?
This would be a question for @U0ETXRFEW
We don't have that. What's the use case? I wonder if it is Joyride or Calva that would be supporting this.
I don't think this can be used as a workaround, but I haven't tried. In Calva's https://calva.io/api/#replevaluatecode there are two callbacks, for handling stdout
and stderr
, respectively. Maybe (probably not) you can start a thread in the runtime (assuming it is Clojure) which prints to stdout
and then use the callback. The reason I don't think this works is that I don't think we channel stdout
back to the callback, once that evaluation has returned. I might be remembering this wrong, though.
Another personal usecase, basically having a UI where I can click things and it sends itself back, I guess portal sends things back to the repl using its own system not all the way back to calva
Sends itself back to vscode* I'm trying to deeply integrate my UI development with my IDE
I guess maybe I could open some sort of two way communications protocol in joyride, connect that to the runtime myself, then on ping from the runtime, run a command or calva API? That sounds like the most direct way to implement it without direct calva cooperation?
This might be something that's much more convenient using joyride and useful for other people
@U0ETXRFEW could I do the reverse and instead of using customcommands in calva somehow fire the communication from vscode->calva ->joyride->runtime instead of worrying about the customcommand interface?
Instead of having messages go 1. vscode-->>calva--customcommand>>repl-->>runtime and in reverse 2. runtime-->>joyride-->>vscode have the first flow be vscode-->>calva--?>>joyride-->>runtime