[Schema] Cursorshape Help has ( ??? ) in possible values #7614

Closed
opened 2026-01-31 01:08:41 +00:00 by claunia · 3 comments
Owner

Originally created by @JustinGrote on GitHub (Apr 23, 2020).

        "cursorShape": {
          "default": "bar",
          "type": "string",
          "description": "Sets the cursor shape for the profile. Possible values: \"vintage\" ( ??? ), \"bar\" ( ???, default ), \"underscore\" ( ??? ), \"filledBox\" ( ??? ), \"emptyBox\" ( ??? )",
          "enum": [
            "bar",
            "emptyBox",
            "filledBox",
            "underscore",
            "vintage"
          ]
        }

The ( ??? ) should not be present in the description. This is not present on any other parameter.

Originally created by @JustinGrote on GitHub (Apr 23, 2020). ```json "cursorShape": { "default": "bar", "type": "string", "description": "Sets the cursor shape for the profile. Possible values: \"vintage\" ( ??? ), \"bar\" ( ???, default ), \"underscore\" ( ??? ), \"filledBox\" ( ??? ), \"emptyBox\" ( ??? )", "enum": [ "bar", "emptyBox", "filledBox", "underscore", "vintage" ] } ``` The ( ??? ) should not be present in the description. This is not present on any other parameter.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 01:08:41 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 23, 2020):

what on earth, those were UTF-8 before I left for lunch

@DHowett-MSFT commented on GitHub (Apr 23, 2020): what on earth, those were UTF-8 before I left for lunch
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 23, 2020):

5FD432AE-F36B-45E5-8501-BCFFC3C52399

Here’s what I see.

Here’s what RFC7159 has to say on the matter:

  1. String and Character Issues

8.1. Character Encoding

JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32.

This is, so far as I can tell, by design.

@DHowett-MSFT commented on GitHub (Apr 23, 2020): ![5FD432AE-F36B-45E5-8501-BCFFC3C52399](https://user-images.githubusercontent.com/14316954/80156574-1ea6b400-8579-11ea-992d-75dbc5b3b4f2.jpeg) Here’s what I see. Here’s what RFC7159 has to say on the matter: > 8. String and Character Issues > >8.1. Character Encoding > > JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32. This is, so far as I can tell, by design.
Author
Owner

@JustinGrote commented on GitHub (Apr 23, 2020):

@DHowett-MSFT good catch, I was looking at a converted one. Apologies for the wasted time.

@JustinGrote commented on GitHub (Apr 23, 2020): @DHowett-MSFT good catch, I was looking at a converted one. Apologies for the wasted time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7614