This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-15
Channels
- # aleph (5)
- # announcements (1)
- # architecture (35)
- # babashka (9)
- # beginners (87)
- # chlorine-clover (13)
- # cider (3)
- # cljdoc (12)
- # clojure (16)
- # clojure-australia (2)
- # clojure-dev (4)
- # clojure-europe (5)
- # clojuredesign-podcast (21)
- # clojurescript (19)
- # conjure (1)
- # core-async (1)
- # data-science (1)
- # emacs (44)
- # events (2)
- # helix (1)
- # leiningen (2)
- # malli (31)
- # pathom (3)
- # pedestal (31)
- # portal (3)
- # reagent (20)
- # reitit (5)
- # reveal (2)
- # rewrite-clj (18)
- # tools-deps (6)
- # xtdb (5)
@seancorfield You said you use your Atom / VSCode with WSL. How do you configure to work? Is your Editor in Windows or in Linux XWindow?
VS Code has a Remote-WSL2 extension. I just followed the VS Code docs for that.
With Atom, I ended up installing the Linux version on WSL2, and using VcXsrv (Xlaunch) on Windows to render X11 UIs.
When I run Reveal, I run that on WSL2 -- because that's where I start my REPL -- and its UI is rendered on Windows via VcXsrv.
Originally, I ran Atom on Windows and the REPL on WSL2, relying on the smart mapping in Chlorine to detect the cross-platform file paths.
Yes, I run Docker on Windows via the backend WSL2 integration. I use it to run Percona (MySQL), Redis, and ElasticSearch.
hum, that´s because I´m asking you about it. I wonder to use something like that. But don´t you have problems interconnect containers?
It all works perfectly as far as I can tell.
My entire dev env is on WSL2, just as it was on macOS before. Everything works exactly the same way.