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

Coq: Reset command does not use newly installed libraries #1016

Open
cas-haaijman opened this issue Jan 29, 2025 · 4 comments
Open

Coq: Reset command does not use newly installed libraries #1016

cas-haaijman opened this issue Jan 29, 2025 · 4 comments

Comments

@cas-haaijman
Copy link
Contributor

If I remember correctly, it was previously possible to use the Coq: Reset command to reload Coq after you installed new libraries. This no longer seems to work, if a library is added after starting loading a file in VS Code, the only way seems to load the library seems to be to close and re-open VS Code.

@gares
Copy link
Member

gares commented Jan 29, 2025

Reset does not really restart the language server, and Rocq library subsystem scans the file system for libraries only at boot.
I'm afraid this is really hard to fix without changing Rocq.

In the meanwhile, you can use reload window.

@SkySkimmer
Copy link
Contributor

Rocq library subsystem scans the file system for libraries only at boot

Not true, at least in coqtop it works fine to do a failing Require foo, compile foo.vo then try again

@gares
Copy link
Member

gares commented Jan 29, 2025

What I meant is that the loadpath corresponding to user-contribs is populated at boot time.
If the directory in which foo will be is not there at boot, then Rocq does not find it.
Or at least, this is my diagnoses of the problem.

@SkySkimmer
Copy link
Contributor

That seems correct, I guess this could be considered a Coq bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants