-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Windows 10 Pro) read-string fails when reading the environment map returned by calling the clojure executable with -Sdescribe #85
Comments
If I'm not wrong about the above, and not just doing something silly, then I think we should also figure out how to avoid forcing users on windows to create a powershell wrapper to call the clojure command. |
+1, I have same issue (Win 8.1). This is my workaround(no ubuntu wsl) as below:
Actually, I think step #3 is not nessary if we do a tweak like this: Please notice that The above approach can find both I have submitted a PR for process creating issue on Windows. |
I think this may be related, this stacktrace is from a powershell on Windows10
clojure and clj work fine. |
Lein with deps.edn does not work on Windows, so we're moving to clj+deps.edn. See RickMoynihan/lein-tools-deps#85
Lein with deps.edn does not work on Windows, so we're moving to clj+deps.edn. See RickMoynihan/lein-tools-deps#85
Error Input: Just running
lein deps
Error Output:
Unsupported escape character: \W
The clojure tools are delivered as a powershell module on windows.
To use lein-tools-deps I created a batch file to wrap the powershell command named windows.clojure.bat
This produces the following when calling from a command line and passing -Sdescribe
When lein-tools-deps calls the executable and receives raw string output, the following happens:
read-string here receives the following from (shell/sh exe "-Sdescribe")
read-string
breaks on the escaped slashes\\
As a workaround, I installed the clojure tools on my ubuntu WSL and changed my batch script to the following:
This returns the file paths in unix form. This works, but I can't speak to how brittle it may turn out to be yet. It would be great if we can add whatever processing is required here to properly interpret windows file conventions, instead of the barebones read-string.
I hope this is helpful, thank you for your work.
😃
The text was updated successfully, but these errors were encountered: