| Age | Commit message (Collapse) | Author |
|
- Update Docker images to install compatible version of lablgtk3
- We remove unnecesary variables from configure.
- We fix path detection of GTK libs in makefile
|
|
|
|
|
|
|
|
|
|
The effect of modify_base is told to be widget-dependent. It uses to
change the background with gtk2 but not with gtk3. So we use the more
explicit modify_bg.
|
|
This was automatic in gtk2 (apparently because of the specification
not being granted). This is needed with gtk3.
|
|
This was not needed in gtk2 but is needed with gtk3.
|
|
This is not mandatory for gtk+3 since it is deprecated from only gtk
3.4. This would be needed for gtk+4 though.
|
|
|
|
|
|
According to
https://developer.gnome.org/gtk2/stable/GtkToolbar.html#gtk-toolbar-set-tooltips,
tooltips are now managed globally by gtk-enable-tooltips which is true by default.
|
|
Was formerly displaying a stippled ("pointillé") light blue. Now only
a light blue.
|
|
|
|
Thanks to J. Garrigue for the hint.
|
|
Indeed, gtk3 has no more Pixmap, it should use Cairo instead.
We also deactivate the functions in the graph of dependency. In
particular, this also blocks coqOps.ml.
|
|
|
|
They rely on list and strings from configwin which themselves rely on
gtk2 only widgets.
|
|
They rely on gtk2 clist and would need to be changed to list_store.
|
|
This seems fragile: does it depend on the order files are loaded? (It
was working for gtk2 when gtk initialization was in coqide_main.ml but
it does not work anymore for CoqIDE built on gtk3).
Eventually, it might be needed to centralize all initialization side
effects in one place.
|
|
|
|
|
|
|
|
This library is unstable and not meant to be consumed by anyone. We
thus make it private.
|
|
Ack-by: JasonGross
Reviewed-by: ejgallego
Ack-by: gares
Reviewed-by: ppedrot
|
|
|
|
|
|
|
|
Before #9263 this type was returned by the STM's `parse_sentence`, but
the type was lost on the generalization to entries.
|
|
We make `coqc` a truly standalone binary, whereas `coqtop` is
restricted to interactive use.
Thus, `coqtop -compile` will emit a warning and call `coqc`.
We have also refactored `Coqargs` into a common `Coqargs` module and a
compilation-specific module `Coqcargs`.
This solves problems related to `coqc` having its own argument
parsing, and reduces the number of strange argument combinations a
lot.
|
|
|
|
|
|
DAG nodes hold now a system state and a parsing state.
The latter is always passed to the parser.
This paves the way to decoupling the effect of commands on the parsing
state and the system state, and hence never force to interpret, say,
Notation.
Handling proof modes is now done explicitly in the STM, not by interpreting
VernacStartLemma.
Similarly Notation execution could be split in two phases in order to obtain a
parsing state without fully executing it (that requires executing all
commands before it).
Co-authored-by: Maxime Dénès <maxime.denes@inria.fr>
Co-authored-by: Emilio Jesus Gallego Arias <e+git@x80.org>
|
|
main window.
|
|
(fix #9204)
|
|
Also removing dead code about show_toolbar: this is governed by an
item of the view menu rather than by the preference panel since
aa357d601 (Dec 2003).
|
|
- deprecate the old 5-tuple accessor in favor of a view record,
- move `name` and `kind` proof data from `Proof_global` to `Proof`,
this will prove useful in subsequent functionalizations of the
interface, in particular this is what abstract, which lives in the
monads, needs in order no to access global state.
- Note that `Proof.t` and `Proof_global.t` are redundant anyways.
|
|
|
|
|
|
|
|
Improve debug output
|
|
This is a pre-requisite to use automated formatting tools such as
`ocamlformat`, also, there were quite a few places where the comments
had basically no effect, thus it was confusing for the developer.
p.s: Reading some comments was a lot of fun :)
|
|
Unused since b0da879dc6abfca6b4e233b7469265a5cf52ce15 (see also
followup 4f554c88aa).
|
|
In some cases, toplevel ML clients may want to modify the default set
of flags that is passed to the main initalization routine. This is for
example useful for `idetop` to suppress some undesired printing at
startup.
I would say that clients ought to have more control, but I do expect
that PRs such as #8690 will help providing a better separation thus a
mode orthogonal API.
|
|
|
|
|
|
|
|
|
|
|
|
`CoqProject_file` uses the feedback system, however this is not very
convenient in some scenarios such as `coqdep` that has to be run very
early in the build process [and thus in "boot" mode].
We thus make the warning function a paramater.
Should fix #8913.
|