leanprover / leanprover/vscode-lean4

Extension doesn't play nice with msys2

Open
#346 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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
  1. go to directory with lean project
  2. run mingw this changes the path, but it should be additive, not substractive
  3. run code .

or

  1. open unrelated project in vscode in mingw.
  2. open vscode normally
  3. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.