https://bugs.documentfoundation.org/show_bug.cgi?id=100932
Bug ID: 100932
Summary: Consider adding logging for command line / shell
--headless usage
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: [email protected]
Reporter: [email protected]
A common usecase for Libreoffice writer is to act as a headless rendering
component.
While the UNO API can be used, the command line options like --convert-to seem
to offer a much lower barrier to entry.
Unfortunately; things like #37531 crop up.
Examples of confused users:
http://stackoverflow.com/questions/22062973/libreoffice-convert-to-not-working
* Silent 'failure', users only figuring out they haven't installed
libreoffice-writer by accident, etc.
http://stackoverflow.com/questions/24704536/how-do-i-convert-doc-files-to-txt-using-libreoffice-from-the-command-line/38397232
* Others figuring out open instances of libreoffice are getting passed
commands; but missing they can specify a per user environment
etc.
While --backtrace does exist, it isn't often too helpful.
>From IRC discussion:
vmiklos: most logging is done using SAL_INFO() / SAL_WARN(), and those expand
to nothing on release builds.
Could a build of libreoffice (particularly what a lot of distros package up as
libreoffice-headless) be configured to allow SAL_INFO/SAL_WARN to output to
STDOUT/STDERR via a --verbose or --debug type argument if used with --headless.
This would keep the existing silent behaviour for desktop users, but allow
semi-technical users to gain some insight if they opt in.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
