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

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

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 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.

Other install methods

Via GitHub

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

🔴 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 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

Via Scoop (unofficial)

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.


Windows Terminal 2.0 Roadmap

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

Project Build Status

Project Build Status
Terminal Terminal Build Status
ColorTool Colortool Build Status

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 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.

Shared Components

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.


Resources

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


FAQ

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).


Documentation

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.


Contributing

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 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 Guidance

Prerequisites

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 a set of convenience scripts & tools in the /tools directory:

Building in PowerShell

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

Building in Cmd

.\tools\razzle.cmd
bcz

Running & Debugging

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

You should then be able to build & debug the Terminal project by hitting F5.

👉 You will not be able to launch the Terminal directly by running the WindowsTerminal.exe. For more details on why, see #926, #4043

Coding Guidance

Please 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 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 [email protected] with any additional questions or comments.

Owner
Microsoft
Open source projects and samples from Microsoft
Microsoft
Comments
  • Guide for build and installation

    Guide for build and installation

    Tools needed

    1. VS2017 or higher with the following packages ("Workloads" tab in Visual Studio Installer) : 1.1 Desktop Development with C++. 1.2 Universal Windows Platform Development. 1.3 Windows 10 SDK (10.0.18362.0). 1.4 If you're running VS2019, you'll also need to install either v141 Toolset or v142 Toolset.
    2. Git command-line tool.
    3. Nuget.exe (Needed in build step 3, can be found in Terminal/dep/nuget).

    Build Steps

    1. git clone this repository, not download .zip file.
    2. Run git submodule update --init --recursive in Terminal folder.
    3. Run nuget restore OpenConsole.sln (This step can be skipped, then Visual Studio should warn you that there are packages to restore - then restore).
    4. Open OpenConsole.sln with Visual Studio.
    5. Build whole solution(F7) with your platform(x86/x64) and release mode, you may need to fix some build errors: 5.1 C2220 and code page warnings: All errors and warnings are encoding error of unicode characters, a helpful workaround is to modify corresponding file encoding to UTF-8 BOM (Notepad++ is recommended). 5.2 Errors in src/tools/vtpipeterm/main.cpp: In addtion, you should also add u8 prefix before string literals with unicode characters, e.g. line 395, 398, 401 and 404.

    Workaround

    Try build with PR 458 or PR 549, both of them can build successfully.

    Installation

    Unfortunately, the generated .appx doesn't have any certificates, so it cannot be installed via double-click or powershell, the only way to install is to deploy the solution in VS.

    1. Open Windows Settings - Upgrade & Security - For Developers, switch App sources to Developer mode.
    2. Right click on CascadiaPackage project (under Solution/Terminal), select Deploy Solution to install, then you'll find Windows Terminal (Preview) in start menu.

    Settings

    After open the terminal, you can't see any menu buttons.

    Just press Ctrl + T to open a new tab, and you'll see a drop-down button in the tab bar.

    Click it and select Settings, then you can modify the configuration via opened profiles.json.

    Add WSL

    1. Create a new session in profiles, with content copied from profiles/cmd.
    2. Give it a new guid.
    3. Give it a new name, such as WSL.
    4. Specify its commandline to wsl.exe.

    Then you'll find WSL in the drop-down menu of tab bar.

    Here're sample codes:

    {
        "guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",
        "name": "WSL",
        "colorscheme": "Campbell",
        "historySize": 9001,
        "snapOnInput": true,
        "cursorColor": "#FFFFFF",
        "cursorShape": "bar",
        "commandline": "wsl.exe",
        "fontFace": "Consolas",
        "fontSize": 12,
        "acrylicOpacity": 0.75,
        "useAcrylic": true,
        "closeOnExit": false,
        "padding": "0, 0, 0, 0"
    }
    
  • Add

    Add "open Windows terminal here" into right-click context menu

    Add "open Windows terminal here" to right-click context menu?

    We know that, for windows 7, by default when we click "shift + right click with mouse" when we enter into a folder without selecting anything, we can see the option "open command window here".

    image

    While for windows 10, by default when we click "shift + right click with mouse", we can see the option "open powershell window here".

    So for Windows 10 (version later than 1903), how can we make the following three options available in right-click context menu?

    • open command window here
    • open powershell window here
    • open Windows terminal here

    Looking forward to your reply, thanks a lot~

  • [Question] Configuring Windows Terminal profile to always launch elevated

    [Question] Configuring Windows Terminal profile to always launch elevated

    Hi! Is there a way to configure a profile so that the commandLine it launches always starts with elevated (admin) permissions?

    Currently, you can launch the entire application as Administrator, but then every single commandLine runs as Administrator, which is not ideal.

  • Feature request: hot key drop down ala quake/guake/tilda

    Feature request: hot key drop down ala quake/guake/tilda

    The petty thing I miss most when I pop into Windows is having a separate hot key terminal for each of my three monitors. The closest i've ever been to believing in god was when I realized that was obtainable and if you could make that happen in Windows I just might have to kiss you.

  • AltGR SEQUENCES DO NOT WORK -- Can't type any AltGr combinations in Windows Terminal

    AltGR SEQUENCES DO NOT WORK -- Can't type any AltGr combinations in Windows Terminal

    Your Windows build number: 10.0.18362.86

    What you're doing and what's happening: Trying to enter the @ sign on a Swedish keyboard in a PowerShell console using Alt Gr + 2.
    See animated gif:

    terminal

    What's wrong / what should be happening instead: Windows terminal shows digit-argument instead of outputting the @ sign as expected.

    It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓

  • No keyboard input

    No keyboard input

    You may experience an issue with Windows Terminal where keyboard input does not work. By and large, we've determined that this is caused by the "Touch Keyboard and Handwriting Service" being disabled.

    If you're hitting this issue, make sure that the "Touch Keyboard and Handwriting Service" is not disabled. Certain "de-bloating" software (and apparently MSI Afterburner) likes to disable it or suppress it in the name of making your machine less understandable and "faster".

    If you're experiencing an input issue that is not helped by exiting MSI Afterburner or re-enabling the "Touch Keyboard and Handwriting Service", please file a new issue.

    Original issue content Latest version of Windows Terminal.

    Tried clean installing multiple times, keyboard input works on everything else (as I am typing with it here ...) yes that includes powershell.exe and cmd.exe.

    What gives?

  • Feature Request: Standard Opacity options like the traditional console.

    Feature Request: Standard Opacity options like the traditional console.

    Perhaps I overlooked it browsing through the json file but i didn't see another means to achieve transparency and i'm not a fan of the acrylic effects blurring factor or the fact that it turns off when the window is not selected. The traditional console provides for a static opacity just like in most nix envs, i'd hope it's just a matter of time before it's implemented here?

  • [Conpty] Add support for mouse input

    [Conpty] Add support for mouse input

    On: Microsoft Windows [Version 10.0.17763.134]

    I have implemented conpty in my terminal emulator: https://github.com/wez/wezterm

    I can successfully run target\debug\wezterm.exe to spawn console applications such as cmd.exe powershell.exe and bash.

    The issue I'm seeing is that when I launch bash, either indirectly via cmd.exe or directly via the bash launcher, conpty seems to swallow the mouse reporting escape sequences; I don't see them being received by my terminal parser, and thus vim has no effective mouse support despite being configured with set mouse=a.

    Running the same WSL install via wsl-terminal does have working mouse support, and wezterm has been my daily driver on Linux for about a year with working mouse support, so we can rule out an obvious misconfiguration with vim and the parser in wezterm.

    I've also tried echo -e "\e[?1000h" to manually enable mouse reporting from the shell; normally (on linux and via wsl-terminal) this causes clicks in the terminal to send data to the shell (which appears as garbage input), but when running my terminal with conpty, these are also swallowed up somewhere.

    Is there something special needed for the apps that I spawn into my pty to be able to work with the mouse?

    In case you want to double check the key portion of the code, the relevant file is: https://github.com/wez/wezterm/blob/master/src/winpty.rs The flow is to CreatePipe a pair of pipes, CreatePseudoConsole, and then pass that to a spawned child via the threadproc attributes, as the samples in the MSDN docs and this repo also do.

  • Terminal hangs when opening new windows or new tabs on Windows Server 2022

    Terminal hangs when opening new windows or new tabs on Windows Server 2022

    After installing either Terminal 1.10 or Terminal Preview 1.11 (after its dependencies and winget), opening it the first time (or subsequent times) causes the window to hang indefinitely (the process shows as 'Not Responding' in Task Manager). A similar problem happens when clicking the + to open a new tab.

    The problem happens regardless if the default terminal is either Powershell or others (like Command Prompt).

    A partial workaround is to launch a second copy of the app while the instance is hung, then use Task Manager to kill the hung app. Once the hung process closes, the application opens as expected. The workaround does not address the new tab problem, but just the initial window opening.

    If there is any logging or debug that can be enabled, please let me know.

  • Changing Ubuntu WSL starting directory keeps it set to the defualt

    Changing Ubuntu WSL starting directory keeps it set to the defualt

    When editing the the settings, I have tried to chang the default starting directory for the Ubuntu WSL Terminal profile as follows "startingDirectory": "/mnt/D/Folder/SubFolder/", and while it doesnt cause any issues or causes the Terminal to resort to default configuration, it does not set the default starting directory to the specified path.

    Also it seems that most settings for the profile do literally nothing when changing them, from color, to acrylic or scheme settings.

    Note: changing the setting for power shell, cmd, of Kali-Linux does work and change things respectively

  • MEGATHREAD: Breaking settings changes in version 0.11!

    MEGATHREAD: Breaking settings changes in version 0.11!

    BREAKING SETTINGS CHANGES IN 0.11

    • BREAKING CHANGE We've deleted a lot of legacy settings handling (#5190)
      • Please see our blog post and our most recent status update for more information.
      • If you had settings hanging out in the globals dictionary, you'll want to move them out.
        • REMEDIATION: move everything from globals to the root of your settings file and delete the empty globals object.
        • Failure to do so will cause us to ignore your default profile, launch mode, etc., etc.
        • THIS INCLUDES defaultProfile
      • requestedTheme has been renamed to theme (#5265)
    • profiles.json has been renamed to settings.json. This should be transparent to you as we'll rename it on first launch (#5199)
      • As a side effect, we'll finally stop resurrecting old pre-version-0.3 roaming profiles.
    • If you don't specify a splitPane split mode, it'll default to automatic (#5194)
    • copy's original and poorly-understood trimWhitespace argument is now called singleLine to indicate that it will, in fact, copy text as a single line (#5216)
    • The default font for any profiles that don't specify a font is now Cascadia Mono (#5121)

    Do your settings look like this?

    {
        "globals": {
            "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
            "initialCols": 200,
            "initialRows": 65,
            "initialPosition": "0,0",
            "wordDelimiters" : " ()\"'-:,;<>[email protected]#$%^&*|+=[]{}~?\u2502",
            "confirmCloseAllTabs": true,
            "keybindings": [
                ...
            ]
        },
        "profiles": {
            ...
        }
    }
    

    Then change them to look like this:

    {
        "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
        "initialCols": 200,
        "initialRows": 65,
        "initialPosition": "0,0",
        "wordDelimiters" : " ()\"'-:,;<>[email protected]#$%^&*|+=[]{}~?\u2502",
        "confirmCloseAllTabs": true,
        "keybindings": [
            ...
        ],
        "profiles": {
            ...
        }
    }
    

    Or even better, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.

  • Capability to set a alternative default profile when launchen the terminal over the windows explorer context menu

    Capability to set a alternative default profile when launchen the terminal over the windows explorer context menu

    Description of the new feature/enhancement

    At the moment we can specify the default profile when the windows terminal is getting started. Under Windows 11 I miss the option, to specify which profile should be getting used when i start the terminal over the windows explorer context menu.

    At least in my setup i´m normaly using WSL so thats my standard profile. But when I´m starting the terminal over the context menu, i want to use cmd. Of course i can manually open the cmd but then i´m losing the directory context and have to manually cd into the right path.

    I would love to see an option where i can specifiy, which profile should be used when the terminal is getting started over the explorer context menu.

    Proposed technical implementation details (optional)

    Maybe a second dropdown in the settings?

  • Dynamically generate profiles from hosts in OpenSSH config files

    Dynamically generate profiles from hosts in OpenSSH config files

    Summary of the Pull Request

    This PR looks for the presence of OpenSSH config files and creates profiles from the hosts present.

    References

    Closes #9031

    PR Checklist

    • [x] Closes #xxx
    • [x] CLA signed. If not, go over here and sign the CLA
    • [ ] Tests added/passed
    • [ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
    • [ ] Schema updated.
    • [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

    Detailed Description of the Pull Request / Additional comments

    Validation Steps Performed

    Installed OpenSSH, configured host for alt.org NetHack server, connected and played some NetHack from the created profile.

  • Fix potential lags/deadlocks during tab close

    Fix potential lags/deadlocks during tab close

    ConptyClosePseudoConsole blocks until OpenConsole exits. This is problematic for the changes in 666c446, which stopped calling that function on a background thread to solve a race condition. This commit fixes the potential lags/deadlocks from waiting on OpenConsole's exit, by adding ConptyClosePseudoConsoleNoWait which only closes the IO handles and allows OpenConsole to exit naturally. This uncovered another potential deadlock in ServiceLocator::RundownAndExit which might call itself recursively.

    Closes #14032

    Validation Steps Performed

    • Print tons of text and concurrently close the tab. Tab closes, OpenConsole/pwsh exits instantly ✅
    • Use Enter-VsDevShell and close the tab. Tab closes instantly, OpenConsole/pwsh exits after ~5 seconds ✅
  • Fix font size rounding in the settings UI

    Fix font size rounding in the settings UI

    This fixes an issue with c51bb3a, where some fractional font sizes are displayed as something like 13.600000000001.

    Closes #14024

    Validation Steps Performed

    • Enter a font size of 13.6 and save
    • NumberBox displays "13.6" ✅
  • AtlasEngine: Fix uneven baselines when scaling glyphs

    AtlasEngine: Fix uneven baselines when scaling glyphs

    This commit changes the glyph scale algorithm to prefer aligning glyphs to their baseline. This improves the visual appearance of simulated italic glyphs. However wide Emojis in narrow cells now look slightly worse without centering.

    Closes #13987

    Validation Steps Performed

    • Use FiraCode which has no italic variant and instead uses simulated italics
    • Write italic text
    • Baseline is consistent ✅
  • AtlasEngine: Fix cursor invalidation

    AtlasEngine: Fix cursor invalidation

    There's a different behavior regarding cursors between conhost and Windows Terminal. In case of the latter we don't necessarily call PaintCursor during cursor movement, because the cursor blinker never stops "blinking".

    Closes #14028

    Validation Steps Performed

    • Enter text until after the line wraps
    • Hold backspace until the line unwraps
    • No leftover cursor on the second line ✅
Spitfire is a basic terminal language that can exicute code via the terminal.

Spitfire is a basic terminal language that can exicute code via the terminal. It is easy to learn and runs fast, considering that its just a 300 line c++ file.

Nov 18, 2021
Free open-source modern C++17 / C++20 framework to create console, forms (GUI like WinForms) and unit test applications on Microsoft Windows, Apple macOS and Linux.
Free open-source modern C++17 / C++20 framework to create console, forms (GUI like WinForms) and unit test applications on Microsoft Windows, Apple macOS and Linux.

xtd Modern C++17/20 framework to create console (CLI), forms (GUI like WinForms) and tunit (unit tests like Microsoft Unit Testing Framework) applicat

Sep 25, 2022
EAMain provides a multi-platform entry point used for platforms that don't support console output, return codes and command-line arguments.

EAMain provides a multi-platform entry point used for platforms that don't support console output, return codes and command-line arguments.

Aug 23, 2022
FastReport.Cloud console tool for Linux and perhaps some other OSes

FastReport Cloud console shell This is a simple console shell to FastReport Cloud service. Prerequests GNU packages for build shell: curl-development

Feb 10, 2022
Run commands with hidden console.
Run commands with hidden console.

Minimal run This is a tiny C program for running Windows commands with a hidden console. It's suitable for use in Windows shortcuts, i.e. lnk files. I

May 30, 2022
cpp-progressbar is a small console program I wrote in c++. 3 themes are available
cpp-progressbar is a small console program I wrote in c++. 3 themes are available

cpp-progressbar cpp-progressbar is a small console program I wrote in c++. 3 themes are available (this program only works on linux) Instalation Downl

Jun 17, 2022
A C++ console tool to tracker baby actions.

BabyTracker This is a C++ console tool to tracker baby actions. Currently it supports adding Sleep Sessions Breast Feed Sessions Bottle Feed Sessions

Oct 17, 2021
Terminal calculator made for programmers working with multiple number representations, sizes, and overall close to the bits
Terminal calculator made for programmers working with multiple number representations, sizes, and overall close to the bits

Programmer calculator The programmer calculator is a simple terminal tool designed to give maximum efficiency and flexibility to the programmer workin

Sep 8, 2022
A C, C++ and Rust library to draw graphics with pixels in the terminal
A C, C++ and Rust library to draw graphics with pixels in the terminal

A library to draw graphics with pixels in the terminal Who needs a GUI when you have a terminal ? Building To generate libpluto.a, run: $ make To ins

Sep 3, 2022
timg - Terminal Image and Video Viewer
 timg - Terminal Image and Video Viewer

timg - Terminal Image and Video Viewer

Sep 20, 2022
Small header only C++ library for writing multiplatform terminal applications

Terminal Terminal is small header only library for writing terminal applications. It works on Linux, macOS and Windows (in the native cmd.exe console)

Sep 22, 2022
:computer: C++ Functional Terminal User Interface. :heart:
:computer: C++ Functional Terminal User Interface. :heart:

FTXUI Functional Terminal (X) User interface A simple C++ library for terminal based user interface. Demo: Feature Functional style. Inspired by [1] a

Sep 16, 2022
A little UNIX-inspired terminal application for the Numworks Calculator (not using escher).
A little UNIX-inspired terminal application for the Numworks Calculator (not using escher).

L.E. Terminal (let for short) is a little UNIX-inspired terminal for the Numworks Calculator.

Aug 31, 2022
Draw sequence diagram in text from terminal.

sequence-diagram-cli Draw seqence diagram from terminal.

Aug 4, 2022
X terminal emulator rendering through OpenGL ES Compute Shaders

Zutty is a terminal emulator for the X Window System, functionally similar to several other X terminal emulators such as xterm, rxvt and countless others

Sep 20, 2022
n³ The unorthodox terminal file manager
n³ The unorthodox terminal file manager

n³ The unorthodox terminal file manager

Sep 18, 2022
Graphs the activity of a chia harvester in a linux terminal.
Graphs the activity of a chia harvester in a linux terminal.

Chia Harvest Graph Monitor for Chia Harvesting Introduction The chiaharvestgraph tool will graph Chia Harvesting activity in a linux terminal. Use a 2

Sep 21, 2022
a simple to use linux terminal

a simple to use linux terminal

Feb 17, 2022
Collection of human friendly terminal interface for git.
Collection of human friendly terminal interface for git.

A collection of human friendly terminal user interface for git.

Sep 17, 2022