System description: Isabelle/jEdit in 2014

Abstract

This is an updated system description for Isabelle/jEdit, according to the official release Isabelle2014 (August 2014). The following new PIDE concepts are explained: asynchronous print functions and document overlays, syntactic and semantic completion, editor navigation, management of auxiliary files within the document-model.Comment: In Proceedings UITP 2014, arXiv:1410.785

Technologies for "Complete, Transparent & Interactive Models of Math" in Education

“…Definitions are reachable by mouse-click (as well as types mentioned above): What is an indispensable feature of a programmers' IDEs and a prerequisite to master the complexity of contemporary software, that is now also available in most advanced IDEs for proof assistants; Fig.1 shows a compilation of screenshots from Isabelle/jEdit [31]: Given a simple calculation as a lemma (as a simple example for more comprehensive theorems) a mouse-click on an element immediately leads to the respective definition; a click on int leads to the definition mentioned above, a click on the + leads to the definition close to relevant algebraic structures like the additive semi-group semigroup_add, a click on the theorem distrib_left to be used by the simplifier leads to the respective formula in the context of a semiring, where the integers in the calculation at hand are an instantiation of (which is formally proved also there). Other semantic information is available as well, for instance distinction of constants, of free and bound variables by colours.…”

Interactive Proof Presentations with Cobra

“…The PIDE framework [20] which was developed together with the Isabelle/jEdit integration has already been successfully integrated into the collaborative web environment Clide in previous work [16]. We were able to reuse significant portions of the code to implement Cobra.…”

“…When a slide includes a code snippet, the viewer will find it augmented with semantic information (Figure 2). The syntax highlighting will reflect the semantic meaning of tokens, just like in Isabelle/jEdit [20] or Clide [16,13]. For Isabelle theories, the proof states can be iterated (just like other fragments) if the class state-fragments is added.…”

Deeply Integrating C11 Code Support into Isabelle/PIDE

“…The Isabelle system is based on a generic document model allowing for efficient, highly-parallelized evaluation and checking of its document content (cf. [2,21,22] for the fairly innovative technologies underlying the Isabelle architecture). These technologies allow for scaling up to fairly large documents: we have seen documents with 150 files be loaded in about 4 min, and individual files -like the x86 model generated from Antony Fox' L3 specs -have 80 kLoC and were loaded in about the same time.…”