GitLab

If we failed immediately, give the user some information about why we
failed. There is a bit too much plumbing to give the short answer of
"well you haven't built yet", but we can add a short message to give them
a hint.

Fixes #1480

After deferring the start of the rust service to other providers, it
should be save again to enable the provider again.

Notify the user about a missing rust-analyzer executable.

The build is broken currently because LLVM was moved to a separate
extension in https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commit/603cf4e45eb08b46a1b4a3a13c77ae8705eb5163
So use that extension and fix the build.

It should hopefully spare a few hundreds of KB. We don't need the
shared library anyway, as we only use html-tidy through the CLI.

Currently any C -like functions using underscores gets them removed and
instead use them as mnemonic underlines. Of course that's not expected
so this commit fixes it properly.

Related #1472

We require 1.11.2, which we don't have in gnome-build-meta.

This fixes the subsummary issue that crept in when Flatpak removed all
arches from the summaries.

Requires https://github.com/flatpak/flatpak/pull/4256

This makes rust-analyzer output real markdown with proper newlines.

Currently it shows even with the VCS/Build/Tests project tree section.
So do like all other menu items and use hidden-when=action-disabled.

Another big step towards mnemonics everywhere. :)

If the first time the popover is shown only the menu key is used, the popover
will be going upwards instead of to the right. So this commit instead sets
the popover position (i.e. direction) when initializing it instead of when
poping up the popover with the mouse (since the menu key doesn't go through
the same code path here).

Despite not changing anything visually on the first look, the focus
outline is stretched when the valign is left to "fill". So this commit
sets it to "center" so it isn't stretched.

It was because the signal was connected before set_buffer() was
called, when buffer was NULL. Instead just connect notify::file with
the rest of the buffer, and let the existing DzlBindingGroup handle
it with the rest of the buffer signals.

Fixes 7aac27d9

Currently if Builder crashes then all the pages opening/closing/moving
and any state a page had modified will be lost entirely, because saving
is only done when closing the primary workspace, which obviously
doesn't happen cleanly when it crashes.

So to avoid this big issue, this commit adds support for automatically
saving the grid's session state whenever a page is added/closed/moved,
or one of the worthy page properties changes, as defined by its session
addin.

So now Builder should be more reliable to such crashes, or at least
at least the last five minutes of work on the primary workspace will
be saved. It makes crashes less disruptive when working on a project.