This repository has been archived by the owner on Oct 14, 2023. It is now read-only.
leanpkg doesn't work on Windows when lean is copied to C:\Program Files\lean\ #1973
Comments
This is just the canonical problem that Windows has with file names with spaces in, right? |
It is not canonical problem. Other tools have no such a problems. It’s Windows specific. I think that somewhere inside, an executable is called and the path to it is not quoted. In Windows shells you need to put quotes around paths that could have spaces in them. Otherwise spaces will separate path to different command line arguments, which usually is not intended. |
The problem is the lack of quoting in leanpkg.bat. I'm going to open a PR soon with a fix. |
solson
added a commit
to solson/lean
that referenced
this issue
Oct 7, 2018
Fixes leanprover#1973. I've tested it locally and this appears to be enough to solve the problem.
solson
added a commit
to solson/lean
that referenced
this issue
Oct 7, 2018
Fixes leanprover#1973. I've tested it locally and this appears to be enough to solve the problem.
Kha
pushed a commit
that referenced
this issue
Oct 27, 2018
Fixes #1973. I've tested it locally and this appears to be enough to solve the problem.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
Description
leanpkg doesn't work on Windows when lean is copied to C:\Program Files\lean\
Steps to Reproduce
Expected behavior: [What you expect to happen]
leanpkg to run correctly on Windows under normal installation place for that OS
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of
lean --version
,please include the OS and what version of the OS you're running.
Lean (version 3.4.1, commit 17fe3decaf8a, Release)
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
The text was updated successfully, but these errors were encountered: