I'm re-enabling macros inside the diff template dialog, in next beta.
As said elsewhere, the reason for forbidding was
that .vfs files (those where your virtual file system is saved) could become just like MS Word .doc, and carry malicious instructions.
Indeed, you load others' VFS files very rarely, i guess, but safety is crucial.
So, the new behaviour will be: when a macro is found inside the .vfs, i will warn the user
"This file contains macros.
If you got this file from someone else, then it's dangerous, because macros can delete files.
Abort loading?"
I guess you don't load vfs files very often, so this dialog won't bother that much.
And an inattentive user, who clicks YES everywhere, would just abort the loading instead of continuing in a risky operation.
I think this method is safe enough. I'm open to other opinions.