There is no real need to expose the dependency and with the change
of the enachant version it could be problematic to forward the right
enchant include folder to the library user, thus it's easier to just
hide the dependency.
The now deprecated e_cal_recur_nth array usage with bare _() didn't always
work, it worked here only due to the same strings being marked for
translation in the "evolution" translation domain, which avoids
the intention of not localizing the same string multiple times.
It could happen that the snapshot save got interrupted by other UI
code, one of them being composer close, which causes the composer's
dispose() execution, even it has more than one ref_count. The dispose()
frees the content widgets, which results in use-after-free when
the snapshot save continues its execution. The interrupt was possible
also due to several asynchronous calls being involved during the save.
This had been reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1538865
Indentation gap had been added in front of every text in the indented block,
which can be wrong in cases where the text is "split" by an anchor, for example
when added by magic-links. There was used wrong indentation gap in the plain
text version too (3 in UI versus 4 spaces in plain text per level).
This had been reported downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1538775
The runtime warnings were:
- null pointer passed as argument NNN, which is declared to never be null
- left shift of MMM by NNN places cannot be represented in type 'int'
There had already been a workaround for EClientCache, which proved
to be sub-optimal, and it can strike on more places, thus better
to load the extension modules before EShell is created.
As it had been before this change, once any account had Google built-in
OAuth2 authentication, it had been offered to every account of that provider,
which is wrong. This change adds/removes particular built-in OAuth2
authentication methods on demand, also when changing server host name,
without influencing any other account.
It's using the same mime type, but the code to make it a real file
or anything like that fails. With this change the button (or the image
of it on the right side of the button) can be dragged into the folder
tree or message list, importing it into the mail folder.
