Windows Command Line Buffer that doesn't clear on close?

Windows Command Line Buffer that doesn't clear on close?

When I was working with RedHat at Uni, one of the things I liked most about the command line was that it stored commands from previous sessions to its buffer for long-term retrieval. The ability to press up a couple of times and rerun a command set from yesterday was a big help in getting me to accept the notion of typing being better than clicking.

Asked by: Guest | Views: 425

Total answers/comments: 2

Comments display order:

Guest [Entry]

"Cygwin is the best option here. It keeps command history just like your unix shell does on a genuine unix box. Something to be said about cygwin is that it supports all of the native shell commands that windows ""knows and loves"".

So do not think just because you are running it in a cygwin shell that you have any limited functionality. Cygwin appears to be running right on top of a command shell within windows."

Guest [Entry]

"I'd suggest you to use Far manager on a daily basic (http://www.farmanager.com). So, in Far CTRL-E works as a switcher of previous commands, even from yesterday and the day before yesterday.

As for the software, Far Manager is a long time successor of Norton Commander (or I'd say it was inspired by) created by the author of Rar compression utility. The stable version is a shareware, but even as a non-registered shareware quite useful. Also recently an open-source unicode version supported by a group of developers started. Far has a plugin system (for example WinSCP plugin from the author of WinSCP and tons of other plugins). It's a good replacement of cmd for any command-line operations (if you know or knew NC, you know what I mean) and from the other side the replacement of explorer if you prefer keyboard to mouse. I can't remember when I last time copied something with explorer or anything else :)"