This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
RE: Console on Sourceforge with Cygwin
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'35 more silly cygwin hippo references until beer o'clock'" <cygwin-talk at cygwin dot com>
- Date: Wed, 30 Aug 2006 16:25:19 +0100
- Subject: RE: Console on Sourceforge with Cygwin
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On 30 August 2006 16:19, mwoehlke wrote:
> One Angry User wrote:
>> On a drizzly Tuesday, the 29th day of August, 2006, Keith Christian's
>> computer deigned to emit the following stream of bytes:
>>> Could you provide one example for a user that would start with "Click
>>> Start/Run and type the following command"
>>
>> Oh, no, it doesn't work like that. Command-line options are for wimps who
>> read manpages! Console uses menus! MENUS, man! Now, there's real
>> configurability!
>
> Sigh.
>
> Command line options are wonderful... for console programs. GUI's are
> for writing apps such that settings can be discovered /without/ having
> to resort to the doc. I suppose you think Firefox, Thunderbird, IE, etc.
> need manpages, and should only be configurable via command-line
> switches?
It's not as orthogonal as all that. Sometimes a GUI program isn't just a
GUI program. Sometimes, even though it has a GUI, all you want to do is
script it - at which point, you *have* to have command-line options.
So, command line options are wonderful for GUI programs *as well as* console
programs. After all, consider the ever-popular post that goes ...
"Hi, can anyone tell me what command-line options I can use to get setup.exe
to do a completely unattended installation and choose a selection of
packages?"
Oops, I just said it.
*sip*
<heh>
cheers,
DaveK
--
Can't think of a witty .sigline today....