This is the mail archive of the cygwin-talk mailing list for the cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Console on Sourceforge with Cygwin

"Dave Korn" <> wrote in message 046201c6cc48$80a00480$a501a8c0@CAM.ARTIMI.COM">news:046201c6cc48$80a00480$a501a8c0@CAM.ARTIMI.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


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

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.

No, that is not nessisary for scripting. Applescript works just fine on Mac programs
that have no command line arguments. On Windows, COM (aka Active-X) allows
scripting of programs without command line arguments.

I will admit that batch command line scripting (as generally offered by shells) is much
easier with command line options, but even then it might not be nessisary in some circumstances.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]