GitLab

Setting whether counter-example should be get in why3ide is done by in GUI - instead of setting this using command-line option.

+ fixed wrong step limit in one session

and merge the why3 and why3session libraries back into one.

- make Whyconf.Args.initialize return the base config file, too.
  This is needed when we change configuration and want to save it.
- make Main pass "why3 <command>" as argv[0]
- remove "-version" options from everything but the main executable

two parts: why3 and why3session.

(The Coq tactic does not include why3session)

+ create AUTHORS file
+ fix the linking exception in LICENSE
+ update the "About" in IDE
+ remove the trailing whitespace
+ inflate my scores at Ohloh

  - the symbols that appear in the metas are identified in the xml by
    their position in the task:
    - in which declaration
    - in which definition (if that apply otherwise -1)
    - in which constructor(or case in inductive predicate) (if that apply otherwise -1)
    - in which field (if that apply otherwise -1)

  - the md5sum of the prefix of the task that end with the declaration is used to know if the
    symbol have been changed, and if it is obsolete.

  - currently metas that contains obsolete symbol are removed.

There is still a need to have some proof replacement process

Prover ids are only used for the command line option "-P".
The user can choose what he wants (they must be unique)
The prover name and version should not be modified. If someone want to
test different command line options for a prover he can use the
"alternative" field.

If someone want to replay an external proof but he doesn't have the
corresponding prover (same name,version,alternative), why3ide ask for
a replacement among the known provers. The choice can be saved.

The loaded files are slimmed down version of the standard configuration
file. They only support the following sections and fields:

[main]
  loadpath=
  plugin=
[prover ...]
  option=
  driver=

It is also possible to define brand new [prover] sections.

For now, the only supported frontends are why3 and why3ide.

rename location_color to goal_color and lighter_location_color
to premise_color