On Fri, 2011-08-26 at 13:08 -0400, Terrence Enger wrote:
Meanwhile, looking under Tools > Options > LibreOffice >
Paths, I see that my local builds put things under
~/.config/libreoffice, and sure enough there is
shall go try that.
That file lacked the entry for MacroSecurityLevel. Adding
it changed the program behaviour, but not for the better.
And then the program wiped out the entry.
Better news: In the build from aa51fd4-4eb4f62-260b7c1, the
program allows execution for a new module. The build from
c305fc3 is not quite so cooperative: bug 40420 "SIGSEGV,
So, I have what I need for my own playing around. Thank
you, Regina, for your pointers.
The remaining questions are ... Does anybody else share the
problem of the ineffective "MacroSecurity..." button? Does
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy