Skip to content
The new Windows Terminal, and the original Windows console host -- all in the same place!
Branch: master
Clone or download
DJackman123 and adiviness Add feature to ColorTool to write color scheme as JSON for Windows Te…
…rminal (issue #986) (#1052)

* Add a new console target that writes the color scheme to stdout in JSON format for copying into a Windows Terminal profiles.json file.

* Update src/tools/ColorTool/ColorTool/ConsoleTargets/TerminalSchemeConsoleTarget.cs

Co-Authored-By: Michael Niksa <miniksa@microsoft.com>

* Create a base class for scheme parsers for common code and helpers.  Fix string formatting according to review comments.
Latest commit 04e808f Jun 25, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add explicit "validation steps" to PR template (#1140) Jun 4, 2019
.nuget Update razzle to use vswhere (#13) (#606) May 10, 2019
build split code format check into its own job (#1270) Jun 14, 2019
dep add audit build step for code formatting check (#1208) Jun 11, 2019
doc doc: Add ColorTool link to profiles.json documentation (#1396) Jun 23, 2019
pkg/appx Initial release of the Windows Terminal source code May 2, 2019
res Integrate the new icon; license assets under CC BY-ND 4.0 (#1303) Jun 18, 2019
samples Some Typo-Fixes in Comments (#1049) May 29, 2019
src Add feature to ColorTool to write color scheme as JSON for Windows Te… Jun 25, 2019
tools tools: add support for the -Prerelease VS locations (#1202) Jun 12, 2019
.clang-format add clang-format conf to the project, format the c++ code (#1141) Jun 11, 2019
.editorconfig add .editorconfig file (#585) May 24, 2019
.gitattributes Initial release of the Windows Terminal source code May 2, 2019
.gitignore Fix OpenConsole.psm1 to use vswhere (#1113) Jun 7, 2019
.gitmodules Lowercase GH org name in .gitmodules (#629) May 9, 2019
.vsconfig Remove ATL from .vsconfig! (#954) May 23, 2019
CODE_OF_CONDUCT.md Add a README and a CODE_OF_CONDUCT May 6, 2019
LICENSE Initial release of the Windows Terminal source code May 2, 2019
NOTICE.md Switch to jsoncpp as our json library (#1005) Jun 4, 2019
NuGet.Config Tab to spaces (#578) May 14, 2019
OpenConsole.sln Apply a GDI region to the top level Island window to allow dragging w… Jun 25, 2019
README.md doc: fix some punctuation in README.md (#1512) Jun 24, 2019
common.openconsole.props Initial release of the Windows Terminal source code May 2, 2019
consolegit2gitfilters.json inbox: Reflect Windows inbox changes from 20190516 May 16, 2019
dirs Initial release of the Windows Terminal source code May 2, 2019

README.md

Welcome!

This repository contains the source code for:

  • Windows Terminal
  • The Windows console host (conhost.exe)
  • Components shared between the two projects
  • ColorTool
  • Sample projects that show how to consume the Windows Console APIs

Other related repositories include:

Build Status

Project Build Status
Terminal Build Status
ColorTool

Terminal & Console Overview

Please take a few minutes to review the overview below before diving into the code:

Windows Terminal

Windows Terminal is a new, modern, feature-rich, productive terminal application for command-line users. It includes many of the features most frequently requested by the Windows command-line community including support for tabs, rich text, globalization, configurability, theming & styling, and more.

The Terminal will also need to meet our goals and measures to ensure it remains fast, and efficient, and doesn't consume vast amounts of memory or power.

The Windows console host

The Windows console host, conhost.exe, is Windows' original command-line user experience. It implements Windows' command-line infrastructure, and is responsible for hosting the Windows Console API, input engine, rendering engine, and user preferences. The console host code in this repository is the actual source from which the conhost.exe in Windows itself is built.

Console's primary goal is to remain backwards-compatible with existing console subsystem applications.

Since assuming ownership of the Windows command-line in 2014, the team has added several new features to the Console, including window transparency, line-based selection, support for ANSI / Virtual Terminal sequences, 24-bit color, a Pseudoconsole ("ConPTY"), and more.

However, because the Console's primary goal is to maintain backward compatibility, we've been unable to add many of the features the community has been asking for, and which we've been wanting to add for the last several years--like tabs!

These limitations led us to create the new Windows Terminal.

Shared Components

While overhauling the Console, we've modernized its codebase considerably. We've cleanly separated logical entities into modules and classes, introduced some key extensibility points, replaced several old, home-grown collections and containers with safer, more efficient STL containers, and made the code simpler and safer by using Microsoft's WIL header library.

This overhaul work resulted in the creation of several key components that would be useful for any terminal implementation on Windows, including a new DirectWrite-based text layout and rendering engine, a text buffer capable of storing both UTF-16 and UTF-8, and a VT parser/emitter.

Building a new terminal

When we started building the new terminal application, we explored and evaluated several approaches and technology stacks. We ultimately decided that our goals would be best met by sticking with C++ and sharing the aforementioned modernized components, placing them atop the modern Windows application platform and UI framework.

Further, we realized that this would allow us to build the terminal's renderer and input stack as a reusable Windows UI control that others can incorporate into their applications.

FAQ

Where can I download Windows Terminal?

The Windows Terminal preview can be downloaded from the Microsoft Store.

https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701

I built and ran the new Terminal, but I just get a blank window app!

Make sure you are building for your computer's architecture. If your box has a 64-bit Windows, change your Solution Platform to x64.
To check your OS architecture go to Settings -> System -> About (or Win+X -> System) and under Device specifications check for the System type.

I built and ran the new Terminal, but it looks just like the old console! What gives?

Firstly, make sure you're building & deploying CascadiaPackage in Visual Studio, NOT Host.EXE. OpenConsole.exe is just conhost.exe, the same old console you know and love. opencon.cmd will launch openconsole.exe, and unfortunately, openterm.cmd is currently broken.

Secondly, try pressing Ctrl + T. The tabs are hidden when you only have one tab by default. In the future, the UI will be dramatically different, but for now, the defaults are supposed to look like the console defaults.

I tried running WindowsTerminal.exe and it crashes!

  • Don't try to run it unpackaged. Make sure to build & deploy CascadiaPackage from Visual Studio, and run the Windows Terminal (Dev Build) app.
  • Make sure you're on the right version of Windows. You'll need to be on Insider's builds, or wait for the 1903 release, as the Windows Terminal REQUIRES features from the latest Windows release.

Getting Started

Debugging

  • To debug in VS, right click on CascadiaPackage (from VS Solution Explorer) and go to properties, in the Debug menu, change "Application process" and "Background task process" to "Native Only".

Contributing

We are excited to work alongside you, our amazing community, to build and enhance Windows Terminal!

We ask that before you start work on a feature that you would like to contribute, please read our Contributor's Guide. We will be happy to work with you to figure out the best approach, provide guidance and mentorship throughout feature development, and help avoid any wasted or duplicate effort.

👉 Remember! Your contributions may be incorporated into future versions of Windows! Because of this, all pull requests will be subject to the same level of scrutiny for quality, coding standards, performance, globalization, accessibility, and compatibility as those of our internal contributors.

Note: The Command-Line Team is actively working out of this repository and will be periodically re-structuring the code to make it easier to comprehend, navigate, build, test, and contribute to, so DO expect significant changes to code layout on a regular basis.

Documentation

All documentation is located in the ./doc folder. If you would like to contribute to the documentation, please submit a pull request.

Communicating with the Team

The easiest way to communicate with the team is via GitHub issues. Please file new issues, feature requests and suggestions, but DO search for similar open/closed pre-existing issues before you do.

Please help us keep this repository clean, inclusive, and fun! We will not tolerate any abusive, rude, disrespectful or inappropriate behavior. Read our Code of Conduct for more details.

If you would like to ask a question that you feel doesn't warrant an issue (yet), please reach out to us via Twitter:

Developer Guidance

Build Prerequisites

  • You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal.

  • You must have the 1903 SDK (build 10.0.18362.0) installed.

  • You must have at least VS 2017 installed.

  • You must install the following Workloads via the VS Installer. If you're running VS 2019, opening the solution will prompt you to install missing components automatically.

    • Desktop Development with C++
    • Universal Windows Platform Development
      • Also install the following Individual Component:
        • C++ (v141) Universal Windows Platform Tools
  • You must also enable Developer Mode in the Windows Settings app to locally install and run the Terminal app.

Building the Code

This repository uses git submodules for some of its dependencies. To make sure submodules are restored or updated, be sure to run the following prior to building:

git submodule update --init --recursive

OpenConsole.sln may be built from within Visual Studio or from the command-line using MSBuild. To build from the command line, find your shell below.

PowerShell

Import-Module .\tools\OpenConsole.psm1
Set-MsBuildDevEnvironment
Invoke-OpenConsoleBuild

CMD

.\tools\razzle.cmd
bcz

We've provided a set of convenience scripts as well as README in the /tools directory to help automate the process of building and running tests.

Coding Guidance

Please review these brief docs below relating to our coding standards etc.

👉 If you find something missing from these docs, feel free to contribute to any of our documentation files anywhere in the repository (or make some new ones!)

This is a work in progress as we learn what we'll need to provide people in order to be effective contributors to our project.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

You can’t perform that action at this time.