-
Notifications
You must be signed in to change notification settings - Fork 38
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
Update description of VSCode extensions #226
Conversation
Looks good to me (and this is was somehow awaited information to take decisions on #218) |
BTW, does this mean that the VsCoq 1 vs VsCoq 2 difference of terminology disappears and that VsCoq 1 is just considered an old non-lsp variant of VsCoq? |
I'll leave to the home pages of the projects to detail these things. |
OK. It that I was afraid that the text "Both extensions are based on LSP" led to confusion if VsCoq 1 is still an option. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a much-needed fix, and since we didn't manage to converge on a description that would say more, I agree that it is reasonable to defer additional explanations to the projects' webpage.
Just a minor suggested change to clarify the situation for users who were already aware of the existence of VsCoq before.
Co-authored-by: Théo Zimmermann <[email protected]>
The info was outdated. This is a minimal fix.