Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 2011-06-27, Stephan Zietsman wrote:

Tom wrote:
I think on Windows you can "pipe" commands although it's a bit different from
gnu&linux or bsd.  I htink there is a way of piping output into a text-file but
i don't know how.  This might work tho

soffice.exe -? | more

The "|more" option does work when listing help for other types of
commands (such as "help |more"), but unfortunately it doesn't work in
this case.  The main difference in this case is that the help text is
not echoed to the prompt (terminal), but it is rather displayed in a
message pop-up, which truncates (cuts off) the text at some point.

According to the code, only UNIX systems get the help text written to
the console. Everything else gets a dialog box.

,----[desktop/source/app/cmdlinehelp.cxx, line 154]
| #ifdef UNX
|         // on unix use console for output
|         fprintf(stdout, "%s%s",
| [...]
| #else
|         // rest gets a dialog box
|         CmdlineHelpDialog aDlg;
`----

-- 
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg

-- 
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.