ArchiveorgSoftwareThe new Windows Terminal and the original Windows console host, all in the same place! This repository contains the source code for:Related repositories include:Installing and running Windows Terminal 🔴 Note: Windows Terminal requires Windows 10 1903 (build 18362) or laterMicrosoft Store [Recommended]Install the Windows Terminal from the Microsoft Store[1].This allows you to always be on the latest version when we release new buildswith automatic upgrades.This is our preferred method.Other install methodsVia GitHubFor users who are unable to install Windows Terminal from the Microsoft Store,released builds can be manually downloaded from this repository's Releasespage[2].Download the Microsoft.WindowsTerminal_.msixbundle file fromthe Assets section. To install the app, you can simply double-click on the.msixbundle file, and the app installer should automatically run. If thatfails for any reason, you can try the following command at a PowerShell prompt:```powershellAdd-AppxPackage Microsoft.WindowsTerminal_.msixbundle``` 🔴 Note: If you install Terminal manually: 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[3] users can download and installthe latest Terminal release by installing the Microsoft.WindowsTerminalpackage:powershellwinget install --id=Microsoft.WindowsTerminal -eVia Chocolatey (unofficial)Chocolatey[4] users can download and install the latestTerminal release by installing the microsoft-windows-terminal package:powershellchoco install microsoft-windows-terminalTo upgrade Windows Terminal using Chocolatey, run the following:powershellchoco upgrade microsoft-windows-terminalIf you have any issues when installing/upgrading the package please go to theWindows Terminal packagepage and follow theChocolatey triage process[5][6]Via Scoop (unofficial)Scoop[7] users can download and install the latest Terminalrelease by installing the windows-terminal package:powershellscoop bucket add extrasscoop install windows-terminalTo update Windows Terminal using Scoop, run the following:powershellscoop update windows-terminalIf you have any issues when installing/updating the package, please search foror report the same on the issuespage[8] of Scoop Extras bucketrepository.Windows Terminal 2.0 RoadmapThe plan for delivering Windows Terminal 2.0 is describedhere[9] and will be updated as the project proceeds.Project Build StatusProject|Build Status---|---Terminal| ColorTool| Terminal & Console OverviewPlease take a few minutes to review the overview below before diving into thecode:Windows TerminalWindows Terminal is a new, modern, feature-rich, productive terminal applicationfor command-line users. It includes many of the features most frequentlyrequested by the Windows command-line community including support for tabs, richtext, globalization, configurability, theming & styling, and more.The Terminal will also need to meet our goals and measures to ensure it remainsfast and efficient, and doesn't consume vast amounts of memory or power.The Windows Console HostThe Windows Console host, conhost.exe, is Windows' original command-line userexperience. It also hosts Windows' command-line infrastructure and the WindowsConsole API server, input engine, rendering engine, user preferences, etc. Theconsole host code in this repository is the actual source from which theconhost.exe in Windows itself is built.Since taking ownership of the Windows command-line in 2014, the team addedseveral new features to the Console, including background transparency,line-based selection, support for ANSI / Virtual Terminalsequences[10], 24-bitcolor[11],a Pseudoconsole("ConPTY")[12],and more.However, because Windows Console's primary goal is to maintain backwardcompatibility, 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[13] on the Command-Line team's blog.Shared ComponentsWhile overhauling Windows Console, we modernized its codebase considerably,cleanly separating logical entities into modules and classes, introduced somekey extensibility points, replaced several old, home-grown collections andcontainers with safer, more efficient STLcontainers[14],and made the code simpler and safer by using Microsoft's Windows ImplementationLibraries - WIL[15].This overhaul resulted in several of Console's key components being availablefor re-use in any terminal implementation on Windows. These components include anew DirectWrite-based text layout and rendering engine, a text buffer capable ofstoring both UTF-16 and UTF-8, a VT parser/emitter, and more.Creating the new Windows TerminalWhen we started planning the new Windows Terminal application, we explored andevaluated several approaches and technology stacks. We ultimately decided thatour goals would be best met by continuing our investment in our C++ codebase,which would allow us to reuse several of the aforementioned modernizedcomponents in both the existing Console and the new Terminal. Further, werealized that this would allow us to build much of the Terminal's core itself asa reusable UI control that others can incorporate into their own applications.The result of this work is contained within this repo and delivered as theWindows Terminal application you can download from the Microsoft Store, ordirectly from this repo'sreleases[16].ResourcesFor more information about Windows Terminal, you may find some of theseresources useful and interesting:FAQI built and ran the new Terminal, but it looks just like the old consoleCause: You're launching the incorrect solution in Visual Studio.Solution: Make sure you're building & deploying the CascadiaPackage project inVisual 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[17]).DocumentationAll project documentation is located at[18]. If you would liketo contribute to the documentation, please submit a pull request on the WindowsTerminal Documentation repo[19].ContributingWe are excited to work alongside you, our amazing community, to build andenhance Windows Terminal!BEFORE you start work on a feature/fix, please read & follow ourContributor'sGuide[20] tohelp avoid any wasted or duplicate effort.Communicating with the TeamThe easiest way to communicate with the team is via GitHub issues.Please file new issues, feature requests and suggestions, but DO search forsimilar open/closed pre-existing 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:Developer GuidancePrerequisitesBuilding the CodeThis repository uses gitsubmodules[21] for some of itsdependencies. To make sure submodules are restored or updated, be sure to runthe following prior to building:shellgit submodule update --init --recursiveOpenConsole.sln may be built from within Visual Studio or from the command-lineusing a set of convenience scripts & tools in the /tools directory:Building in PowerShellpowershellImport-Module .\tools\OpenConsole.psm1Set-MsBuildDevEnvironmentInvoke-OpenConsoleBuildBuilding in Cmdshell.\tools\razzle.cmdbczRunning & DebuggingTo debug the Windows Terminal in VS, right click on CascadiaPackage (in theSolution Explorer) and go to properties. In the Debug menu, change "Applicationprocess" and "Background task process" to "Native Only".You should then be able to build & debug the Terminal project by hittingF5. 👉 You will not be able to launch the Terminal directly by running the WindowsTerminal.exe. For more details on why, see #926, #4043[22][23]Coding GuidancePlease review these brief docs below about our coding practices. 👉 If you find something missing from these docs, feel free to contribute to any of our documentation files anywhere in the repository (or write some new ones!)This is a work in progress as we learn what we'll need to provide people inorder to be effective contributors to our project.Code of ConductThis project has adopted the Microsoft Open Source Code ofConduct[24]. For more information see the Code of ConductFAQ[25] or contact Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein![26] with anyadditional questions or comments. To restore the repository download the bundle wget and run: git clone microsoft-terminal_-_2021-07-17_23-16-33.bundle Source:[27]Uploader: microsoft[28]Upload date: 2021-07-17 References^ Windows Terminal from the Microsoft Store (^ Releasespage (^ winget (^ Chocolatey (^ Windows Terminal packagepage (^ Chocolatey triage process (^ Scoop (^ issuespage (^ is describedhere (^ ANSI / Virtual Terminalsequences (^ 24-bitcolor (^ Pseudoconsole("ConPTY") (^ this accompanying series of blog posts (^ STLcontainers (^ Windows ImplementationLibraries - WIL (^ directly from this repo'sreleases (^ ConPty (^ (^ WindowsTerminal Documentation repo (^ Contributor'sGuide (^ gitsubmodules (^ #926 (^ #4043 (^ Microsoft Open Source Code ofConduct (^ Code of ConductFAQ (^ Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein! (^ (^ microsoft (

weiterlesen: RSS Quelle öffnen