Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Subject: Re: setup.exe command line options
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: Keith Starsmeare <keith_starsmeare AT yahoo DOT co DOT uk>
Cc: cygwin-developers AT cygwin DOT com
In-Reply-To: <000901c15e57$56a898e0$6c423c3e@Obsession>
References: <005001c15e52$d4402f70$2c4e3c3e AT Obsession>
	<20011026151819 DOT A1599 AT redhat DOT com> 
	<000901c15e57$56a898e0$6c423c3e AT Obsession>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15 (Preview Release)
Date: 31 Oct 2001 21:27:40 +1100
Message-Id: <1004524061.1121.48.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 31 Oct 2001 10:31:54.0923 (UTC) FILETIME=[42D61FB0:01C161F7]

On Sat, 2001-10-27 at 05:49, Keith Starsmeare wrote:
>
> One other thing would be a --help option, is there a way that I can output
> to stdout? printf, and fprintf(stdout,..) don't output to the command line.
> I'm currently using fprintf(stderr, ..), which brings up a handy dialog box,
> for tracing.

The console from gui-mode program issue has been covered twice recently,
I think on cygwin-xfree86 and on cygwin-apps. 

IMO for setup a simple dynamically constructed window with the options
written therein is appropriate. However, in terms of gain-to-time,
having the options working is much more important, we can always
document them on the web site somewhere until setup can spit them out
itself.

And, in fact, external only doco might be worth doing as a preference,
to avoid the nonsense "I ran setup with --foo and it did bar"... "Have
you read the setup.exe documentation?" "What Documentation?" "The FAQ!"
"No, I simply ran with -? and guessed at what would happen!" style
conversations.

Rob