Update console-virtual-terminal-sequences.md with Cursor Shape

[pizzaz93]

Fixes #140
Fixes #108

I've filled in the parts of the chart I can populate based on the report in this issue.
I'm not sure if <n> or ? are the equivalent of SP?

[ghost]

All CLA requirements met.

[opbld33]

Docs Build status updates of commit e98cee0:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/console-virtual-terminal-sequences.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[KalleOlaviNiemitalo]

No, SP is not equivalent to ? or <n>. See ECMA-48 (June 1991) clause 5.4 (Control sequences).

SP q here means 0x20 as an Intermediate Byte, followed by 0x71 as a Final Byte. ? is 0x3F and is generally used as the first Parameter Byte, where it means private or experimental use. <n> in this documentation means an integer parameter, consisting of Parameter Bytes in the range 0x30 to 0x39.

This could be documented as ESC [ <n> SP q followed by a separate table of supported values of <n>. I don't know offhand whether there is a "Code" for this control sequence.

[KalleOlaviNiemitalo]

According to https://invisible-island.net/xterm/ctlseqs/ctlseqs.html and https://github.com/microsoft/terminal/blob/5238235268e32dc6ad1bf2c62b44a28eb16a272b/src/terminal/parser/OutputStateMachineEngine.hpp#L138, the code is DECSCUSR.

[opbld33]

Docs Build status updates of commit f1788cb:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/console-virtual-terminal-sequences.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[pizzaz93]

I added the clarification for SP q and the DECSCUSR code.

I also added an edit for another repo issue that concerns this documentation.

[opbld32]

Docs Build status updates of commit 23b1731:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/console-virtual-terminal-sequences.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit ec95920:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/console-virtual-terminal-sequences.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit e1d1841:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/console-virtual-terminal-sequences.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[DHowett]

Thanks!

[pizzaz93]

@DHowett should we add #259 into this PR?

[DHowett]

Nah. If we merge both of them, Git will handle making sure the final product contains both changes. No need to pre-combine them!

[KalleOlaviNiemitalo]

Elsewhere on this page, the Description column shows how the control sequence is defined by the industry, and the Behavior column shows how Windows Terminal implements it. Did DEC define DECSCUSR with parameter 0 as activating the cursor shape preferred by the user, or is that specific to Windows Terminal?

Page 5-127 of http://boundlessterminals.com/manuals/VT520-VT525ProgrammerInformation.pdf lists "0, 1 or none" as selecting the "Blink Block (Default)" cursor style. That suggests to me that the number 1 means this style specifically, and 0 or none means the default style, which in those DEC terminals is hardcoded rather than a user preference. So the pull request looks OK in that respect.

Does Windows Terminal support DECSCUSR without a parameter? Perhaps that too should be documented here, something like the paragraph in another section of this page:

Console-Docs/docs/console-virtual-terminal-sequences.md

Line 171 in e1d1841

For each of the sequences, the default value for <n> if it is omitted is 0.