GNOME Bugzilla – Bug 775643
Autoconfig: Support also Signature sources
Last modified: 2016-12-21 14:37:37 UTC
As a follow up of the bug #773156: The Autoconfig should also support signature sources, which are more complicated than simple .source files. The current rule is that a signature .source contains a [Mail Signature] section (e-source-mail-signature.h/.c extension). Exactly the same filename, without the .source extension, is stored in the ~/.config/evolution/signatures/ folder. Create some such signatures in Edit->Preferences->Composer Preferences->Signatures tab, to see how it works in action. I suggest to create all 3 types and properly test them, especially test HTML messages with inline images and that copying a script signature will still keep it working/executable. We can force a notation that the autoconfig/ directory will contain at least the below two files for the signatures of exactly the same name, but different extension, like: company-sig.source ... contains the ESource data company-sig.signature ... contains the actual signature content and when copying the .signature file its extension will be removed.
Made as suggested above. Couple notes: - inline images (not emoticons) are currently referenced as file:///.... URLs, thus the signature creator should have on mind to use a storage which the all users have reachable - the signature itself is also processed by the variable replacement on copy Created commit e8e831b in eds master (3.23.4+)