Microsoft terminal service linux

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

The new Windows Terminal and the original Windows console host, all in the same place!

License

microsoft/terminal

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

This reverts a number of changes to input handling to how it used to be in conhost v1. It merges the input event coalescing logic into a single function and inlines the console suspension event handling, because soon these functions will receive `std::span` arguments which cannot be preprocessed anymore, unlike a `std::deque`. It also adds back support for Ctrl-S being an alias for VK_PAUSE which was lost in commit fccc741 in 2018. Closes #809 ## Validation Steps Performed * Unit and feature tests are  * Ctrl-S pauses output 🎉

Git stats

Files

Failed to load latest commit information.

README.md

terminal-logos

Welcome to the Windows Terminal, Console and Command-Line repo

This repository contains the source code for:

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

Related repositories include:

Installing and running Windows Terminal

Note : Windows Terminal requires Windows 10 2004 (build 19041) or later

Microsoft Store [Recommended]

Install the Windows Terminal from the Microsoft Store. This allows you to always be on the latest version when we release new builds with automatic upgrades.

This is our preferred method.

For users who are unable to install Windows Terminal from the Microsoft Store, released builds can be manually downloaded from this repository’s Releases page.

Download the Microsoft.WindowsTerminal_.msixbundle file from the Assets section. To install the app, you can simply double-click on the .msixbundle file, and the app installer should automatically run. If that fails for any reason, you can try the following command at a PowerShell prompt:

# NOTE: If you are using PowerShell 7+, please run # Import-Module Appx -UseWindowsPowerShell # before using Add-AppxPackage. Add-AppxPackage Microsoft.WindowsTerminal_versionNumber>.msixbundle
  • You may need to install the VC++ v14 Desktop Framework Package.
    This should only be necessary on older builds of Windows 10 and only if you get an error about missing framework packages.
  • Terminal will not auto-update when new builds are released so you will need to regularly install the latest Terminal release to receive all the latest fixes and improvements!

Via Windows Package Manager CLI (aka winget)

winget users can download and install the latest Terminal release by installing the Microsoft.WindowsTerminal package:

winget install --id Microsoft.WindowsTerminal -e

Via Chocolatey (unofficial)

Chocolatey users can download and install the latest Terminal release by installing the microsoft-windows-terminal package:

choco install microsoft-windows-terminal

To upgrade Windows Terminal using Chocolatey, run the following:

choco upgrade microsoft-windows-terminal

If you have any issues when installing/upgrading the package please go to the Windows Terminal package page and follow the Chocolatey triage process

Scoop users can download and install the latest Terminal release by installing the windows-terminal package:

scoop bucket add extras scoop install windows-terminal

To update Windows Terminal using Scoop, run the following:

scoop update windows-terminal

If you have any issues when installing/updating the package, please search for or report the same on the issues page of Scoop Extras bucket repository.

The plan for the Windows Terminal is described here and will be updated as the project proceeds.

Terminal & Console Overview

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

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, conhost.exe , is Windows’ original command-line user experience. It also hosts Windows’ command-line infrastructure and the Windows Console API server, input engine, rendering engine, user preferences, etc. The console host code in this repository is the actual source from which the conhost.exe in Windows itself is built.

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

However, because Windows Console’s primary goal is to maintain backward compatibility, we have been unable to add many of the features the community (and the team) have been wanting for the last several years including tabs, unicode text, and emoji.

These limitations led us to create the new Windows Terminal.

You can read more about the evolution of the command-line in general, and the Windows command-line specifically in this accompanying series of blog posts on the Command-Line team’s blog.

While overhauling Windows Console, we modernized its codebase considerably, cleanly separating 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 Windows Implementation Libraries — WIL.

This overhaul resulted in several of Console’s key components being available for re-use in any terminal implementation on Windows. These components include a new DirectWrite-based text layout and rendering engine, a text buffer capable of storing both UTF-16 and UTF-8, a VT parser/emitter, and more.

Creating the new Windows Terminal

When we started planning the new Windows Terminal application, we explored and evaluated several approaches and technology stacks. We ultimately decided that our goals would be best met by continuing our investment in our C++ codebase, which would allow us to reuse several of the aforementioned modernized components in both the existing Console and the new Terminal. Further, we realized that this would allow us to build much of the Terminal’s core itself as a reusable UI control that others can incorporate into their own applications.

The result of this work is contained within this repo and delivered as the Windows Terminal application you can download from the Microsoft Store, or directly from this repo’s releases.

For more information about Windows Terminal, you may find some of these resources useful and interesting:

  • Command-Line Blog
  • Command-Line Backgrounder Blog Series
  • Windows Terminal Launch: Terminal «Sizzle Video»
  • Windows Terminal Launch: Build 2019 Session
  • Run As Radio: Show 645 — Windows Terminal with Richard Turner
  • Azure Devops Podcast: Episode 54 — Kayla Cinnamon and Rich Turner on DevOps on the Windows Terminal
  • Microsoft Ignite 2019 Session: The Modern Windows Command Line: Windows Terminal — BRK3321

I built and ran the new Terminal, but it looks just like the old console

Cause: You’re launching the incorrect solution in Visual Studio.

Solution: Make sure you’re building & deploying the CascadiaPackage project in Visual Studio.

Note : OpenConsole.exe is just a locally-built conhost.exe , the classic Windows Console that hosts Windows’ command-line infrastructure. OpenConsole is used by Windows Terminal to connect to and communicate with command-line applications (via ConPty).

All project documentation is located at aka.ms/terminal-docs. If you would like to contribute to the documentation, please submit a pull request on the Windows Terminal Documentation repo.

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

BEFORE you start work on a feature/fix, please read & follow our Contributor’s Guide to help avoid any wasted or duplicate effort.

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 preexisting issues before creating a new issue.

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

  • Kayla Cinnamon, Program Manager: @cinnamon_msft
  • Dustin Howett, Engineering Lead: @dhowett
  • Mike Griese, Senior Developer: @zadjii
  • Carlos Zamora, Developer: @cazamor_msft
  • Pankaj Bhojwani, Developer
  • Leonard Hecker, Developer: @LeonardHecker
Оцените статью
Adblock
detector