This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-15
Channels
- # announcements (8)
- # beginners (65)
- # calva (25)
- # cider (11)
- # clj-kondo (9)
- # cljsrn (14)
- # clojure (103)
- # clojure-europe (15)
- # clojure-greece (1)
- # clojure-italy (28)
- # clojure-nl (39)
- # clojure-spec (9)
- # clojure-uk (28)
- # clojuredesign-podcast (37)
- # clojurescript (56)
- # cursive (41)
- # data-science (10)
- # datomic (25)
- # duct (1)
- # emacs (1)
- # events (3)
- # figwheel-main (7)
- # fulcro (9)
- # graalvm (7)
- # graphql (10)
- # jobs (2)
- # nrepl (17)
- # off-topic (40)
- # quil (12)
- # reitit (11)
- # remote-jobs (5)
- # rum (2)
- # shadow-cljs (387)
- # sql (22)
- # tools-deps (8)
- # vim (26)
- # xtdb (47)
- # yada (9)
Do Cider (and other editors) implement support for nREPL over HTTP using drawbridge?
If so, how does that work? I’d assumed Cider had an elisp nREPL client, but if it does then I assume it can’t use drawbridge.
> Do Cider (and other editors) implement support for nREPL over HTTP using drawbridge?
> If so, how does that work? I’d assumed Cider had an elisp nREPL client, but if it does then I assume it can’t use drawbridge. Basically you need to send the same requests/process the same responses over HTTP. Drawbridge itself would be transparent to the clients, but the overhead of dealing with HTTP is overkill for most clients I guess. A few users requested support for this in Emacs over the years, but the only real use-case was to debug remote apps, which they can easily do over an ssh tunnel as well.
The main use case that has been requested for Cursive is to have a REPL exposed with better auth control.