Command Line Geeks?
-
Yes! I can't live without 4NT[^]. The filename completion and lots of extra built-in commands make life a lot easier. Heck, I even still have the DOS NU tools in my path (like ts - text search in file). They don't show LFNs but I don't care. ;) I think you need to lower your age guess to 25 though. ;P --Mike-- Ericahist | CP SearchBar v2.0.2 | Homepage | RightClick-Encrypt | 1ClickPicGrabber #include "witty-quote.h"
Michael Dunn wrote: Yes! I can't live without 4NT[^]. Me, too. Additionally, I have defined myriads of aliases to easen my daily work. Regards Thomas
Disclaimer:
Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you. -
Wow. I just looked up 4NT and discovered that it costs money. Has it always been like that? IIRC, 4DOS was shareware on DOS (some features disabled). -- Yeah well, my daddy can beat up your daddy!
It's always been payware as long as I can remember. --Mike-- Ericahist | CP SearchBar v2.0.2 | Homepage | RightClick-Encrypt | 1ClickPicGrabber "That probably would've sounded more commanding if I wasn't wearing my yummy sushi pajamas." -- Buffy
-
I'm thinking about posting a handful of articles on tools only of interest to those of us who live in console windows. The question, of course, is whether it's worth it. How many of you live with one or more command prompts open and use them for a significant part of your work? Certainly this has faded out over the years - are there any younger than say 35-40 who do this? -- -Blake (com/bcdev/blake)
Blake Coverett wrote: How many of you live with one or more command prompts open and use them for a significant part of your work? Certainly this has faded out over the years - are there any younger than say 35-40 who do this? I do and I am 31, however I have been programming since I was 8. I always have several 4nt windows open and I do most of my batch builds from there. I modified the vc autobuild sample so that I can batch build VC6 workspaces from the command line. There are also many things that are much faster from the command line like deleting files or how about a recursively deleting all .bak files in a tree. Thats quite a pain in the GUI and simple in the command window. Also I think of the times I need to process 100,000 or more medical images in a batch. Doing this with the GUI is very slow and cumbersome... I can write a one or two line 4nt script to execute all I need and if the parameters change I can repeat the whole batch with a new set of parameters. John
-
-
I just have to add that I find it ironic that any programmer could have such a dim view of the command console. I a very high level, but definitely real sense all programs are just glorified batch scripts compiled into binary form. I've seen a few pure GUI based scripting tools out there and I can't think of one of them that has caught on to the same level as all these "old" text based programming languages. Seriously, a script or command line interface gives the user a level of automation flexability that a graphical interface can't match. The whole advantage of the GUI is that it presents a subset of possible user interactions in a clear easy to interpret screen. It's limit is that there is a finte amount of space which limits the number of commands presented to the user.