It makes the window to activate the Mail view, but it fails to switch
to the correct folder. The problem was that folder_name was actually
the folder_uri.
The later seems to be unreliable, returning no targets when pasting
into the composer, while the former returns the targets reliably.
Hard to tell what failed for the later, but as long as the other one
works, then prefer it over the other.
Namely this one:
evolution-util-CRITICAL **: e_content_request_process: assertion 'G_IS_OBJECT (requester)' failed
which could show up on close. The 'requester' had been NULL, thus
it caused no harm in memory, but it is still better to cancel
the request gracefully, than claim on the console.
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.
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.
