devblogs.microsoft.com
Open in
urlscan Pro
2a02:26f0:7100:9ac::2f1e
Public Scan
Submitted URL: https://go.microsoft.com/fwlink/?linkid=2028595
Effective URL: https://devblogs.microsoft.com/commandline/new-experimental-console-features/
Submission: On December 23 via manual from CH — Scanned from CH
Effective URL: https://devblogs.microsoft.com/commandline/new-experimental-console-features/
Submission: On December 23 via manual from CH — Scanned from CH
Form analysis 5 forms found in the DOM
Name: searchForm — GET /search
<form class="c-search" autocomplete="off" id="searchForm" name="searchForm" role="search" action="/search" method="GET" data-seautosuggest="" data-seautosuggestapi="https://www.microsoft.com/msstoreapiprod/api/autosuggest"
data-m="{"cN":"GlobalNav_Search_cont","cT":"Container","id":"c1c9c3m1r1a1","sN":1,"aN":"c9c3m1r1a1"}" aria-expanded="false">
<input id="cli_shellHeaderSearchInput" aria-label="Search" aria-expanded="false" aria-controls="universal-header-search-auto-suggest-transparent" aria-owns="universal-header-search-auto-suggest-ul" type="search" name="query" placeholder="Search"
data-m="{"cN":"SearchBox_nav","id":"n1c1c9c3m1r1a1","sN":1,"aN":"c1c9c3m1r1a1"}" data-toggle="tooltip" data-placement="right" data-bs-original-title="Search">
<button id="search" aria-label="Search" class="c-glyph" data-m="{"cN":"Search_nav","id":"n2c1c9c3m1r1a1","sN":2,"aN":"c1c9c3m1r1a1"}" data-bi-mto="true" aria-expanded="false"
disabled="disabled">
<span role="presentation">Search</span>
<span role="tooltip" class="c-uhf-tooltip c-uhf-search-tooltip">Search</span>
</button>
<div class="m-auto-suggest" id="universal-header-search-auto-suggest-transparent" role="group">
<ul class="c-menu" id="universal-header-search-auto-suggest-ul" aria-label="Search Suggestions" aria-hidden="true" data-bi-dnt="true" data-bi-mto="true" data-js-auto-suggest-position="default" role="listbox" data-tel="jsll"
data-m="{"cN":"search suggestions_cont","cT":"Container","id":"c3c1c9c3m1r1a1","sN":3,"aN":"c1c9c3m1r1a1"}"></ul>
<ul class="c-menu f-auto-suggest-no-results" aria-hidden="true" data-js-auto-suggest-postion="default" data-js-auto-suggest-position="default" role="listbox">
<li class="c-menu-item"> <span tabindex="-1">No results</span></li>
</ul>
</div>
<input type="hidden" name="blog" value="/commandline/" data-m="{"cN":"HiddenInput_nav","id":"n2c1c9c3m1r1a1","sN":2,"aN":"c1c9c3m1r1a1"}" style="overflow-x: visible;"
aria-label="Search">
</form>POST https://devblogs.microsoft.com/commandline/wp-comments-post.php
<form method="post" action="https://devblogs.microsoft.com/commandline/wp-comments-post.php" id="commentform" class="wp-core-ui">
<div id="editor-container-0">
<div id="wp-comment_reply_content-wrap" class="wp-core-ui wp-editor-wrap html-active">
<div id="wp-comment_reply_content-editor-container" class="wp-editor-container">
<div id="qt_comment_reply_content_toolbar" class="quicktags-toolbar hide-if-no-js"><input type="button" id="qt_comment_reply_content_strong" class="ed_button button button-small" aria-label="Bold" value="b"><input type="button"
id="qt_comment_reply_content_em" class="ed_button button button-small" aria-label="Italic" value="i"><input type="button" id="qt_comment_reply_content_link" class="ed_button button button-small" aria-label="Insert link"
value="link"><input type="button" id="qt_comment_reply_content_del" class="ed_button button button-small" aria-label="Deleted text (strikethrough)" value="del"><input type="button" id="qt_comment_reply_content_customcode"
class="ed_button button button-small" value="code"></div><textarea class="wp-editor-area" style="height: 200px" cols="40" name="comment_reply_content" id="comment_reply_content" aria-label="textarea editor"></textarea>
</div>
</div>
<div class="vote">
<span class="form-submit">
<input name="submit" type="submit" id="submit" class="btn btn-primary" value="Reply">
<input type="button" value="Cancel" id="cancel-reply-comment-form" name="Cancel" class="btn btn-secondary">
<input type="hidden" name="comment_post_ID" value="4095" id="comment_post_ID">
<input type="hidden" name="comment_parent" id="comment_parent" value="0">
</span>
<span class="code-of-conduct"><a href="https://answers.microsoft.com/en-us/page/codeofconduct" target="_blank">Code of Conduct</a></span>
</div>
<input type="hidden" id="_wp_unfiltered_html_comment_disabled" name="_wp_unfiltered_html_comment" value="ad7af05511">
</div><!-- editor-container -->
</form>POST https://devblogs.microsoft.com/commandline?na=s
<form method="post" action="https://devblogs.microsoft.com/commandline?na=s" onsubmit="return newsletter_check(this)">
<input type="hidden" name="nlang" value="">
<div class="d-flex flex-row align-items-center gap-12 mb-12">
<div class="d-flex align-items-center justify-content-start flex-md-grow-1 bg-white" style="align-self: stretch; height: 32px; border-radius: 4px; overflow: hidden; border: 1px solid var(--clr-border); width: 90%;"> <input
class="x-hidden-focus bg-white" style="flex: 1 1 0; align-self: stretch; border: none; padding: 4px 10px; font-family: Segoe UI; color: var(--clr-body);" type="email" name="ne" aria-labelledby="stayInformed" placeholder="Enter your email"
required=""></div>
<div class="d-flex align-items-center justify-content-center">
<button class="tnp-submit btn-primary" type="submit" value="Subscribe">Subscribe</button>
</div>
</div>
<div class="tnp-privacy-field" style="font-size: 10px; line-height: 14px; word-wrap: break-word"><label>By subscribing you agree to our
<a style="color: var(--clr-body-link); text-decoration: underline;" href="https://docs.microsoft.com/en-us/collaborate/terms-of-use" target="_blank">Terms of Use</a> and
<a style="color: var(--clr-body-link); text-decoration: underline;" href="https://go.microsoft.com/fwlink/?LinkId=521839" target="_blank">Privacy</a></label></div>
</form><form id="wp-link" tabindex="-1">
<input type="hidden" id="_ajax_linking_nonce" name="_ajax_linking_nonce" value="0d13b1837d">
<h1 id="link-modal-title">Insert/edit link</h1>
<button type="button" id="wp-link-close"><span class="screen-reader-text"> Close </span></button>
<div id="link-selector">
<div id="link-options">
<p class="howto" id="wplink-enter-url">Enter the destination URL</p>
<div>
<label><span>URL</span>
<input id="wp-link-url" type="text" aria-describedby="wplink-enter-url"></label>
</div>
<div class="wp-link-text-field">
<label><span>Link Text</span>
<input id="wp-link-text" type="text"></label>
</div>
<div class="link-target">
<label><span></span>
<input type="checkbox" id="wp-link-target"> Open link in a new tab</label>
</div>
</div>
<p class="howto" id="wplink-link-existing-content">Or link to existing content</p>
<div id="search-panel">
<div class="link-search-wrapper">
<label>
<span class="search-label">Search</span>
<input type="search" id="wp-link-search" class="link-search-field" autocomplete="off" aria-describedby="wplink-link-existing-content">
<span class="spinner"></span>
</label>
</div>
<div id="search-results" class="query-results" tabindex="0">
<ul></ul>
<div class="river-waiting">
<span class="spinner"></span>
</div>
</div>
<div id="most-recent-results" class="query-results" tabindex="0">
<div class="query-notice" id="query-notice-message">
<em class="query-notice-default">No search term specified. Showing recent items.</em>
<em class="query-notice-hint screen-reader-text"> Search or use up and down arrow keys to select an item. </em>
</div>
<ul></ul>
<div class="river-waiting">
<span class="spinner"></span>
</div>
</div>
</div>
</div>
<div class="submitbox">
<div id="wp-link-cancel">
<button type="button" class="button">Cancel</button>
</div>
<div id="wp-link-update">
<input type="submit" value="Add Link" class="button button-primary" id="wp-link-submit" name="wp-link-submit">
</div>
</div>
</form>#
<form id="myForm" action="#">
<div class="modal-body">
<div class="form-group">
<label for="code-text">Paste your code snippet</label>
<textarea class="form-control" id="code-text" style="height: 150px;"></textarea>
</div>
</div>
<div class="modal-footer">
<button type="button" onclick="myCodeFunction()" class="btn btn-primary">Ok</button>
<button type="button" name="Cancel" onclick="myCodeCancelFunction()" class="btn btn-secondary" data-dismiss="modal">Cancel</button>
</div>
</form>Text Content
We use optional cookies to improve your experience on our websites, such as
through social media connections, and to display personalized advertising based
on your online activity. If you reject optional cookies, only cookies necessary
to provide you the services will be used. You may change your selection by
clicking “Manage Cookies” at the bottom of the page. Privacy Statement
Third-Party Cookies
Accept Reject Manage cookies
Skip to main content
Microsoft
Dev Blogs
Dev Blogs
Dev Blogs
* Home
* Developer
* Microsoft for Developers
* Visual Studio
* Visual Studio Code
* Develop from the cloud
* Visual Studio for Mac
* All things Azure
* DevOps
* Windows Developer
* Developer support
* ISE Developer
* Engineering@Microsoft
* Azure SDK
* Command Line
* Perf and Diagnostics
* React Native
* Technology
* AutoGen
* DirectX
* OpenAPI
* Semantic Kernel
* SurfaceDuo
* Windows AI Platform
* Languages
* C++
* C#
* F#
* TypeScript
* PowerShell Community
* PowerShell Team
* Python
* JavaScript
* Java
* Java Blog in Chinese
* Go
* .NET
* All .NET posts
* .NET Aspire
* .NET MAUI
* AI
* ASP.NET Core
* Blazor
* Entity Framework
* Servicing
* .NET Blog in Chinese
* Platform Development
* #ifdef Windows
* Azure Government
* Azure VM Runtime Team
* Bing Dev Center
* Microsoft Edge Dev
* Microsoft Azure
* Microsoft 365 Developer
* Microsoft Entra Identity Developer Blog
* Old New Thing
* Power Platform
* Windows MIDI and Music dev
* Data Development
* Azure Cosmos DB
* Azure Data Studio
* Azure SQL
* OData
* Revolutions R
* SQL Server Data Tools
* Unified Data Model (IDEAs)
* More
Theme
Sign in
Search Search
* No results
Cancel
* Dev Blogs
* Windows Command Line
* New Experimental Console Features
December 10th, 2018
NEW EXPERIMENTAL CONSOLE FEATURES
Rich Turner
Sr. Program Manager
TABLE OF CONTENTS
* Terminal Scrolling
* Disable Scroll Forward:
* Cursor Shape
* Cursor Colors
* Terminal Colors
* Karma Karma Karma Karma Console Chameleon
* Looking Back, Moving Forward
* Moving Forward
* Call To Action!
Show more
READ NEXT
February 15, 2019
WHAT’S NEW FOR WSL IN WINDOWS 10 VERSION 1903?
Craig Loewen
May 6, 2019
ANNOUNCING WSL 2
Craig Loewen
As of Windows 10 build 18298, when you open the properties page of any Console
window, you’ll notice an additional “Terminal” tab. Click on this tab and you’ll
see several new settings for some experimental features we’re working on for
future OS releases:
]2 Experimental settings in action
> Important Note: These settings are “experimental”, because in certain
> scenarios, it’s possible that they might not behave like you would expect them
> to, may not make it into the next OS release, and may change completely before
> we ship! But have fun with them anyway and let us know how you get on – we’d
> love to hear your feedback. Let’s outline each of the settings groups from the
> bottom up, ending with a more thorough discussion the Terminal Color settings:
TERMINAL SCROLLING COPY LINK
DISABLE SCROLL FORWARD: COPY LINK
* When cleared (default state), the Console can to scroll anywhere within the
Console’s buffer, even below the most recent row of text displayed When
checked, the Console will not allow scrolling below the last line output,
similar to how most *NIX terminals work
CURSOR SHAPE COPY LINK
Legacy Style: Thicker underscore by default, but controlled by the cursor size
property in the “Options” page
Underscore: Thinner underscore
Vertical Bar: For all you crazy kids who like your cursors tall and skinny
Empty Box: The second-best cursor:
Solid Box: The one true cursor
CURSOR COLORS COPY LINK
Inverse Color: The current and default behavior where the cursor color is the
calculated inverse of the background color … which results in, for example, this
adorable fetching pink against the bright green background of my first computer
– the Dragon 32
Use Color: Draw the cursor in a specific RGB color, like this fetching green
against dark gray background:
TERMINAL COLORS COPY LINK
The Terminal Colors fields allow you to specify specific RGB color values for
the default foreground and/or background colors. These colors are independent of
the color palette and are not affected by changes you make to your color
palette! But before we discuss the inherent implications here, we need to
consider how these new settings fit into the color changes we’ve been making
over the last several Windows 10 releases:
KARMA KARMA KARMA KARMA CONSOLE CHAMELEON COPY LINK
Over the last couple of years, during “The Grand Overhaul” of Windows Console,
we’ve made some significant improvements to Console’s parsing and handling of
ANSI/VT sequences, and how the Console stores and renders colored text.
This all started with a rewrite of the Console’s VT parser. Prior to the (then
new) team’s efforts, Windows Console barely supported any VT sequences at all.
But with the steady growth in adoption of *NIX-first open-source tools, many of
which emit VT sequences to color and draw text-based UI’s, it was increasingly
imperative that the Windows Console be able to support VT sequences.
]10 Before (XP) and after (Win10) VT support added to Console
This was made even more important and urgent due to the arrival of Windows
Subsystem for Linux which allowed unmodified Linux binaries to run natively on
Windows, allowing Windows users to easily run most of the *NIX tools they’d
previously had to fire-up in a separate VM.
The first significant version of the Console’s new VT engine shipped in Windows
10 1609 (Anniversary Update), and was quickly followed in the 1703 (Creators
Update) release which contained much richer support for a wider range of VT
sequences. This allowed Console to render many of even the most complex
text-based UI’s generated by tools like Tmux (a great tutorial here for the
uninitiated) and Midnight Commander … or even vim, bash, Midnight Commander and
htop running simultaneously in separate Tmux panes:
]14 TMux hosting vim, bash, Midnight Commander, and htop
Also in Creators Update, the Console shipped its massively improved color
support, increasing its color support from a mere 8-bit/16-colors (a single
8-bit value held both the foreground and background color 0-7 in the low and
high nybble respectively), to full 24-bit/16M-colors!
But we weren’t yet done! In the Fall Creators Update (Oct 2017), we updated the
Console’s default color palette for the first time … ever! After working with
Microsoft’s usability and accessibility teams, and following recommended color
selection guidelines, we arrived at a new color palette that is FAR better
suited to modern high-contrast displays.
In addition, we also shipped an open-source ColorTool which you can use to apply
different color palette’s to your Console windows if you wish.
So, we’re done with color support in the Console, right?
Nope!
LOOKING BACK, MOVING FORWARD COPY LINK
The Console now lives in two worlds:
1. 1. Windows – Console supports traditional/legacy command-line Windows apps
that call the Win32 Console APIs to color/manipulate text displayed on the
Console
2. ANSI/VT – Console also now supports apps that color/manipulate the text that
they display by embedding VT sequences within the text that they emit
Because of #2 above, Console has to support some of the different ways in which
VT compatible terminals think about the world.
A key difference between Windows Console and *NIX-based VT Terminals is that
*NIX Terminals have a notion of default foreground and background colors, which
are independent from the Terminal’s color palette. The Windows Console does not
… at least not quite the same!
Windows Console refers the “Screen Text” and “Screen Background” colors to the
colors defined in the Console’s palette:
]19 Console color settings
But Console has no notion of “default” foreground or background color to the
command-line apps that draw on the screen. At best, there’s an assumption that
color #0 is often the background color, and that #7 is the foreground, but this
is an often-incorrect assumption, not a widely-understood rule. In fact, Windows
command-line apps have no way of determining the default foreground and
background colors!!
For a good example of this, let’s explore Windows PowerShell: The Windows
PowerShell team wanted to differentiate PowerShell Consoles from Cmd Consoles by
changing the PowerShell Console’s default background color.
They specifically modified the PowerShell shortcuts’ settings:
* Re-defined color #5 as a specific shade of blue: RGB(1,36,86)
* Re-defined color #6 as a specific shade of gray: RGB(238,237,240)
However, they also decided to modify the shortcut’s background and foreground
color indexes to
* Color #5 as the background color (instead of the generally assumed color #0)
* Color #6 as the foreground color (instead of the generally assumed color #7)
Sometimes, PowerShell wants to, for example, “render this text in on whatever
the default background color is”.
Alas, because Windows Console has no API to discover what the “default
background color” is, PowerShell assumes that the background is the color
defined by color #0 … which usually IS the background color … except in
PowerShell which uses color #5
Thus, if you’ve ever mis-typed a command in Windows PowerShell, you’ve likely
seen something like this:
]20 PowerShell assumes the background color is #0
MOVING FORWARD COPY LINK
Alas, the changes we’re working on (and exposing via the experimental Terminal
settings page) won’t fix this specific issue for Windows PowerShell
Existing/legacy applications that specifically say “draw this text in on color
#0” will still draw text in some-foreground-color, on a (usually black/dark)
background, even if the Console’s default background color is bright green! In
some ways this is good;there will be no behavioral change for existing/legacy
apps. But the downside is that such apps will continue to render less than
optimal output (like in the PowerShell example above.
However, making Console aware of the notion of “default independent foreground
and background colors” will enable Console to more accurately render VT enriched
text-UI, and will give Console users more control over the customizability of
their Command-Line environment.
CALL TO ACTION! COPY LINK
This issue further amplifies the recommendation to start writing (or update
existing) Command-Line apps to emit VT enriched text, rather than calling Win32
Console APIs to control/format Console output: VT-enabled apps will not only
benefit from rendering improvements like those described above (with more on the
way), but they’ll also enjoy richer features available via VT-sequences, like
24-bit color support, and default foreground/background color support.
We look forward to hearing how you get-on with these experimental changes. If
you find issues with the color support, please find/file issues on our GitHub
issues repo, reach out and let @richturn_ms know on Twitter, and/or submit
feedback via the Feedback Hub.
6
29
0
* Share on Facebook
* Share on Twitter
* Share on Linkedin
Category
CmdCommand-LineLinux toolsWindows ConsoleWindows Subsystem for Linux (WSL)
Topics
ANSI/VT SequencescmdColorLinuxPowerShell
AUTHOR
Rich Turner
Sr. Program Manager
Geek, Nerd, Hacker. Fan of Rugby, Motorcycles, Skiing, Outdoor activities.
29 COMMENTS
Discussion is closed. Login to edit/delete existing comments.
Code of Conduct
Sort by :
Newest
Newest Popular Oldest
* Douglas Tondo June 6, 2020 1
Collapse this comment Copy link
Is there a way to allow a configuration that terminal blinks (in taskbar)
after a long command (more them 30 seconds) finish the execution?
Example of use: imagine that you are installing a big program that takes 3
minutes to download at least… I normally minimize the terminal and do other
stuffs… It would be good if the terminal blinks after the installation
finished ( allow user to type the next command )
Thanks!
* Rich Turner Author June 8, 2020 1
Collapse this comment Copy link
Hey Douglas. Since blog comments aren’t monitored as actively, and don’t
provide a good way of having a bidirectional conversation, I encourage you
to search the Terminal repo and file asks/issues if you don’t find any that
already describe your scenario: https://github.com/microsoft/terminal
* David Bollman March 12, 2020 2
Collapse this comment Copy link
Please allow some of the same functionality as putty, primarily the nearly
unlimited scroll up option. Limiting it to 999 is crazy small. Also the
default of 20000 would be my recommendation (similar to putty), it’s rare you
need to bump that (but it happens).
Also you really should have no limit either on the command history.
Finally you should not have a different copy paste mechanism in every
different cmd prompt, (powershell, linux window, cmd)…
* Rich Turner Author March 12, 2020 2
Collapse this comment Copy link
Thanks for sharing your thoughts David. Alas, we can only change Console so
much before we start to break people, so we're having to pretty much leave
it alone, except for essential maintencnace.
However, we're building a whole new, modern, fast, productive command-line
UX in Windows Terminal in which we're improving at a significant pace. You
can download the Terminal from the Windows Store, and/or clone the source
and report issues via its GitHub repo:
https://github.com/microsoft/terminal
Ultimately...
Read more
Thanks for sharing your thoughts David. Alas, we can only change Console so
much before we start to break people, so we’re having to pretty much leave
it alone, except for essential maintencnace.
However, we’re building a whole new, modern, fast, productive command-line
UX in Windows Terminal in which we’re improving at a significant pace. You
can download the Terminal from the Windows Store, and/or clone the source
and report issues via its GitHub repo:
https://github.com/microsoft/terminal
Ultimately what you’re asking for will be delivered when we get to the
“persistent sessions” collection of features that are currently in our
backlog. The idea here is to provide the ability to serialize
command-history to a file, providing for command-history that is only
limited in length by your PC’s storage capacity We’re also considering
enabling command output to be serialized to a file to enable restartable
sessions, though this presents some security/privacy concerns which need
very careful consideration.
We don’t currently offer a different copy & paste per-profile in Terminal,
through it has been requested because different shells use different key
sequences/chords for different operations. E.g. in Cmd & PowerShell, CTRL+C
== break, whereas many Linux distros default CTRL + SHIFT + C/V to copy and
paste because CTRL+C has specific behaviors in many Linux tools like EMACS.
Rest assured, we’ll provide a way for you to declare what key chords you
want to map to which operations (as we do today), but may consider allowing
you to override specific key chords on a per-profile basis if you want to.
Read less
* chris@cleanscape.net January 8, 2020 1
Collapse this comment Copy link
Overall, I think the new console is great! There's two things the
experimental console does "wrong". (NOTE: The editor on this site is weird,
it won't let me add numbers 1 and 2 to the two points below.)
Unlike the classic console, if you use "Discard Old Duplicates", the new one
is case-insensitive. Thus, if I run foo /v and then foo /V, only one of the
two is kept in the command history, despite the...
Read more
Overall, I think the new console is great! There’s two things the
experimental console does “wrong”. (NOTE: The editor on this site is weird,
it won’t let me add numbers 1 and 2 to the two points below.)
Unlike the classic console, if you use “Discard Old Duplicates”, the new one
is case-insensitive. Thus, if I run foo /v and then foo /V, only one of the
two is kept in the command history, despite the fact the case is significant
to foo!
You can’t bypass DOSkey macros by placing a space in front of them.
Who may I pass these issues on to? Thanks!
Read less
* Rich Turner Author January 9, 2020 1
Collapse this comment Copy link
Thanks for the note, but please file issues in the team’s GitHub repo where
we triage and manage all issues, asks, etc.:
https://github.com/microsoft/terminal
However, we do recommend that, wherever possible, enthusiastic command-line
users adopt the new Windows Terminal and PowerShell – Console + Cmd are
both supported, but are not receiving significant investment as their job
is preserving backward compatibility, whereas Terminal + PowerShell is all
about the future.
* Валерий Заподовников November 24, 2019 1
Collapse this comment Copy link
Sorry Валерий: I don’t understand the issue you’re describing?
* José Moya November 20, 2019 1
Collapse this comment Copy link
Hi!
I have been using the "legacy terminal" style from the beggining of the
terminal changes.
Today I installed the WSU and so I unclicked the "legacy terminal" (in order
to be able of configuring the username), but I had a black screen for Debian.
When I finally could make a user for it (after resetting the install three
times), I noticed that when I opened cmd, all I saw was a black window,
also.Read more
Hi!
I have been using the “legacy terminal” style from the beggining of the
terminal changes.
Today I installed the WSU and so I unclicked the “legacy terminal” (in order
to be able of configuring the username), but I had a black screen for Debian.
When I finally could make a user for it (after resetting the install three
times), I noticed that when I opened cmd, all I saw was a black window, also.
After some tries, I found there was some invisible text I could copy and
paste in a notepad.
I opened the console properties, selected “colors” and saw they were
configures as white text on black background.
But then I noticed the new “terminal” tab. Inside it, despite of the colors
chosen in the “colors” tab, black was chosen for both text and background.
I think I never tinkered with the terminal colors before, but, anyway,
shouldn’t be some warning about background being the same color as text?
Read less
* Rich Turner Author November 21, 2019 0
Collapse this comment Copy link
Hey Jose.
You should only very rarely need to use the Legacy Console. FWIW, I've used
it once in the last 5 years! Also note that if you enable Legacy Console,
it affects ALL Console instances, not just the one you configure. Best
option is to never use Legacy console unless you have no other choice.
Console only sets colors etc. to defaults on install. Any other changes to
your colors must have been done manually. But...
Read more
Hey Jose.
You should only very rarely need to use the Legacy Console. FWIW, I’ve used
it once in the last 5 years! Also note that if you enable Legacy Console,
it affects ALL Console instances, not just the one you configure. Best
option is to never use Legacy console unless you have no other choice.
Console only sets colors etc. to defaults on install. Any other changes to
your colors must have been done manually. But don’t feel bad – I did just
the same with my foreground and background colors a few months ago
Re. warnings about foreground == background, please post an ask in the
GitHub repo: https://github.com/microsoft/terminal/issues.
Read less
* 長瑞 高 October 12, 2019 1
Collapse this comment Copy link
The Popup Text and Popup Background “Colors” does not work at all.
And, when switching to Chinese input mode, the cursor disappears and never
appear again.
C:\Users\Cray>cmd
Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.
* Barry Irvine October 9, 2019 1
Collapse this comment Copy link
I wonder if these changes are related to cmd.exe's color command breaking?
I used to be able to use the color command without any arguments to reset the
colours to what they were when the window opened, but now that only works if
cmd.exe is run using the /T:xx option. My PC with windows 10.0.16299.1087 is
still working, but all my others have 10.0.18362.295 or later have the
problem. I thought it might...
Read more
I wonder if these changes are related to cmd.exe’s color command breaking?
I used to be able to use the color command without any arguments to reset the
colours to what they were when the window opened, but now that only works if
cmd.exe is run using the /T:xx option. My PC with windows 10.0.16299.1087 is
still working, but all my others have 10.0.18362.295 or later have the
problem. I thought it might be something to do with my settings, but when I
copied cmd.exe from the working install to one of the other PCs it started
working like it used to. Hardly an ideal workaround, especially considering
the permissions changes required to replace cmd.exe, but it saves me having
to update a huge number of .bat files.
Read less
* Jeremy Bradshaw August 27, 2019 1
Collapse this comment Copy link
I realize this blog post is fairly old now and a lot has changed, though FYI,
the link in the "Terminal" tab still comes to this page. Once here, there is
some information that no longer holds true. That is, the link to the other
blog post (where I'll comment too)
https://blogs.msdn.microsoft.com/commandline/2017/08/11/introducing-the-windows-console-colortool/
- is referencing ColorTool as if it is still part of the Microsoft Terminal.
But it isn't. It also seems like all development...
Read more
I realize this blog post is fairly old now and a lot has changed, though FYI,
the link in the “Terminal” tab still comes to this page. Once here, there is
some information that no longer holds true. That is, the link to the other
blog post (where I’ll comment too)
https://blogs.msdn.microsoft.com/commandline/2017/08/11/introducing-the-windows-console-colortool/
– is referencing ColorTool as if it is still part of the Microsoft Terminal.
But it isn’t. It also seems like all development is going into Microsoft
Terminal, and the links lead to that as well in these posts. So it’s hard to
determine what these posts have to do with the built in cmd.exe anymore.
Read less
* Rich Turner Author August 27, 2019 1
Collapse this comment Copy link
Hey Jeremy. Please note that Windows Terminal <> Windows Console. The
former is our brand new next-generation Terminal app for Windows. The
latter is the traditional Console app shipped within Windows itself. I
encourage you to read the blog post series I’ve written to help explain how
the Windows command-line evolved, how it ended up where it has, and where
we’re going into the future:
https://devblogs.microsoft.com/commandline/windows-command-line-backgrounder/
* Neil MacMullen July 25, 2019 1
Collapse this comment Copy link
The colortool looks very interesting. Although it's a larger issue than just
configuring colors for the terminal , one of the things I would like to see
more focus on is the ability to quickly visually distinguish different
windows/terminals to determine context. For example, I often have 7 or 8
different terminal windows open across multiple virtual desktops and figuring
out which one I'm trying to get back to for a particular operation is
always...
Read more
The colortool looks very interesting. Although it’s a larger issue than just
configuring colors for the terminal , one of the things I would like to see
more focus on is the ability to quickly visually distinguish different
windows/terminals to determine context. For example, I often have 7 or 8
different terminal windows open across multiple virtual desktops and figuring
out which one I’m trying to get back to for a particular operation is always
tricky. The least bad solution seems to be to give each a distinct
background color so I can just remember to alt-tab to “the red one” for
example and colortool will certainly help with this (avoiding clashing text
colors is always a problem). Other approaches that might be useful….
* Allow the title/tab bar color to be configured
* Allow a custom background image per instance
* Provide a large numeral overlay during Alt-tab (a bit like when you choose
“Identify desktops” in multi-monitor configuration)
* Provide a mechanism for _automatically_ shading/brushing the terminal
background differently for each new instance.
Of course this is a much larger issue than just Terminal – I often have 2 or
3 instances of Visual Studio running and would like to be able to theme these
separately for quick identification – but terminal/powershell are usually the
worst case for me.
Read less
* Rich Turner Author August 1, 2019 1
Collapse this comment Copy link
Some of this we already do, but please file new feature requests on
https://github.com/microsoft/terminal.
* Gaowen Jin May 12, 2019 1
Collapse this comment Copy link
Change “Cursor Shape” doesn’t work for me. After I type anything, it will
change to “Legacy Style”. This happened in Windows 10 build 18894.
* Ruiyang Li June 11, 2019 1
Collapse this comment Copy link
You are not alone.
* Chris Hayes August 3, 2019 1
Collapse this comment Copy link
I had a little trouble with the cursor option resetting, but it seemed
like it would reset whenever I changed settings tabs without hitting okay
and reopening the settings panel. Not sure if I was experiencing the same
bug as you guys. What if you set the cursor via the Right Click >
Defaults panel? That might force it to stay.
Load more comments
STAY INFORMED
Get notified when new posts are published.
Subscribe
By subscribing you agree to our Terms of Use and Privacy
Follow this blog
Are you sure you wish to delete this comment?
OK Cancel
INSERT/EDIT LINK
Close
Enter the destination URL
URL
Link Text
Open link in a new tab
Or link to existing content
Search
No search term specified. Showing recent items. Search or use up and down arrow
keys to select an item.
Cancel
CODE BLOCK
×
Paste your code snippet
Ok Cancel
Feedback
What's new
* Surface Pro
* Surface Laptop
* Surface Laptop Studio 2
* Surface Laptop Go 3
* Microsoft Copilot
* AI in Windows
* Explore Microsoft products
* Windows 11 apps
Microsoft Store
* Account profile
* Download Center
* Microsoft Store support
* Returns
* Order tracking
* Certified Refurbished
* Microsoft Store Promise
* Flexible Payments
Education
* Microsoft in education
* Devices for education
* Microsoft Teams for Education
* Microsoft 365 Education
* How to buy for your school
* Educator training and development
* Deals for students and parents
* Azure for students
Business
* Microsoft Cloud
* Microsoft Security
* Dynamics 365
* Microsoft 365
* Microsoft Power Platform
* Microsoft Teams
* Microsoft 365 Copilot
* Small Business
Developer & IT
* Azure
* Developer Center
* Documentation
* Microsoft Learn
* Microsoft Tech Community
* Azure Marketplace
* AppSource
* Visual Studio
Company
* Careers
* About Microsoft
* Company news
* Privacy at Microsoft
* Investors
* Diversity and inclusion
* Accessibility
* Sustainability
Your Privacy Choices Opt-Out Icon Your Privacy Choices Your Privacy Choices
Opt-Out Icon Your Privacy Choices Consumer Health Privacy
* Sitemap
* Contact Microsoft
* Privacy
* Manage cookies
* Terms of use
* Trademarks
* Safety & eco
* Recycling
* About our ads
* © Microsoft 2024
Notifications