There are no command line options supported yet (although there's discussion around this and it will come eventually), which means you can't start up the shell in a specific folder, execute a startup command or even pick a profile to start with. One problem currently is that you can't easily automate the terminal application when it launches. You can launch Windows Terminal from anywhere with: wt.exe To make it easy to load, Microsoft provides a globally mapped executable - wt.exe - that you can launch without providing a path from anywhere in your system: From Windows-R, from another console or from another application using CreateProcess() related APIs. It's all very utilitarian which is to be expected - after all the focus first and foremost is on building a better Console Host and it's an early preview. The core terminal functionality is rock solid,īut the Windows UI shell and command interface are not very feature rich around the edges yet. The terminal works great, but it's still in the early stages of development.
There are lots of reasons to like this new Terminal and I don't want to get into all of them here. I've been using Windows Terminal for a while now since it was announced and made available in the Windows Store a few months back. Opening an Admin Windows Terminal from Visual Studio Leaving this post in place for archival purposes only.Ī related and more recent post that talks about launching from other applications can be found here:
This post is mostly obsolete, as Windows Terminal now supports a -d parameter for specifying a startup folder: wt.exe -d "c:\temp".
0 kommentar(er)
