microsoft / microsoft/terminal
Scenario: Improved support for different graphics renditions [VT, SGR]
Open
Nobody has claimed this yet.
Area-Rendering
Area-VT
Issue-Scenario
Product-Conhost
Product-Terminal
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
Supported
| Attribute | Standard | Stored | Rendered | As of | Notes |
|---|---|---|---|---|---|
1 Intensity (Bright) |
VT100 | ✔ | ✔ | Always | |
1 Intensity (Bold Weight) |
VT100 | ✔ | ✔ | v1.10 | #109, #5682, https://github.com/microsoft/terminal/issues/2916#issuecomment-544880423 |
2 Faint |
ECMA-48 2nd | ✔ | ✔ | v1.3 | #6703 / #6873 |
3 Italic |
ECMA-48 2nd | ✔ | ✔ | v1.9 | #5461 |
4 Underline |
ECMA-48 2nd | ✔ | ✔ | Always | #6911 as of v1.3, underline is rendered per font metrics |
5 Blink |
VT100 | ✔ | ✔ | v1.4 | #7388 |
7 Reverse Video |
VT100 | ✔ | ✔ | Always | |
8 Conceal/Invisible |
ECMA-48 2nd | ✔ | ✔ | v1.3 | #6876 |
9 Crossed Out |
ECMA-48 2nd | ✔ | ✔ | v1.3 | #6205 |
21 Doubly Underlined |
ECMA-48 3rd | ✔ | ✔ | v1.3 | #2916 |
53 Overline |
ECMA-48 4th | ✔ | ✔ | v1.2 | #6000 |
Unsupported, Planned
| Attribute | Standard | Stored | Rendered | Notes |
|---|---|---|---|---|
| Fancy Underlines (kitty) |
none | ❌ | ❌ | #7228 |
Unsupported, Unplanned
| Attribute | Standard | Stored | Rendered | Notes |
|---|---|---|---|---|
| Extended Fonts (mintty) |
none | ❌ | ❌ | #6779, unplanned |
Miscellaneous Related Issues
- #4321 pursuant to ITU T.416 (ISO-8613-6), we should support (prefer?)
:for subparameter separators instead of;- ("semicolon delimiters" are non-standard for SGR
38,48; see terminfo here)
- ("semicolon delimiters" are non-standard for SGR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named in the issue. Start by reviewing the supported and unsupported SGR tables and the linked issues, then identify a concrete rendition to implement and its validation path. Done would require updating the tracked support and rendering status with tests or other evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100