Enabling ANSI colors in older versions of Windows
To use ANSI colours in the Windows terminal requires setting VirtualTe
+rminalLevel.
VirtualTerminalLevel = 1 is now set by default for the terminal and in
+ ConPTY.
In Windows versions 1511 through to 1903 this had to be enabled in the
+ registry at:
[HKEY_CURRENT_USER\Console]
"VirtualTerminalLevel"=dword:00000001
Alternatively it can be enabled by calling the SetConsoleMode API with
+ the ENABLE_VIRTUAL_TERMINAL_PROCESSING flag
24 bit color
The latest W10 Console has full 24-bit color support, this is primaril
+y for Linux compatibility so the console properties page and the defa
+ult Windows color mappings still use just 16 colors, there is no plan
+ to add additional console colors to the Win32 API.
To take advantage of the new colors use ColorTool.exe and install a th
+eme, or use the VT100 sequences described here.
When the VT100 sequences are used with a version of the Windows Consol
+e that supports 24-bit colors they will display the desired RGB color
+, older consoles will choose the nearest appropriate color from the e
+xisting 16 color table.
https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences?redirectedfrom=MSDN#extended-colors
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
