Login to OSNews
Username or Email
Designing Command-Line Interfaces
on Fri 5th Aug 2011 17:42 UTC
Since we're on a CLI kick today, here's an "attempt at presenting some of the most
important guidelines for CLI design
Thread beginning with comment 484037
To view parent comment,
To read all comments associated with this story, please
RE: Comment by abstraction
on Mon 8th Aug 2011 01:50 UTC in reply to "
Comment by abstraction
There is also the issue of output. Any seasoned user know how to redirect stdout to a file (using > for those who don't). This means there is no need to supply an option with where to output the result of a program. It should always go to stdout by default.
Unless it outputs more than one file. Extracting an archive, for example, or running a codegen tool.
Sign Up For The OSNews Newsletter!
Friends & Fans
OSNews Privacy Statement
Notice to Bulk Emailers
© 1997-2013 OSNews Inc. All Rights Reserved. OSNews and the OSNews logo are trademarks of OSNews.
Source Code © 2007-2013,
, except where noted
Reader comments are owned by the poster. We are not responsible for them in any way.
All trademarks, icons, and logos shown or mentioned in this web site are the property of their respective owners.
OSNews.com uses icons from the
© 2008 John Resig
Reproduction of OSNews stories is permitted only with explicit authorization from OSNews. Reproductions must be properly credited.