leanprover / leanprover/vscode-lean4
Extension doesn't play nice with msys2
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 313
- Forks
- 104
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 1
Description
Description
I need to program stuff with mingw, so I open vscode on mingw, once 1 window has been opened in mingw, all other windows will inherit this context, so it doesn't matter if they are open on
Context
I have lots of vscodium sessions open, and I would like to have lean open simmulataneously with the others
Steps to Reproduce
- go to directory with lean project
- run
mingwthis changes the path, but it should be additive, not substractive - run
code .
or
- open unrelated project in vscode in mingw.
- open
vscodenormally - open lean project
Expected behavior: [Clear and concise description of what you expect to happen]
LSP starts and works
Actual behavior: [Clear and concise description of what actually happens]
LSP fails and crashes
Versions
[Version of vscode-lean4 (Hover over 'lean4' in the 'Extensions' menu)]
0.0.117
[Output of lean --version in the folder that the issue occured in]
Lean (version 4.2.0-rc4, commit 819b5eaceaa4, Release)
[OS version]
windows 10
Additional Information
I would love to know how to debug LSPs so I can figure out the exact bug, but it's been annoying me for a while. I've never developed a vscode extension
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Reproduce the failure using the listed MSYS2 and VS Code steps, then inspect the extension's LSP startup and environment handling. Done means the Lean LSP starts successfully for a Lean project while other VS Code sessions remain open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100