#JEDIT HYPERSEARCH HOW TO#

This strange phenomenon can only happen in interactive mode: the corresponding batch job will run forever. Isabelle assumes that the proof will succeed eventually, so it continues on and proves False. What’s going on? The first lemma, whoops, is actually false but the supplied proof fails to terminate. This last point can be puzzling if you watch the progress bar on the right and follow the processing of your theory: how does it reach the bottom when there are red blobs (inducating errors) and purple blobs (indicating a proof still running)? You need to watch out for this sort of thing:

The whole document is processed in parallel, so the last proof can be fully processed while some earlier parts are still running.

By hovering/clicking you can interrogate symbols for their types and definitions.

Each and every symbol you can see has been digested by the Isabelle process,.

Isabelle/jEdit looks like a text editor, but Isabelle is processing your text the entire time.

Let me summarise his main points even more briefly: More useful to a beginner is the brief tutorial by Christian Sternagel. Nothing says daunting like the Isabelle/jEdit This post is mainly for beginners, but experienced users might learn something too.

It was a bare-bones environment, but at least it was Turing complete! Nowadays, things work differently. The first modern proof assistant, Edinburgh LCF, provided nothing but a top-level to the ML programming language, designed specifically to the Meta Language for proving theorems. It’s about being aware of all the bells and whistles provided to help you prove theorems.

#JEDIT HYPERSEARCH HOW TO#

Getting started: basic Isabelle/jEdit tricks Machine Logic At the junction of computation, logic and mathematics Getting started: basic Isabelle/jEdit tricksĪs mentioned last time, proof assistants can be daunting, and it’s not just about how to prove theorems.

Jedit hypersearch