@robert.mather.rmm Blame Windows for that 🙂 You can create clj
and clojure
.bat
files on your path that run powershell clj ...
etc which might solve that problem.
Hey so I've just done this and you have to be slightly careful with it because making a clj.bat
which calls powershell clj
will create an endless loop 😉
So instead what I've done is made clj.bat and clojure.bat which both contain this line:
@powershell Invoke-Clojure %*
Works like a charm 🙂
Good to know. I think I had clj.bat
call powershell clojure %*
just as a test...
@seancorfield I just punted and moved to WSL for now.
PowerShell is a lot more capable than cmd.exe
so getting the full functionality of clj
/`clojure` is much easier on PS than on cmd.
Yeah, I still use WSL for all my pure server-side stuff on Windows.
The PS port of clj
lets me run REBL and some other tooling more easily tho'.
Can you run shadow-cljs
on PowerShell?
oh, that sounds nice. Haven't tried REBL yet.
(and avoid cmd
altogether)
Love REBL. Core part of my daily workflow.
looks like I can
Beware non obvious and hard to research PS escaping rules https://github.com/technomancy/leiningen/issues/2526 but yeah, ps is a vast improvement over cmd
Hopefully the answers in that issue saves someone from the hours of noob pain I suffered with ps. clj
invocation fortunately just works as you'd expect since it doesn't rely on anything that requires an understanding of the differences between sh
and ps
. Not sure if that's by luck or design but it is far less error prone.