Linked by Thom Holwerda on Mon 27th Feb 2006 18:29 UTC
Permalink for comment 99899
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2006-01-14
Maybe all of what you say is true. But, the most difficult thing I find about using the command line in Windows is not that you couldn't accomplish things with batch file scripting. The problem is that it's always like typing with 10 thumbs. For example, Windows forgets its history between sessions.
Another example is that the arrow keys don't take you backwards from where you are in the history. They take you back from wherever you might have been in the history when you last used it. OK. That's kinda hard to explain. So, let me give you an example. Say you are like me and you use vi to edit a *.cpp file. Then, you compile with gcc. Finally, you execute with ./a.out. In *nix, you can hit the up arrow 3 times to edit, 3 more times to compile and 3 more times to run your file. You can do that all day in *nix. But, in Windows, you eventually come to the beginning (or end) of your history.
Also, a good tabbed console like Konsole would be good. If Monad ignores usability, it will still suck to have to use.
You know, I don't really find Windows scripting so lackluster. In fact, I don't use Bash for scripting. I use Python. What I need is a good command line interface that will allow me write Python scripts in vi.
backdoc