This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-11
Channels
- # announcements (18)
- # beginners (57)
- # calva (20)
- # cider (4)
- # cljdoc (15)
- # cljs-dev (14)
- # clojure (124)
- # clojure-europe (5)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-spec (4)
- # clojure-uk (44)
- # clojurescript (4)
- # clojutre (18)
- # clr (2)
- # cursive (25)
- # datomic (53)
- # emacs (18)
- # events (1)
- # figwheel-main (1)
- # fulcro (34)
- # joker (6)
- # kaocha (13)
- # nrepl (3)
- # nyc (24)
- # off-topic (1)
- # pathom (16)
- # protorepl (4)
- # re-frame (1)
- # reitit (27)
- # rewrite-clj (5)
- # shadow-cljs (38)
- # spacemacs (25)
- # sql (20)
- # vim (28)
- # xtdb (20)
I'm using joker on Windows 7. At the joker command prompt I execute "(joker.os/exec "Clojure.Main.exe" {})" which immediately returns "{:success true, :exit 0, :out "Clojure 1.9.0\r\nuser=> \r\n", :err ""}". I expected Clojure.Main.exe to be executed and remain at it's REPL prompt until I exited it. Any thoughts?
Spawning processes and waiting for them to exit, "Unix-style", seems to be a widespread problem on Windows, at least IME. E.g. when I'm in the Git Bash environment and type the emacs
command, it comes back right away as Emacs starts up, just as if I'd done emacs &
in Unix. I'm not sure what the solution is and whether it can be implemented in Joker.