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

Server does not respond to new file #484

Closed
b-mehta opened this issue Jun 23, 2024 · 1 comment · Fixed by #491
Closed

Server does not respond to new file #484

b-mehta opened this issue Jun 23, 2024 · 1 comment · Fixed by #491
Labels
bug Something isn't working

Comments

@b-mehta
Copy link
Contributor

b-mehta commented Jun 23, 2024

Description

The lean4 server does not display any information or errors on a new file.

Context

Discussion: https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/Server.20crashes.20on.20new.20file

Steps to Reproduce

  1. Have a running Lean server, working on a Lean file
  2. Open a new file in VSCode in the same directory
  3. Save it as test.lean
  4. Write example : 1 = 2 := rfl in the file
  5. Save the file
  6. No errors are generated.

Expected behavior:
The invalid theorem gives an error.

Actual behavior:
The invalid theorem does not give an error.

Versions

vscode-lean4 version: 0.0.168
Lean version: 4.9.0-rc2
OS version: MacOS Monterey

Additional Information

[Additional information, configuration or data that might be necessary to reproduce the issue]

Impact

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

@b-mehta
Copy link
Contributor Author

b-mehta commented Jun 26, 2024

Recording the workaround from the zulip thread for anyone coming across this:

You can close test.lean and then re-open it. Then, when the language client attempts to open the document, VS Code will already have updated window.tabGroups.

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
None yet
Development

Successfully merging a pull request may close this issue.

1 participant