Microsoft clarifies: Windows Terminal will not replace Command Prompt
-
Instead, Windows Terminal is designed to provide a more modern and feature-rich interface for command-line enthusiasts, offering the flexibility to work with various command-line applications, including Command Prompt, PowerShell, and others.
Because people just love their batch files
Yeah, I know you can host cmd in terminal and get your batch files done that way. But it really just brings up the point again, "what's the point of terminal anyway?" "command-line enthusiasts"?!?!?
-
Instead, Windows Terminal is designed to provide a more modern and feature-rich interface for command-line enthusiasts, offering the flexibility to work with various command-line applications, including Command Prompt, PowerShell, and others.
Because people just love their batch files
Yeah, I know you can host cmd in terminal and get your batch files done that way. But it really just brings up the point again, "what's the point of terminal anyway?" "command-line enthusiasts"?!?!?
Kent Sharkey wrote:
But it really just brings up the point again, "what's the point of terminal anyway?"
Only because you can do something...
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Instead, Windows Terminal is designed to provide a more modern and feature-rich interface for command-line enthusiasts, offering the flexibility to work with various command-line applications, including Command Prompt, PowerShell, and others.
Because people just love their batch files
Yeah, I know you can host cmd in terminal and get your batch files done that way. But it really just brings up the point again, "what's the point of terminal anyway?" "command-line enthusiasts"?!?!?
-
Instead, Windows Terminal is designed to provide a more modern and feature-rich interface for command-line enthusiasts, offering the flexibility to work with various command-line applications, including Command Prompt, PowerShell, and others.
Because people just love their batch files
Yeah, I know you can host cmd in terminal and get your batch files done that way. But it really just brings up the point again, "what's the point of terminal anyway?" "command-line enthusiasts"?!?!?
Kent Sharkey wrote:
Because people just love their batch files
You'll take away my batch files and my
Command Promptwhen you pry them from my cold, dead fingers(*). Or when I retire in 2028. (*) Be careful. The edges of the window will be very hot. (paraphrasing JSOP)Software Zen:
delete this; -
Kent Sharkey wrote:
Because people just love their batch files
You'll take away my batch files and my
Command Promptwhen you pry them from my cold, dead fingers(*). Or when I retire in 2028. (*) Be careful. The edges of the window will be very hot. (paraphrasing JSOP)Software Zen:
delete this; -
I still use cmd and vbs scripts. They're lightweight when compared to PowerShell and a whole lot easier to read.
For a long time our automated build process was a grotesque collection of batch files, VBS scripts, and some executables. A little over ten years ago I rewrote the whole mess as a Windows service in C#. Vastly easier to maintain, enhance, and debug.
Software Zen:
delete this; -
For a long time our automated build process was a grotesque collection of batch files, VBS scripts, and some executables. A little over ten years ago I rewrote the whole mess as a Windows service in C#. Vastly easier to maintain, enhance, and debug.
Software Zen:
delete this;