I updated that list of issues with Powershell and possible solutions, still looking for feedback : https://github.com/cark/clojure-windows-cli-issues
And to go along with it a binary wrapper around the powershell scripts : https://github.com/cark/clojure-win-cli-wrap
And a portable binary rewrite of the bash/powershell scripts : https://github.com/cark/clojure-cli-portable
@carkh haven't tested windows yet for clojure-cli-portable -- tried the linux version. basic repl, -Spath seem to work -- an alias like the following seems to trip clojure (not clj) up:
:sock
{
:jvm-opts ["-Dclojure.server.repl={:port,11119,:accept,clojure.core.server/repl}"]
:main-opts ["-e" "(println,\"socket-repl-at-port:11119\")"]
}
this works with the official clj / clojure.
the error i get for clojure-cli-portable's clojure when invoked as "clojure -A:sock -r" is:
Syntax error compiling at (REPL:1:1).
Unable to resolve symbol: socket-repl-at-port:11119 in this context
nice i'll go and fix it, thanks !
thanks for your ongoing work on this, btw -- as well as pointing out nim -- looks quite interesting 🙂
=)
@sogaiu should be fixed
I have a question though
I see you're using the corfield comma, is it required with the regular clojure cli ?
(in the main-opts of your deps.edn)
i think so, but i will try to verify
so i removed commas from the :jvm-opts as well as :main-opts portions and what i get for clj -A:sock -r is:
Error: Could not find or load main class 11119
yes i guess that's required
that's an issue that ought be fixed in regular clojure cli, for now i'll keep it exactly as it is there
i think it's been discussed, but don't know the status
may be #tools-deps might have some hints?
right now i'm focused on parity rather than fixing upstream issues =)
so err, does it work in the regular case for you now ?
i mean with the "Corfield commas"
hum actually nope still buggy
(on linux)
nope it works
works now, thanks 🙂
no, thank you