https://bugs.freedesktop.org/show_bug.cgi?id=51639
--- Comment #10 from Tor Lillqvist <[email protected]> 2012-07-08 06:06:24 PDT --- But we don't add the "program" folder to the system PATH, do we? So to find out from where to run soffice.exe the script would need to look in the registry or something, no? Is it then really much harder for the script to just look in the version.ini file in the same location as soffice.exe. Not that I am sure if version.ini contains anything usable, at least in my LO which in Help:About identifies itself as 3.5.3.2 nothing in version.ini says 3.5.3.2... Anyway, one basic problem right in the initial question is the concept "print on stdout". soffice.exe is a so-called "GUI executable" which means that its stdout and stderr are *not* connected anywhere, especially not to the console window even if they are started from a cmd.exe in a console window. One would have to redirect stdout from the cmd.exe command line to a file, or pipe it to for instance the "more" command. My recommendation is that instead of making soffice.exe --version print some kind of version information to "stdout", we should just make sure version.ini contains some version information that matches the version number as shown by Help:About (in addition to the other cruft it currently contains, some of which is probably fairly pointless). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
