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

Clarify the difference between VsCoq 1 and VsCoq 2 here? #817

Open
patrick-nicodemus opened this issue Sep 2, 2024 · 1 comment · May be fixed by #846
Open

Clarify the difference between VsCoq 1 and VsCoq 2 here? #817

patrick-nicodemus opened this issue Sep 2, 2024 · 1 comment · May be fixed by #846
Labels
kind: bug Something isn't working part: documentation
Milestone

Comments

@patrick-nicodemus
Copy link

## How is `coq-lsp` different from VSCoq?

Moreover, coq-lsp development is active while VSCoq is mostly in
maintenance mode due to the limitations outlined above. In a sense,
you could think of coq-lsp as a full rewrite of VSCoq, using the
experience we have accumulated over years of work in related projects
(such as jsCoq), and the experience in state-of-the art UI design and
implementation in other systems (Rust, Lean, Isabelle).

We didn't pick VSCoq 2 as a project name given than coq-lsp
follows the LSP standard and is not specific to Visual Studio code, in
fact, it works great on other editors such as vim or Emacs.

This paragraph makes me think that the readme is referring to VSCoq 1 rather than VSCoq 2. In this case it would be good to update this readme to clarify the difference between this project and VSCoq 2. I

@ejgallego
Copy link
Owner

Hi @patrick-nicodemus , this is indeed outdated, as the README was written before VsCoq 2 was released. Thanks for notification, we will amend ASAP.

@ejgallego ejgallego added this to the 0.2.1 milestone Sep 5, 2024
@ejgallego ejgallego added kind: bug Something isn't working part: documentation labels Oct 4, 2024
ejgallego added a commit that referenced this issue Oct 4, 2024
ejgallego added a commit that referenced this issue Oct 4, 2024
@ejgallego ejgallego linked a pull request Oct 4, 2024 that will close this issue
@ejgallego ejgallego modified the milestones: 0.2.1, 0.2.2 Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working part: documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants