emacs-lisp code for running SAW in emacs #1331
Merged
Conversation
This file contains 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
robdockins
approved these changes
Jul 14, 2021
nano-o
added
the
PR: ready to merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Now that SAW does not exit after trivial errors, running it in a subprocess and sending inputs from a Sawscript file works quite well and is a nice way to develop proofs. This file complements
saw-mode.elto provide functions to make this way of working easy. I've been using it for a few months and it seems pretty stable.One issue I have not solved is in making emacs correctly recognize SAW forms, using syntax tables. It works pretty well but is thrown off by anything like "(x:[8])", where a parenthesis immediately follows a backslash. Adding a space after the backslash eliminates the problem, so it is not a killer. This is a problem I inherited from
saw-mode.el.Note: the term "inferior" is the standard emacs term for referring to a subprocess, as in "inferior-lisp-mode" or "inferior-haskell-mode", so I am not badmouthing saw in the name of this mode!