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

Saving Documents in SerAPI #128

Closed
brando90 opened this issue Mar 15, 2019 · 1 comment · Fixed by #239
Closed

Saving Documents in SerAPI #128

brando90 opened this issue Mar 15, 2019 · 1 comment · Fixed by #239

Comments

@brando90
Copy link

when the prover is done with a document, I expect we should be able to save the document.

How does one request SerAPI to do that?

@brando90
Copy link
Author

CloseDoc

@ejgallego ejgallego added this to the 0.7.0 milestone Apr 23, 2019
@ejgallego ejgallego modified the milestones: 0.7.0, 0.7.1 Oct 25, 2019
@ejgallego ejgallego modified the milestones: 0.7.1, 0.11.0 Jan 24, 2020
@ejgallego ejgallego modified the milestones: 0.11.0, 0.11.1 May 13, 2020
@ejgallego ejgallego modified the milestones: 0.11.1, 0.12.1 May 27, 2020
@ejgallego ejgallego modified the milestones: 0.12.1, 0.13.1 Mar 12, 2021
ejgallego added a commit that referenced this issue Apr 17, 2021
We introduce a new commmand:
```lisp
(SaveDoc opts)
```
to save .vo files from an interactive session. `opts` are optional,
and can be

- `(sid s)`: save the document at a specific sentence
- `(prefix_output_dir dir)` add a prefix to the `file.vo` to be saved.

Note that Coq requires that the module name and the filename do match,
thus in order to use this command `sertop` must be called with the
`--topfile file.v` flag, otherwise `CannotSaveVo` will be raised.

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

Successfully merging a pull request may close this issue.

2 participants