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

Allow multiple coq buffers to opened at the same time #66

Open
wants to merge 12 commits into
base: pathogen-bundle
Choose a base branch
from

Conversation

bluelightning32
Copy link

  1. Allow multiple instances of coqtop to run for different coq source buffers.
  2. Support python 2 or 3.
  3. Parse default coqtop args from _CoqProject
  4. Allow multiple line ranges for the checked, sent, and error regions. This
    shows when coq processes statements out of order.
  5. Fix parsing comments longer than 995 lines
  6. Fix parsing strings over 995 lines
  7. Add a utility to capture protocol traces from coqide
  8. Use better default colors when the background is dark

@nomeata
Copy link

nomeata commented Sep 22, 2017

Use better default colors when the background is dark

\o/

@sergei-mironov
Copy link

Coquille with this PR seems to work fine. I saw few errors requiring restart, but they don't block the workflow completely and probably may be fixed later. Does anybody plan to merge it? Or maybe is there a coquille fork with it applied?

@bluelightning32
Copy link
Author

I pretty much gave up on getting this merged. You can use my fork, bluelightning32:pathogen-bundle.

@sergei-mironov
Copy link

Thanks! Could you please enable issues for this repository? I don't feel brave enough to fix possible errors but I am ready to report them.

@bluelightning32
Copy link
Author

Done.

I won't have time to work on issues for the next few weeks, but go ahead and file them. I am interested in supporting this project.

@XVilka
Copy link

XVilka commented Aug 22, 2019

Should be rebased on top of the master.

dwarfmaster and others added 12 commits August 22, 2019 00:00
Python no longer fails for most of coq errors. When sending an invalid
argument during a proof, an error is displayed in the info box, but the
cursor moves over the instruction : it may not be intuitive.
Furthermote, moving to a Qed like that creates another python error.
1. Allow multiple instances of coqtop to run for different coq source buffers.
2. Support python 2 or 3.
3. Parse default coqtop args from _CoqProject
4. Allow multiple line ranges for the checked, sent, and error regions. This
   shows when coq processes statements out of order.
5. Fix parsing comments longer than 995 lines
6. Fix parsing strings over 995 lines
7. Add a utility to capture protocol traces from coqide
8. Use better default colors when the background is dark
If the error is serious enough, coqtop reports it happened in state 0. It is
not possible to revert to state 0, because that is before the Init call. So
skip the revert completely if coqtop says state 0.
The CursorMovedI event is triggered when new text is inserted, which is better
than InsertEnter that would resync the buffer on the next insert.

Also fix an off by one error around changing the last character in a statement,
or jumping to the last character in a statement.
1. Allow multi character bullets, like --
2. Do not treat the space directly after the bullet as part of the bullet. This
   is important so that when a new statement is added directly after the
   bullet, the bullet is not rewound.
Use byte offsets for the highlight ranges (sent, checked, error, and warning)
instead of unicode characters offsets.

Also fix python 2 support.
Match the coqide's goal message format. This is important for indicating
whether an unfocused goal needs to be focused or the proof is done.
For the coq to cursor command, send the statements on a background thread while
the main thread redraws the screen. This lets Coq accept multiple commands per
screen redraw. The background thread is terminated after all the statements are
sent.
@bluelightning32
Copy link
Author

I rebased it on top of the pathogen-bundle. Is that what you meant?

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

Successfully merging this pull request may close these issues.

5 participants