+1
In addition to using it to download and run, making any documented debugging tools available to us can only help development.
+1 to this also
Yes, the --help and -h flags should also print out a summary of the options and exit (rather then just starting steam like the currently do).
As a side note, invalid options should be reported and then the executable exits like all other Linux programs do.
For all it's worth, using the following locks you into offline mode:
steam --offline
This is such an obvious oversight... documenting basic options in a manpage. I shouldn't have to spend 30+ minutes googling trying to figure out how to launch steam into big picture mode from the commandline. I did find this... steam steam://store , certainly if there's a steam:// URI, it must be documented somewhere that's easy to find...
Many of the Windows commands seem to work and game commands still work.
Game/Windows/Server commands: https://developer.valvesoftware.com/wiki/Command_Line_Options
Steam browser protocol information: https://developer.valvesoftware.com/wiki/Steam_browser_protocol
Nothing extracted yet.
I know you can run/download steam games using:
Example for TF2:
It would be nice to see this documented when using
Extra command line features would be highly appreciated as well. I think there's quite a lot of people that would love to use steam from the command line.