Fork me on GitHub
#clj-on-windows
<
2022-04-12
>
thheller06:04:10

@spapas did you check the linked document? https:/go.microsoft.com/fwlink/?LinkID=135170

thheller06:04:39

I get

Get-ExecutionPolicy -List

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser    RemoteSigned
 LocalMachine    Unrestricted

thheller06:04:44

maybe yours if set different?

Serafeim Papastefanos06:04:04

@thheller i was actually able to install it using this project https://github.com/borkdude/deps.clj

Serafeim Papastefanos06:04:26

however i understand that clj does not create new projectt so i ended up using lein anyway

seancorfield14:04:15

@spapas There's https://github.com/seancorfield/clj-new for the CLI/`deps.edn` which is based on lein new, and https://github.com/seancorfield/deps-new which is the simpler, newer version based solely on clojure.tools.build -- feel free to ask Qs in #deps-new about either of those.

seancorfield14:04:47

Note that since you're on Windows, you'll run into the weird quoting issues described in https://clojure.org/reference/deps_and_cli#quoting

seancorfield14:04:37

(my recommendation for Windows users is to use WSL2, if possible, so you can just follow all the normal macOS/Linux instructions for all Clojure tools -- only about 5% of Clojure developers use Windows with Powershell)

Serafeim Papastefanos14:04:12

I'm one of the few that use cmd.exe :(

seancorfield14:04:00

You'll find life difficult with Clojure -- all the books and tutorials assume macOS/Linux and a lot of tooling and libraries won't work on cmd/PS (or won't work directly "as documented").

seancorfield14:04:28

Seriously consider adding WSL2 and using bash instead -- it will make your Clojure journey a lot easier. VS Code understands WSL2 so you can use it natively on Windows, even with all your files on WSL2. That's my setup.

Serafeim Papastefanos15:04:11

Thanks I'll keep it in my mind next time I hit a wall!