GitLab

Then it's pretty hard to change that name, or even write anything to it.

Since now, users can change theme being used by the text-highlight module,
not being forced to use a hard-coded theme in the code. First of all,
figure out which themes are installed. It's done with command:

   $ highlight --list-scripts=themes

Pick one, say "editor-vim-dark" (supposing it's installed), and execute:

   $ gsettings set org.gnome.evolution.text-highlight theme edit-vim-dark

And the next time the text-highlight will be called, like when changing the used
format with right-click in the body->Format As->..., the changed theme will
be used. In case the value being set in the GSettings is no longer valid,
like when the theme is not available or had been uninstalled, there will be
no formatting in the message content at all and evolution's console may
contain an error message from highlight, like this one:

   highlight: cannot open themes/unknown.theme: No such file or directory

As pointed out in bug 784209, the --module-dir should be the 'html'
directory, which wasn't a problem with 1.25, but git master of gtk-doc
fails to find html files when it was set to the current directory.

See https://developer.gnome.org/hig/stable/typography.html

https://bugzilla.gnome.org/show_bug.cgi?id=774377

Two changes being done:
a) special value 'stdout', or an empty string, for 'filters-log-file'
   will make logging into stdout
b) running with CAMEL_DEBUG=filters also turns on logging to stdout.

The output file from GSettings has precedence over the stdout used
by CAMEL_DEBUG, when both loggings are enabled. In other words, in case
GSettings has enabled logging, then GSettings dictate which file is
used for the log, otherwise GSettings values are ignored and stdout
is used only when CAMEL_DEBUG logging is enabled.

The accounts were in some artificial disorder, better to use the same
order as the folder tree, then eventually name/mail address. Aliases
are right below the main address of the account they belong to.

See https://developer.gnome.org/hig/stable/typography.html

https://bugzilla.gnome.org/show_bug.cgi?id=774377

These used to show their raw names in the UI, which didn't look correct.

This properly updates sources for inclusion also when adding/removing
them for alarms, while the previous behaviour listened only for source's
enabled/disabled/added/removed notifications, which was not correct.

Related to bug #739955, where is also a little explanation [1] what led
to this change.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=739955#c22