I guess I may not be like other users but typically I just write the 2 minutes worth of script and add that to whatever menu's applicable config(root menu left-click in fvwm, kde's bar, or whatever); I'd say that most commandline progs are _extremely_ intuitive, because on standards (ie posix, UNIX, etc) typing '-v' or '-q' is fairly likely to increase verbosity or decrease (quiet) output respectively; usually one can even guess at what arguments a prog would require (ie PROGNAME infile [outfile] --able to guess an optional second argument is name of outfile). '-' or '-c' for stdin unless it makes sense for this to be the default; many many more. I find it _extremely_ rare being within a gui on any prog on any OS and not being able to figure out how some task is to be done. When things get really bad a quick trip to the help button usually helps matters along (ironically enough). And I agree that for others like myself who do some pretty squirrelly things, windows help can prove futile and Kde's help while being a rather large system, covers only elementary issues (I used in version 2.0 may be drastically different now). Are there others who feel that most gui's are pretty self explanatory?
I've had my share of bad floppies, but what astounds me is how quickly floppy drives/floppy controllers fail. I and others I know use the thing pretty rarely but, man do they break like nobody's business. I admit that I usually buy cheap mobo's.
Slashdot Mirror
He's looking for these devices for"reference" yeah sure. He's obviously trying to take over the world.
I was wondering the same think myself; do you think folks'll try to crack that huge key twice if they did?
I guess I may not be like other users but typically I just write the 2 minutes worth of script and add that to whatever menu's applicable config(root menu left-click in fvwm, kde's bar, or whatever); I'd say that most commandline progs are _extremely_ intuitive, because on standards (ie posix, UNIX, etc) typing '-v' or '-q' is fairly likely to increase verbosity or decrease (quiet) output respectively; usually one can even guess at what arguments a prog would require (ie PROGNAME infile [outfile] --able to guess an optional second argument is name of outfile). '-' or '-c' for stdin unless it makes sense for this to be the default; many many more. I find it _extremely_ rare being within a gui on any prog on any OS and not being able to figure out how some task is to be done. When things get really bad a quick trip to the help button usually helps matters along (ironically enough). And I agree that for others like myself who do some pretty squirrelly things, windows help can prove futile and Kde's help while being a rather large system, covers only elementary issues (I used in version 2.0 may be drastically different now). Are there others who feel that most gui's are pretty self explanatory?
Oh great two way internet access, what will they think of next!!
oh they mean like-- not like satellite, um... nevermind.
2 huge, throbbing k's of pr0n goodness :)~
I've had my share of bad floppies, but what astounds me is how quickly floppy drives /floppy controllers fail. I and others I know use the thing pretty rarely but, man do they break like nobody's business. I admit that I usually buy cheap mobo's.