Hi,
Tor Lillqvist-2 wrote
Needed also for soffice.bin . (I don't recall, but it might be that
editbin doesn't believe a file called .bin is an exectuable, so you
might need to temporarily rename soffice.bin to foo.exe, run editbin
on it, and rename back.)
Thanks. It works. (Renaming soffice.bin is not necessary.)
It doesn’t display errors while running, but it’s possible to get them with
:
try:
# code
except:
traceback.print_exc()
So that’s really useful.
Tor Lillqvist-2 wrote
We could just add a few lines of code to a suitable place that would
make all our programs automatically show stdout and stderr in the
console shell if they are started from a such, on Windows.
Looks good to me.
Regards,
Olivier
--
View this message in context:
http://nabble.documentfoundation.org/LibreOffice-prints-on-tuesdays-tp4047259p4050370.html
Sent from the Dev mailing list archive at Nabble.com.
Context
- Re: Removing C++ SDK examples, clearly encouraging Python extensions (was: LibreOffice prints on tuesdays) (continued)
Re: Removing C++ SDK examples, clearly encouraging Python extensions · Stephan Bergmann
Re: Removing C++ SDK examples, clearly encouraging Python extensions (was: LibreOffice prints on tuesdays) · Thorsten Behrens
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.