4 ms·

Just to clarify (because TC is shit journalism that’s muddying the console/shell distinction): this is an entirely new replacement for conhost.exe, and PowerShe

Just to clarify (because TC is shit journalism that’s muddying the console/shell distinction): this is an entirely new replacement for conhost.exe, and PowerShell is staying the same? Will cmd, PowerShell and WSL all use the new terminal by default?

zadjii 8y ago
This is a new _Terminal_ application, which is akin to conhost.exe. Powershell, cmd.exe, WSL, they're all unaffected by this change. They all run the same in the new terminal as they did in the old one, thanks to the powerful magic of [ConPty](https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/ https://devblogs.microsoft.com/commandline/windows-command-l...)
- plttn 8y ago
  I think what he's asking is when we download Terminal, will Powershell or WSL just launch Terminal when invoked rather than conhost? Also, how stable/unstable will the preview be?
  - zadjii 8y ago
    Unfortunately, registering a "default terminal application" is _not_ something that's made the cut quite yet. It's something we have plans for, but unfortunately not the dev resources for yet. So for the time being, you'll have to launch the Terminal directly to launch it, and running cmd/powershell will still open in conhost.exe. I don't think we have our release strategy exactly set in stone yet, but I believe the plan is to have a weekly/nightly app users can download that'll be less stable, and an official app, that'll be much more stable.
    - plttn 8y ago
      That's not too bad, considering the primary use of a better terminal would be for WSL use. Can we expect the stable app to launch at the same time as weeklies/nightlies, or will there be a delay?
      - zadjii 8y ago
        Probably a bit of a delay - I wouldn't expect a stable v1 of this before late this year. We have a LOT of features we want to add to the new Terminal, so it'll likely be a while before we get into the stabilization phase

zadjii 8y ago

This is a new _Terminal_ application, which is akin to conhost.exe. Powershell, cmd.exe, WSL, they're all unaffected by this change. They all run the same in the new terminal as they did in the old one, thanks to the powerful magic of [ConPty](https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/ https://devblogs.microsoft.com/commandline/windows-command-l...)

plttn 8y ago
I think what he's asking is when we download Terminal, will Powershell or WSL just launch Terminal when invoked rather than conhost? Also, how stable/unstable will the preview be?
- zadjii 8y ago
  Unfortunately, registering a "default terminal application" is _not_ something that's made the cut quite yet. It's something we have plans for, but unfortunately not the dev resources for yet. So for the time being, you'll have to launch the Terminal directly to launch it, and running cmd/powershell will still open in conhost.exe. I don't think we have our release strategy exactly set in stone yet, but I believe the plan is to have a weekly/nightly app users can download that'll be less stable, and an official app, that'll be much more stable.
  - plttn 8y ago
    That's not too bad, considering the primary use of a better terminal would be for WSL use. Can we expect the stable app to launch at the same time as weeklies/nightlies, or will there be a delay?
    - zadjii 8y ago
      Probably a bit of a delay - I wouldn't expect a stable v1 of this before late this year. We have a LOT of features we want to add to the new Terminal, so it'll likely be a while before we get into the stabilization phase