Skip to content
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

problem using vscoq on windows 10 via wsl #709

Open
ellisonch opened this issue Jan 19, 2024 · 1 comment
Open

problem using vscoq on windows 10 via wsl #709

ellisonch opened this issue Jan 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ellisonch
Copy link

I have a normal installation of VS Code on windows 10. I'd like to use the VsCoq extension.

I have set up coq as per the installation instructions on wsl, and everything worked fine.

$ which vscoqtop
/home/ellisonch/.opam/default/bin/vscoqtop

I can't use /home/ellisonch/.opam/default/bin/vscoqtop directly as the vscoq.path setting, as this isn't the "real" path to the executable:
image

So, I thought I would be able to use wsl -- /home/ellisonch/.opam/default/bin/vscoqtop as my vscoq.path, since that command works totally fine outside of vscode. Here's me running that command in a normal windows 10 cmd.exe command prompt:

>wsl -- /home/ellisonch/.opam/default/bin/vscoqtop --version
The Coq Proof Assistant, version 8.18.0
compiled with OCaml 4.13.1

However, trying to use wsl -- /home/ellisonch/.opam/default/bin/vscoqtop as my vscoq.path also fails:
image

When I click "Go to output", that popup goes away and it shows me this error message:

[Error - 11:27:25 PM] Starting client failed
Launching server using command wsl -- /home/ellisonch/.opam/default/bin/vscoqtop failed.

There aren't any other messages.

Is it possible to do what I want, or is vscoq just unsupported on windows vscode? I'd really like to avoid having a separation installation of vscode inside of wsl just for vscoq. Incidentally, I tried running my windows vscode from inside wsl, and it still fails in the above ways.

@ellisonch
Copy link
Author

FWIW, setting vscoq.path to wsl /home/ellisonch/.opam/default/bin/vscoqtop also fails in the same way as above, despite working on the normal windows command line.

@rtetley rtetley added the bug Something isn't working label Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

2 participants