1. 29 Sep, 2011 4 commits
  2. 24 Sep, 2011 1 commit
    • Guillaume Melquiond's avatar
      Keep track of "ITP" provers and avoid running such provers on unedited proofs. · 406f058e
      Guillaume Melquiond authored
      When the user wants to write a Coq proof, she needs to run Coq on the goal,
      wait five seconds for it to fail (it will fail, otherwise there is no point
      in running Coq on this goal: another prover would have succeeded already),
      and finally edit it. This is a waste of time. So goals run with an
      interactive prover are now marked as unknown until their file is edited.
      
      Interactive provers could have been detected by a nonempty "editor" string,
      but there are interactive provers that don't have dedicated editors, and
      there might be automated provers with dedicated user interfaces. So a new
      field was added to prover descriptions.
      
      TODO: actually run the editor when there is only one selected goal,
      rather than keeping the current three-click method of editing proofs.
      406f058e
  3. 18 Sep, 2011 1 commit
  4. 17 Sep, 2011 1 commit
  5. 05 Jul, 2011 1 commit
  6. 02 Jul, 2011 4 commits
  7. 01 Jul, 2011 1 commit
  8. 29 Jun, 2011 1 commit
  9. 11 Jun, 2011 1 commit
    • Andrei Paskevich's avatar
      a little refactoring in Env · b8dcebfc
      Andrei Paskevich authored
      - create_env_of_loadpath is now provided in Env instead of Lexer
      - find_channel functions now depend on format to determine the
        suitable extensions
      b8dcebfc
  10. 24 May, 2011 1 commit
  11. 22 May, 2011 2 commits
  12. 22 Apr, 2011 1 commit
    • François Bobot's avatar
      autodetection : simplify the semantics of the file provers-detection-data.conf · ef43f13a
      François Bobot authored
      * all the provers with the same prover_id are threated as one prover,
      * the first description of a prover in the file pdd.conf which have an
        executable with a good version is used,
      * the order used to test the executable (exec) inside a prover description
        is not specified,
      * a version_bad allows to forbid a version.
      * a version_ok matches no warning is printed
      * a version_old matches a warning is printed
      * if no version matches a warning is printed
      ef43f13a
  13. 21 Apr, 2011 3 commits
  14. 31 Mar, 2011 1 commit
  15. 15 Mar, 2011 1 commit
  16. 04 Mar, 2011 1 commit
  17. 20 Feb, 2011 5 commits
  18. 19 Feb, 2011 1 commit
  19. 16 Feb, 2011 3 commits
  20. 15 Feb, 2011 4 commits
  21. 25 Jan, 2011 1 commit
  22. 29 Dec, 2010 1 commit