Bug 67010 - Other: soffice.bin usage prints to modal window instead of STDOUT
Summary: Other: soffice.bin usage prints to modal window instead of STDOUT
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-17 19:00 UTC by Travis Mann
Modified: 2013-07-18 08:28 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
screenshot of modal usage window (95.64 KB, image/jpeg)
2013-07-17 19:00 UTC, Travis Mann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Travis Mann 2013-07-17 19:00:58 UTC
Created attachment 82561 [details]
screenshot of modal usage window

Problem description: 
soffice.bin prints command line usage instructions to a modal window instead of STDOUT. 

Steps to reproduce:
1. Run one the following commands from the command line:
soffice.bin -help

soffice.bin -invalid_parameter


Current behavior:
soffice.bin prints command line usage instructions to a modal window

Expected behavior:
soffice.bin prints command line usage instructions to STDOUT

Operating System: Windows 7
Version: 4.0.4.2 release
Comment 1 Michael Meeks 2013-07-18 08:28:26 UTC
This behaves as designed cf. desktop/source/app/cmdlinehelp.cxx at least on Windows - where people are extremely unlikely to use the shell, debugging process execution is not as easy as eg. strace :-) and yet sometimes other apps pass invalid arguments into launch soffice behind the scenes.

Naturally if there is some good way of detecting the fact that the client launched from a terminal - [ is there a standard environment variable ] - then we could add that (potentially for all platforms), and ensure that we get a GUI dialog vs. console output but only if the console is interactive [ or somesuch ].

If you'd like to work on that, just re-open this as an Enhancement bug & I'll provide some more code pointers [ but it's all in desktop/source/app that you'd want to hack on that ].

Thanks for the report !