Terminal v0.9 is scheduled for February 11, 2020. New: This is the last release that will have new features before the v1 release Subsequent releases are strictly for bug fixes and polishing Features include: Command line arguments new-tab, split-pane, focus-tab Examples: wt -d . (opens a new Terminal in the current working directory) wt -p "profile name" (opens a new Terminal with the given profile) wt; new-tab -p "profile name"; split-pane -V -p "profile name" Accessibility improvements Microsoft Terminal 1.0 Stable Will Be Released in May 2020.
its in pre release stage & can only be installed via windows store app downloads on 1903 or later but what about those on prior builds like 1709 , 1803 or 1809 LTSC. i thought its a installer with msi extension or might be portable executable like powerrshell core .
It’s currently able to be unzipped to whichever folder you want and used in a somewhat portable fashion. For now anyway. 1903 is the minimum version required because of os dependencies in the console infrastructure.
How robust is this Microsoft Terminal compared with PowerShell or Linux terminals? I will try it out later but just wanted to know about people's view on it.
Any idea what forces it to run only online? There are plenty of Apps that work offline but Terminal requires Microsoft Sign-In?Account Manager to connect to its servers to allow the app to start. I dont think this logic is part of the app itself, I think it is the way it is packaged as an app bundle. May be there is some manifest directive we can change to disable it? May be it is the preview nature that forces this for telemetry? Anyone has experience working with apps/bundles guts?
Somehow I doubt it can replace TCC from Jpsoft. I have been using their shell / terminal / whatever you want to call it since the days of 4Dos.
This is interesting. A number of things I didn’t expect, and haven’t seen before. I installed the preview, using the Microsoft Store. Which appears to have added to my path, under my user variables, not System variables: C:\Users\Henry\AppData\Local\Microsoft\WindowApps When I go to that location and look around, there is a file, “wt.exe”, which is 0 bytes in size, but does indeed launch … something. Something which looks and acts a lot like PowerShell, actually. It has read my powershell profile, it has all of my aliases. Heck, this IS powershell, best I can tell.
I did a little more searching and reading. Yes, by default, it runs PowerShell within the terminal. Or, if you do, wt -p "Command Prompt" it will run cmd.exe within the terminal. (Note that is case sensitive, command prompt will not work. No error, you just get PowerShell by default. Since when are windows commands case sensitive?) And why exactly would you want to run cmd.exe within a Windows Terminal? There must be something that I'm missing.