added _RocqProject for VSCode#255
Open
peterlefanulumsdaine wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I’m revisiting this repo for the first couple of years, during which I migrated to VS Code from Emacs + Proof General. VS Code handles the path/environment slightly differently from how Emacs+PG did, and in particular, all internal imports were failing for me in VSCode with "Cannot find a physical path bound to logical path TypeTheory…"
The minimal fix I can see is adding a basic
_RocqProjectfile as in this PR; as far as I can see, that updates the path in VS Code and doesn’t interfere with the main build setup. But I’m not fully on top of how the build infrastructure works, so I’m leaving these PR notes here in case anyone who knows it better thinks this wasn’t the right choice.