|
From: Thomas J. H. <shi...@sh...> - 2002-05-30 12:50:18
|
At 01:16 PM 5/30/2002 +0200, Joachim Breuer writeth:
>Now I will pipe in here...
Me too...
>Jason Filby <jas...@ya...> writes:
>
>Linux *administrators* got used to powerful features of the command
>line; my administrating of said winboxen would take at least twice as
>long without cygwin available (copy all files meeting certain criteria
>from here to there *keeping their relative pathnames* is something cmd
>and the explorer are not really good at - ideas welcome).
How about XCOPY? It is a highly versatile copy command that I use
regularly for backup purposes onto other drives/systems.
>Cygwin would *almost* be an solution if win's console werent utterly
>broken (by design). Please do not try to argue with me on that, repeat
>after me, win's console (as it is implemented today in 2k) is UNUSABLE
>for a command line power user. (Selection behaviour, size change
>restrictions are the major showstoppers). OK so maybe I can run the
>cygwin shell in an XTerm with it all sitting on 55+ compatibility
>layers, but the fact remains that the not-worked-around basic OS
>concept in that area is broken.
I've used Linux, DOS, Win3.x, Win95/98/Me/NT/2000 and have had no problems
or difficulties with the command prompt under Windows. Linux may have a
powerful set of features, but I have never used more than 20% of them.
That says that there are too many features for me. My home environment is
DOS and over the years I have written several hundred batch files to aid me
in day-to-day chores. I consider myself a "power user" and place heavy
demands on the command line every single day (unless I'm busy writing a few
thousand lines of code).
>BTW: If anyone feels like seriously thinking abouth some of these
>'limitations' I could certainly flesh out a wishlist for 'doze from an
>unix administrator's point of view.
I know there are limitations, but I have only had to write programs on
occasion to do what I want to do. Particularly, pipes are extremely
limited with base OS commands (hence I wrote a program called PIPE) and
directory depth is limited (haven't bothered to write a program). Really,
most of the problems with the command line/batch files have to do with
backwards campatibility issues to DOS v3.0 than anything else. Microsoft's
trying to make people move to VBScript (yuck) so they can get rid of the
Console API, but we can thank large companies that demand command prompt
functionality and so both still exist (which is good for the rest of us :)
Hope this helps!
Thomas J. Hruska -- shi...@sh...
Shining Light Productions -- "Meeting the needs of fellow programmers"
http://www.shininglightpro.com/
|