starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

a cursorCornerRadius setting suggestion #22645

New Issue
Closed
opened 2026-01-31 08:19:23 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:19:23 +00:00
Owner
Copy Link

Originally created by @thiagoigfraga on GitHub (Dec 10, 2024).

Description of the new feature

Hello, everybody. I’ve been looking around the issues list and noticed that this one about adding rounded corners to the cursor shape has been hanging here for a really long time. It attracted my attention: the “filledBox” or “vintage” cursor shapes look so harsh with their sharp edges—especially given how slick and modern everything else in the Terminal can feel. So I figured, why not make this my first “good first issue” contribution, hm?

My plan is pretty straightforward: introduce a new property (something like cursorCornerRadius) so that if someone sets "cursorShape": "filledBox" or "cursorShape": "vintage", they can also tweak this radius value and get a nice, rounded rectangle look. Basically, if we’re already drawing a shape, we just need to feed in a corner radius parameter before it’s rendered, which should give us that softer, more “polished” look.

I think this approach is simple, direct, and easy to configure. it’ll give users more control over how their cursor appears. I’m excited to dive in and try to make this long-standing request finally happen.

If it interest you to, let me know.

Feature Request: CornerRadius on Cursor Shape #1446

Proposed technical implementation details

No response

Originally created by @thiagoigfraga on GitHub (Dec 10, 2024). ### Description of the new feature Hello, everybody. I’ve been looking around the issues list and noticed that this one about adding rounded corners to the cursor shape has been hanging here for a really long time. It attracted my attention: the “filledBox” or “vintage” cursor shapes look so harsh with their sharp edges—especially given how slick and modern everything else in the Terminal can feel. So I figured, why not make this my first “good first issue” contribution, hm? [](url) My plan is pretty straightforward: introduce a new property (something like cursorCornerRadius) so that if someone sets "cursorShape": "filledBox" or "cursorShape": "vintage", they can also tweak this radius value and get a nice, rounded rectangle look. Basically, if we’re already drawing a shape, we just need to feed in a corner radius parameter before it’s rendered, which should give us that softer, more “polished” look. I think this approach is simple, direct, and easy to configure. it’ll give users more control over how their cursor appears. I’m excited to dive in and try to make this long-standing request finally happen. If it interest you to, let me know. [Feature Request: CornerRadius on Cursor Shape #1446](https://github.com/microsoft/terminal/issues/1446) ### Proposed technical implementation details _No response_
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 08:19:23 +00:00
claunia commented 2026-01-31 08:19:24 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 10, 2024):

Hey, welcome to the repository! I appreciate your enthusiasm, but I'd encourage you to keep all your updates in issue #1446 itself. Since that's the main issue for this request, it'll be the best place to write up your proposal and eventually link to your pull request. You don't need to file a new separate issue to declare your intent 🙂

Mind if I mark this one as a duplicate?

@DHowett commented on GitHub (Dec 10, 2024): Hey, welcome to the repository! I appreciate your enthusiasm, but I'd encourage you to keep all your updates in issue #1446 itself. Since that's the main issue for this request, it'll be the best place to write up your proposal and eventually link to your pull request. You don't need to file a new separate issue to declare your intent 🙂 Mind if I mark this one as a duplicate?
claunia commented 2026-01-31 08:19:25 +00:00
Author
Owner
Copy Link

@thiagoigfraga commented on GitHub (Dec 11, 2024):

Hey, welcome to the repository! I appreciate your enthusiasm, but I'd encourage you to keep all your updates in issue #1446 itself. Since that's the main issue for this request, it'll be the best place to write up your proposal and eventually link to your pull request. You don't need to file a new separate issue to declare your intent 🙂

Mind if I mark this one as a duplicate?

Hey, no problem, I understand. I'll keep all the updates in issue #1446, as suggested. Thanks for the clarification! You can mark this one as a duplicate, yes.

@thiagoigfraga commented on GitHub (Dec 11, 2024): > Hey, welcome to the repository! I appreciate your enthusiasm, but I'd encourage you to keep all your updates in issue [#1446](https://github.com/microsoft/terminal/issues/1446) itself. Since that's the main issue for this request, it'll be the best place to write up your proposal and eventually link to your pull request. You don't need to file a new separate issue to declare your intent 🙂 > > Mind if I mark this one as a duplicate? Hey, no problem, I understand. I'll keep all the updates in issue #1446, as suggested. Thanks for the clarification! You can mark this one as a duplicate, yes.
claunia commented 2026-01-31 08:19:25 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 11, 2024):

Thanks for filing. Yeah, we're going to mark this as a /dup of #1446

@carlos-zamora commented on GitHub (Dec 11, 2024): Thanks for filing. Yeah, we're going to mark this as a /dup of #1446
claunia commented 2026-01-31 08:19:25 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Dec 11, 2024):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Dec 11, 2024): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22645
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?