Talk:ANSI escape code

message: How can a document with ANSI escapes be converted into a more portable form? I would like to send such a document, but the receiver has no ANSI terminal.
-- Thomas Hafner
— Preceding unsigned comment added by 192.94.73.35 (talk) 14:00, 21 October 2003 (UTC)
replies: text: Agreed. The article lacks a bigger picture - text terminals are only briefly mentioned and even the VT100 is totally omitted although it has had a lot of influence on the implementations of ANSI X3.64. A little bit of history wouldn't hurt, especially since the de-facto combination of standards has evolved over time. --Viznut 12:58, 4 February 2007 (UTC)
thread_title: Untitled

message: The C0 and C1 control codes article says C1 control codes are defined in ISO 6429. ISO 6429 redirect to this article, ANSI escape code. But in this article, C1 control codes are not discussed. Does C1 have actually anyhting to do with ANSI escape codes? --Abdull 08:03, 8 June 2007 (UTC)
replies: text: Answer to myself. According to the official ECMA-048 5th edition, ECMA-048 4th edition was adopted as ISO 6429 2nd edition. ECMA-048 5th edition was adopted as ISO/IEC 6429 3rd edition. ECMA-048 5th edition defines both the so called ANSI escape codes, as well as the C0 set (PDF page 22) and the C1 set (PDF pages 22, 23). By the way CSI can either be the true CSI character from the C1 set, or be a 7-bit safe sequence of ESC character plus [ (bracket, ASCII 0x5B). --Abdull 10:09, 8 June 2007 (UTC)
thread_title:  ISO 6429 

message: This article only covers display codes.  ANSI X3.64 covered any output device, but was fairly open about implementation.  Many printer companies used variations of ANSI over the years— Digital, Texas Instruments, Printronix, Tally, GENICOM and more.  --— Gadget850 (Ed) talk -  21:44, 8 December 2007 (UTC)
replies: text: Perhaps, with appropriate sources.  The only printer controls I recall well are the PCL ones, which are not ANSI Tedickey (talk) 22:21, 8 December 2007 (UTC)

text: Mud eXtension Protocol (MPX) links to a disambiguation page.  Perhaps you meant the redirect to MXP (computing), in turn to http://www.zuggsoft.com/zmud/mxp.htm, which does appear to contain part of the information you mentioned -- but "a number of MUDs" needs some reliable source (third-party of course) TEDickey (talk) 01:39, 29 March 2015 (UTC)
thread_title:  Display codes 

message: As for the footnote about the color of brown, it would be worth providing a link to the Color Graphics Adapter article.
In that article, it mentions that the color of brown was a special case in hardware.  IBM added circuitry to early CGA monitors to force the color to be orange/brown/rust, instead of an unpleasing dark yellow.  The CGA article explains more about this.
Not all early PC clones did the same CGA monitor hack that IBM did.  Therefore, there is evidently a lot of variation in the industry, about what that color should be.
I edited the article to include this link, unless there's a good reason to not do so.  I could not find solid evidence that ANSI color codes were tied to the IBM CGA hardware design, but they sure seem similar.  It's obvious that the 16 available ANSI colors have a 1:1 mapping to available IBM CGA colors, but they appear in a slightly different order.  If proof can be found that ANSI colors were based on CGA colors, or vice versa, please add this to the article.
--Kreline (talk) 21:37, 11 August 2008 (UTC)
replies: text: Thank you for the reference.  I knew dim yellow was really orange/brn, but didn't know why and from where before. Davygrvy (talk) 08:37, 27 January 2009 (UTC)
thread_title:  The ANSI brown/orange/yellow color and IBM CGA hardware 

message: This article should not be inside that category. Please check the main article on User interface technique for a clarification.
Dragice (talk) 19:09, 5 September 2008 (UTC)
replies: text: Of course I disagree.  You're asserting that ANSI escape codes are not (for example), used to render visual effects for user interfaces. Tedickey (talk) 19:54, 5 September 2008 (UTC)

text: I read the article (which is both vague and oriented toward one viewpoint).  Compare against User interface.  I also note the inconsistency between your remarks and the inclusion of Modifier key, Scrolling, Pie menu. Tedickey (talk) 23:27, 5 September 2008 (UTC)

text: Generally, most people interested in the ANSI codes are using them as literal strings in their (shell) command prompt (or similar uses).  That's in spite of higher-level interfaces, e.g., tput for UNIX systems.  There's technical information here because that's what the topic covers. Given the current category composition, it's more interactive than syntax highlighting Tedickey (talk) 20:47, 13 September 2008 (UTC)
thread_title:  Category: User Interface Techniques 

message: Comments regarding "correctness" are misplaced - "code" is applicable, but more generic.  Tedickey (talk) 00:49, 2 January 2009 (UTC)
thread_title:  "ANSI escape code" vs "ANSI escape sequence" 

message: Shouldn't Franktur be Fraktur?  Wikipedia appears to have chosen the second for other articles.
208.252.219.2 (talk) 22:54, 3 March 2010 (UTC)
replies: text: yes - ECMA-48 agrees it should be Fraktur Tedickey (talk) 00:15, 4 March 2010 (UTC)
thread_title:  "Franktur vs Fractur" 

message: Sorry, but the article is somewhat chaotic. I have learned the ANSI codes time ago, but it takes me nearly 30 minutes to find out how to set a certain color from the information in the article. Guess how long a total uninformed person would take... --89.13.133.69 (talk) 00:56, 26 March 2011 (UTC)
thread_title:  A little chaotic 

message: Wrong. On linux (when capslock is off) Alt+A sends "27 97" which is two character sequence, but second character is not in range 64..95. When capslock is on it sends "27 65".  — Preceding unsigned comment added by 188.233.8.82 (talk) 23:20, 17 September 2011 (UTC)
replies: text: However, you're talking about a sequence sent by the keyboard, which is not topical here.  The relevant content would that described in console_codes manpage TEDickey (talk) 23:30, 17 September 2011 (UTC)
thread_title:  For two character sequences the second character is in the range ASCII 64 to 95 (@ to _) 

message: The given example and presentation is Linux-specific, probably doesn't add much value to this topic.  The script example by the way is highlighted inconsistently. TEDickey (talk) 20:58, 27 October 2011 (UTC)
thread_title:  Example of use in shell scripting 

message: I came here trying to interpret the codes handed to me by an obsolete piece of hardware. Decades ago I knoew from the top of my head what ESC-H or ESC-F or ESC-J were -- these days I figured I'd look it up. Turn out the article merely tells me that ESC-* exists (and that there's some range to the valid contents of "*") but there's no list or table telling me what those codes are. Lame.  — Preceding unsigned comment added by 137.78.180.35 (talk) 01:02, 29 October 2011 (UTC)
thread_title:  Incomplete? 

message: Regarding the edit I have done on 19:12, 29 October 2011 (UTC)
replies: text: Per ECMA-48, CSI is "control sequence introducer".  Most of the sequences discussed in this topic begin with CSI.  It has no meaning outside of that context. "String terminator" is something different.  It is used to end certain sequences. TEDickey (talk) 20:48, 29 October 2011 (UTC)
thread_title:  What is a single-character CSI (155/0x9B/0233)? 

message: The vt100 did have imitators, but the given sources don't address this, since they don't mention the relationship TEDickey (talk) 21:09, 4 November 2011 (UTC)
thread_title:  sparked a variety of "clones," 

message: I originally edited ls-color=always to be ls --color=always, but undid it on retrospect. I know 'ls --color=always' is the correct syntax for gnu ls, but felt that I should comment since it was specified as Unix style. Should this be changed? I feel that gnu ls is more common if the syntax is indeed different.  — Preceding unsigned comment added by 128.255.162.247 (talk) 01:08, 20 December 2011 (UTC)
replies: text: The space is certainly necessary. I think any alternative to GNU is going to use a 1-letter switch but cannot find any indication what that may be. The "always" is not needed. I will revert the text.Spitzak (talk) 05:49, 21 December 2011 (UTC)

text: FreeBSD ls implements -G, which is used by GNU ls for a different purpose.  Mac OS X uses the same code (though its manpage suggests that it is from an older version than FreeBSD, which originated this option). ("-G" is not mentioned in the standard, as I recall. Standard ls does not mention color.) A chief difference between the two implementations is that GNU ls uses neither termcap nor terminfo, and makes assumptions about color behavior which limits it to a subset of what a termcap/terminfo application would do, while FreeBSD ls uses termcap. TEDickey (talk) 09:57, 21 December 2011 (UTC)
thread_title:  ls syntax 

message: Can someone explain the 'Fraktur' option a bit more. Judging by the article it is linked to, it selects a gothic font but I've yet to see gothic fonts on any terminal or emulator from 1980 onwards. Thanks.  Stepho  talk  05:43, 14 May 2013 (UTC)
replies: text: Sigh :( But thanks for the reply anyway.  Stepho  talk  11:07, 14 May 2013 (UTC)
thread_title:  Fraktur 

message: At least on Linux here it appears that the order does not matter; the terminal software (e. g. xterm) will pick out what is reasonable for an ANSI sequence. For example, printf "\033[07;35m" and printf "\033[035;7m" will produce the same result at least here. Though not necessarily everywhere, I'd assume. -andy 77.191.221.163 (talk) 13:17, 19 August 2013 (UTC)
replies: text: That's because 7 (inverse) and 35 (magenta text) are unrelated attributes. printf "\033[035;36m" (select magenta text, then cyan text) would look quite different to printf "\033[036;35m" (select cyan text, then magenta text).  Stepho  talk  13:31, 19 August 2013 (UTC)
thread_title:  Order 

message: A number of printers have used the ANSI emulation over the years. With obvious differences between a video terminal and a printer, there are different commands and similar commands are implemented differently.
 GENICOM ANSI
Sequence                   	Meaning
CSI or ESC [               	Control Sequence Introducer
CSI p1 p2 SP ~             	GENEMU: Selects emulation
ESC [p1 ; p2 SP B          	GSM: Modifies vertical (p1) and horizontal (p2) character size
ESC [p1 ; p2 SP G          	SPI: Sets lpi (p1) and/or cpi (p2) in decipoints
ESC H                      	HTS: Sets a tab at current print position
ESC J                      	VTS: Sets a tab at current paper position
ESC K                      	PLD: Moves print line down 3/72 inch (subscript)
ESC L                      	PLU: Moves print line up 3/72 inch (superscript)
ESC P                      	DCS: Introduces dot graphics
ESC [ p1 a                 	HPR: Moves print position right p1 distance (relative)
ESC [ p1 b                 	REP: Dot graphics: repeat preceding character p1 times
ESC c                      	RIS: Resets printer to a known initial state
ESC [ p1 d                 	VPA: Sets vertical position to p1 decipoints or lines
ESC [ pl e                 	VPR: Moves paper forward p1 decipoints
ESC [ p1; p2 f             	HVP: Moves paper and print position (absolute)
ESC [ p1 g                 	TBC: Clears tabs: p1=3 for horizontal
ESC [ p1 ; ...; pn h       	SM: Set mode (PUM, LNM, proportional, character mapping)
ESC [ p1 j                 	HPB: Moves print position left by decipoints or columns
ESC [ p1 k                 	VPB: Moves paper backward by decipoints or lines
ESC [ p1 l                 	RM: Reset mode (PUM, LNM, proportional, character mapping)
ESC [ p1; ... pn m         	SGR: Selects font styles and enhancements
ESC [ p1 p2 ! p            	GENVF2: EVFU vertical paper movement command
ESC [ p1 ; p2 ; p3 q       	GENGRM: Selects graphics horizontal and vertical dot densities
ESC [ p1; p2 ; p3 r        	GENFD: Sets form length (pl), margins: top (p2), bottom (p3)
ESC [ p1; p2 s             	GENSLR: Sets margins: left (p1), right (p2) in decipoints
ESC [ p1 t                 	Selects bar codes p1=3, quit bar code p1=0
ESC [ p1 ;... p12;v        	GENVTS: Sets vertical tabs (p1, etc.) in decipoints or lines
ESC [ p1 x                 	GENSNC: Selects international character sets
ESC [ p1 ; ...; p10 }      	Selects bar code parameters
ESC [ p1 SP }              	GENDFC: Download Font Control: Checks printer for downloaded font
OSC or ESC ]               	Operating System Command: introduces sequence
ESC ] 5                    	BFL (Begin Font Load): Valid only if download option is installed.
ESC ] !                    	Begins 12-channel EVFU table loading
ESC \                      	ST: String Terminator. Exits special modes
ESC [ p1 `                 	HPA: Horizontal Position Absolute
OSC 9 ; p1 ; ... ; p8-pn ST	Character Map Load
: 
See page 16 for the GENICOM ANSI, page 155 for DEC LGplus and page 195 for DEC PPL3 emulations. --  Gadget850 talk 12:58, 21 August 2013 (UTC)
thread_title:  Printers 

message: Neither of the links provided for the comment about 24-bit colors in konsole is relevant to the statement which they are nominally supporting. TEDickey (talk) 13:04, 7 September 2013 (UTC)
thread_title:  24-bit colors (sic) 

message: Those links are clutter, since ANSI.SYS implements such a small fraction of ANSI to begin with TEDickey (talk) 20:29, 15 September 2013 (UTC)
thread_title:  not ANSIS.SYS 

message: Looking at the suggested source, none of the codes appear to be DEC-specific: there are no DEC-specific sources of information cited on the page. Perhaps the proponent of the source can point out the features which have a reliable source - comments in a wiki fail that criteria - otherwise the comment about DEC can be deleted.  A reliable source of course would be WP:Verifiable.  Most of the controls are Amiga-specific or from some unidentified source; a small fraction is "ANSI".  TEDickey (talk) 19:18, 10 July 2014 (UTC)
thread_title:  Amiga versus ANSI versus DEC 

message: Some might visit this page just to see how they can filter those codes out of a stream of characters. How many characters to skip? Is there an "end" tag? All that sort of information is - if at all - hard to find in the article.79.220.111.150 (talk) 01:03, 18 February 2015 (UTC)
thread_title:  Hard to locate information about the general syntax of those escape codes. 

message: Without some specific wording in ECMA-48 (which was not cited), this area is addressed in one of vttest's screens: no terminal which fails to accept controls embedded in a CSI sequence is VT100-compatible.  Perhaps the readers would prefer discussing some other type of terminal, in which case a suitable citation also is needed. TEDickey (talk) 23:55, 20 July 2015 (UTC)
replies: text: That section either needs a citation or to be removed, I agree.  By the way, does "accept" mean executing the controls, or just continuing to treat them like any other character in a CSI sequence? PsyMar (talk) 17:33, 31 July 2015 (UTC)

text: You can download a "real" VT100 from a repository on Github, it's an 8080 emulator and some custom code sufficient to run a real VT100 ROM. It does show that a real VT100 fails some of the more recent tests in vttest though. 2001:470:1F09:10D6:5E26:AFF:FE7D:2F72 (talk) 22:52, 12 December 2015 (UTC)
thread_title:  illegal(sic) characters embedded in CSI sequence 

message: I don't understand why lead would have a "notable exception" instead of a "notable example" in the lead.  Imagine if the WP article on metals ended the lead with "A notable non-metal is Oxygen." KazDragon (talk) 13:47, 9 November 2015 (UTC)
replies: text: The only device/software in common use today that accepts a text stream as input for display to a user as a scrolling output with the newest text at the end that does not interpret ANSI is the Windows console. This exception is 'notable' because it is important enough to discourage usage of these sequences, especially in the stdout of software.Spitzak (talk) 23:46, 10 November 2015 (UTC)
thread_title:  Notable Exception in Lead 

message: The conversion from 0-5 to 0-255 is done with this expression:
 nr = nr ? nr * 40 + 55 : 0;
NOT this one
 nr = nr * 51;
That makes the XTerm colours quite a bit brighter. 2001:470:1F09:10D6:5E26:AFF:FE7D:2F72 (talk) 22:01, 12 December 2015 (UTC)
replies: text: What about terminals that are not XTerm?  Like VT241?  Or VT340?  Or Windows console?  Or PuTTY?  Do any of the standards cover this?  ECMA-48 says to look at T.416, but T.416 says only that it is "the index into the colour table given by the attribute “content colour table” applying to the object with which the content is associated".  Which is really helpful.  82.13.91.100 (talk) 23:45, 22 March 2020 (UTC)
thread_title:  The XTerm 6x6x6 cube is NOT the "websafe" colours.  

message: This article doesn't even introduce what "CSI" is.  It just goes straight into using the acronym, without establishing any prior context. The whole article reads like a reference sheet for geeks, rather than a general article explaining the concepts.
Also, the term "ANSI code" should probably be avoided without further qualification. There are many standards specified by ANSI that are also some kind of "code". Context that may be implicit on some technical forums is not necessarily implicit to a general Wikipedia audience.
: WP:SOFIXIT. Jeh (talk) 23:12, 22 June 2016 (UTC)
replies: text: And please sign your talk page posts? Jeh (talk) 23:14, 22 June 2016 (UTC)
thread_title:  Use of terminology and acronyms 

message: Hello fellow Wikipedians,
I have just modified 2 external links on ANSI escape code. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20120113230301/http://www.pestingers.net/Computer_history/Computers_79.htm to http://www.pestingers.net/Computer_history/Computers_79.htm
*Added archive https://web.archive.org/web/20060206022229/http://enterprise.aacc.cc.md.us/~rhs/ansi.html to http://vt100.net/docs/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 03:17, 24 June 2017 (UTC)
thread_title:  External links modified 

message: This page is worse than useless. Half the escape codes here aren't even defined by ANSI X3.64 or ECMA-48. The whole article is just a dumping ground of pure garbage.
:But it would be useful to know which ones aren't in the standard(s). Can you tell us? --Wtshymanski (talk) 01:32, 27 October 2017 (UTC)
thread_title:  Complete mess 

message: "The display attributes remain in effect until the next occurrence of SGR."
This wording suggests that display attributes are cleared upon the next occurrence of SGR.  For example, consider the independent display attributes italic and underline.  Does the sequence CSI 3 m XXX CSI 4 m YYY show YYY with both italic and underline?  If each SGR resets all display attributes, then codes such as CSI 24 (underline off) are unnecessary.  The article should clarify that individual attributes continue until they are explicitly cleared by another SGR.
I made an edit to this effect.
Jim Fehrle (talk) 00:06, 27 March 2018 (UTC)
replies: text: That means that the effect remains in effect until a following command that relates to that feature comes along to change it - so in the example you give "YYY" will indeed be both italic and underlined. An occurrence of SGRm, being equivalent to SGR0m will reset those and all other features - so it might have been a typo in that quoted sentence! SlySven (talk)  —Preceding undated comment added 00:52, 1 May 2018 (UTC)
thread_title:  Wording clarification: display attributes 

message: The article claims that
According to the vi article:
According to the VT100 article:
and according to this article:
March 1978 predates August 1978, so it would appear that programs using cursor-control sequences to implement a full-screen editor predate "the first popular video terminal to support [the ANSI escape] sequences".
There may have been a point in time at which ANSI terminals were sufficiently dominant that programs didn't need to use termcap or terminfo, or libraries such as curses/ncurses that used termcap or terminfo, and could just directly use ANSI escape sequences, but I suspect that point in time came significantly later than the point at which UN*Xes had a significant number of programs using cursor-positioning escape sequences. Guy Harris (talk) 19:06, 3 July 2018 (UTC)
replies: text: Sure - that had have been in the 1990s when graphical workstations (with terminal emulators) were more prevalent than hardware video terminals. TEDickey (talk) 20:45, 3 July 2018 (UTC)
replies: text: And that was probably significantly later than the point at which UN*Xes had a significant number of programs using cursor-positioning escape sequences, so "Unix-like operating systems almost always could assume they were using a terminal or emulator that supported these sequences" is ahistorical, and the first paragraph of ANSI escape code#Unix-like systems needs to be rewritten to reflect history. Guy Harris (talk) 20:55, 3 July 2018 (UTC)

text: By about 1984 every single terminal used by any modern Unix machine interpreted ANSI escape sequences. This caused lots of software to ignore termcap/curses, for instance the prompt examples in this article right here. The most popular Unix is Linux (or maybe OS/X) which way postdates this.Spitzak (talk) 22:04, 3 July 2018 (UTC)

text: That's not close to being factual, but simply repeating your opinion.  Offhand, there's the Wyse50 and Wyse60, which were used well beyond "1984".  TEDickey (talk) 01:22, 4 July 2018 (UTC)
thread_title:  Could Unix-like systems and software running on them *really* "almost always" assume ANSI escape codes were usable? 

message: In section "Escape sequences" you can find "Sequences have different lengths. All sequences start with ESC (27 / hex 0x1B / octal 033), followed by a second byte in the range 0x40–0x5F (ASCII @A–Z[\]^_).[16]:5.3.a
First, ESC + followed byte is not different lengths.
Second, it's not valid ESC sequence.
See yours ref 16 (ECMA-48):
4.2.48 Intermediate Byte
a) In an escape sequence, a bit combination that may occur between the control function ESCAPE (ESC) and the Final Byte.
b) In a control sequence, a bit combination that may occur between the control function CONTROL SEQUENCE INTRODUCER (CSI) and the Final Byte, or between a Parameter Byte and the Final Byte.
ESC sequence is defined in ECMA-35:
4.17 Intermediate Byte
A bit combination which may occur between that of the control character ESCAPE and the Final Byte in an escape sequence.
13.1.
...
The first byte of an escape sequence shall be the bit combination representing the ESCAPE character and the last shall be known as the Final Byte. An escape sequence may also contain one or more bytes known as Intermediate bytes.
...
I suggest to add
then by any number of "intermediate bytes" in the range 0x20–0x2F (ASCII space and !"#$%&'()*+,-./),
to ESC definition, as is now in CSI definition.
31.179.146.6 (talk) 11:24, 11 October 2018 (UTC)
replies: text: , feel free to boldly make this update. II | (t - c) 11:40, 26 November 2018 (UTC)
thread_title:  Fix ESC sequence 

message: Usually, ANSI escapes will be used by programmers. So, I don't think many people who AREN'T programmers will visit this page often. Therefore, I believe that the "too technical" warning should be dropped, as this page's audience should be mostly programmers who can understand this stuff.
Nathan0kulzer (talk) 13:16, 26 August 2019 (UTC)
replies: text: Unless whoever put it there can clearly indicate what sort of stuff is "too technical" and what audience they think is appropriate as the "minimally technically aware", I'd say "drop it".  If the idea is "try to explain it to somebody who doesn't know what a 'bit' is", then the goal isn't "write it so that person can read the article and understand it without having to, for example, click on the link to bit and read it to understand what a 'bit' is", the goal is "add enough links so that the reader can learn enough to understand it. Guy Harris (talk) 18:54, 26 August 2019 (UTC)
replies: text: Since no one weighed in to oppose it, I went ahead and removed the tag. To my mind, the introduction and 'History' section are at the right level for non-experts, while the other sections are naturally more technical in nature. -- Rublov (talk) 00:57, 29 October 2020 (UTC)
thread_title:  Should we drop the "too technical" warning? 

message: PU2_(ANSI) is a Redir to this article - but no mention. --Itu (talk) 05:34, 26 May 2020 (UTC)
replies: text: Perhaps, at one point, this article talked about PU1 and PU2, but it currently doesn't, so PU1 (ANSI) and PU2 (ANSI) shouldn't redirect to this article.  I've changed them both to redirect to C0 and C1 control codes#C1 control codes for general use instead, as that section at least mentions the Private Use codes. Guy Harris (talk) 05:56, 26 May 2020 (UTC)
thread_title:  PU2 

message: It's (often) okay to use a primary source for stating that something exists, but using a primary source to state that something was first done in a given venue isn't good practice TEDickey (talk) 23:25, 4 June 2020 (UTC)
replies: text: These people came up with the idea of having this extension. When it comes to parts that a standard does not cover, it's not sufficient to just state what something does, but also state who is using it. --Artoria2e5 🌉 09:43, 5 June 2020 (UTC)

text: Sure - I took out the word "first", because it went beyond the facts, and was promotional. TEDickey (talk) 22:41, 5 June 2020 (UTC)

text: The added github listing appears to fall into this same discussion.  It is the same author, with minor contributions from a few others (who for instance use Wikipedia as a source of information). TEDickey (talk) 08:03, 20 October 2023 (UTC)
thread_title:  use of primary source for promotion 

message: The given source doesn't support the statement.  To do this, it would have to either (a) point out that it was done first in SCO (Xenix?) with a year of introduction, or (b) a knowledgeable third-party source which makes this statement. For instance, it wasn't a new feature in 1997 when it was added to xterm, nor was it new when incorporated into Linux console a few years before that.  So a 2003 manual mentioning the feature doesn't support the term "invention" TEDickey (talk) 13:39, 13 June 2020 (UTC)
thread_title:  "PC colors" as as SCO "invention" 

message: I suggest to add ESC[?3h and ESC[?3l that perform this switch. pietro151.29.37.171 (talk) 11:57, 8 December 2020 (UTC)
thread_title:  80/132 cols 

message: Dear authors
The sentence "So, for example, <esc>[4;2~ is Shift-End, <esc>[20~ is function key 9, <esc>[5C is Ctrl-Right" has been marked as dubious. However, given that the tables below that sentence are correct, I think the examples are valid:
Example 1: <esc>[4;2~: 
This matches the general pattern "<esc> '[' (<num>) (';'<num>) '~'" with the explanation "keycode sequence, <num> defaults to 1" given above. As is explained in the text "If the terminating character is '~', the first number must be present and is a keycode number, the second number is an optional modifier value.". Therefore "4" ist the keycode, which according to the "vt sequences" table blow is "<esc>[4~ - End" and ";2" is the modifier. The modifier  "... defaults to 1, and after subtracting 1 is a bitmap of modifier keys being pressed: Meta-Ctrl-Alt-Shift.". So 2-1=1 and in the bit map "Meta-Ctrl-Alt-Shift" this selects "Shift"
Example 2: <esc>[20~
This is F9 as per the "vt sequences" table: "<esc>[20~ - F9"
Example 3: <esc>[5C
In the paragraph above the examples it is explained "If the terminating character is a letter, the letter is the keycode value, and the optional number is the modifier value." So "C" is the terminating letter and the meaning of the keycode letter "C" is "<esc>[C - Right" as per the table "xterm sequences". And from the modifier 5 one has to subtract 1 to get the value for the bitmap of the modifier keyes. So 5-1=4 and 4 selects "Ctrl" in "Meta-Ctrl-Alt-Shift". 
So I think the examples are correct (but it took me a while to understand them).
So why dubious?
89.206.112.15 (talk) 09:44, 22 March 2021 (UTC)
thread_title:  Dubious examples? Don't think so 

message: The information about the "Windows Terminal" is incorrect. It says "Windows Terminal, introduced in 2019, supports the sequences by default. Microsoft has deprecated the classic Windows Console subsystem and APIs, and intends to replace them with Windows Terminal going forward". I find it very difficult to believe that the Window Console Subsystem and APIs would ever be deprecated so I read the reference to it very carefully and I could not find any reference to the statement. There was a link in the reference page https://docs.microsoft.com/en-us/windows/console/classic-vs-VT which addresses concerns about the classic Windows Console subsystem and APIs, in section "Future planning and pseudoconsole" on this page it say this:
There are no plans to remove the Windows console APIs from the platform.
On the contrary, the Windows Console host has provided the pseudoconsole technology to translate existing Windows command-line application calls into virtual terminal sequences and forward them to another hosting environment remotely or across platforms.
:Impression from the reference is that when users run "Command" or "Powershell" the terminal window will be Windows Terminal, and programs run inside it can assume ANSI sequences work. It does seem sensible that the old API would be emulated in this. The API is not being depreciated. But the inability to print escape sequences *is* being depreciated.Spitzak (talk) 01:56, 5 August 2021 (UTC)
thread_title:  Incorrect information about Windows Console being replaced 

message: 3.10 contains multiple occurences of "(draft section)" and uses code blocks instead of tables.
197.185.106.15 (talk) 04:36, 13 September 2021 (UTC)
thread_title:  3.10 has been incomplete for months 

message: I believe it would be benefitial to add a column per teminal emulator implementation to state SGR code support.
Kaznovac (talk) 15:13, 2 January 2022 (UTC)
replies: text: perhaps not: you'd need a reliable source, and it's fairly well known that coverage is haphazard (see xterm FAQ) TEDickey (talk) 15:17, 2 January 2022 (UTC)
thread_title:  Add SGR terminal support information 

message: I think the CPM section under history could be substantially cut down.  It barely mentions ANSI codes at all and wants to talk about CPM hardware terminals instead.
Maybe CPM had substantial use in the 80s with ANSI terminals, but you wouldn't know it from reading that section. — Preceding unsigned comment added by 45.48.161.1 (talk) 20:51, 19 June 2022 (UTC)
replies: text: That section was removed in https://en.wikipedia.org/w/index.php?title=ANSI_escape_code&diff=1186405891&oldid=1186404947 this edit], with the edit comment "remove - 95% off topic, besides phrase "also describes it as supporting ANSI"". Guy Harris (talk) 06:37, 24 April 2024 (UTC)
thread_title:  CP/M section barely mentions ANSI codes 

message: That sentence needs a rewrite (color support in terminfo predates slang by more than ten years). TEDickey (talk) 18:37, 5 November 2022 (UTC)
thread_title:  terminfo/termcap color-support vs slang 

message: An editor's comment about colors versus reverse-video is poorly sourced (the source given provides the reader with no insight) TEDickey (talk) 18:55, 26 April 2023 (UTC)
replies: text: I believe the text cited in support of the "inconsistent emulation" claim is found in the Display elements subsection on the target page. Unfortunately that subsection is not directly linkable, due to that page's poor HTML-internal structure. –ReadOnlyAccount (talk) 16:38, 29 February 2024 (UTC)

text: You appear to be talking about the paragraph beginning "Virtual terminal display buffers also encompass a "light/dark background" screen flag", which uses the term only in the sentence "console-termio-realizer handles this flag itself, therefore, for consistency across realized-upon terminals and with other realizers.", following a couple of comments (including some inaccurate) about other programs.  That's not a reliable source for the purpose intended in this topic. TEDickey (talk) 19:54, 29 February 2024 (UTC)
thread_title:  inconsistent emulation