Users can easily disable text-highlight module with command:
$ gsettings set org.gnome.evolution.text-highlight enabled false
to disable default processing through this module. It's still possible
to manually format certain part with it using the 'Format as' context menu.
The default had been .tar.xz, but as claimed in [1], it makes back up
significantly slower with not much gain on the back up file size. This
change adds a setting to remember what file type had been used the last
time and it is reused the next time the back up is invoked.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1491024
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
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.
