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

Can't change cursor in secondary buffer #293

New Issue
Open
opened 2026-01-30 21:48:10 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:48:10 +00:00
Owner
Copy Link

Originally created by @parkovski on GitHub (Jun 1, 2018).

Since I'm doing all my secondary buffer issues... Using the cursor change sequences in Windows vim doesn't work. They do work in Linux vim and in the regular PowerShell prompt (Windows).

Just realized this may just be vim not setting ENABLE_VIRTUAL_TERMINAL_INPUT. Not sure though, since this is a printed sequence, and true color works - do the cursor escapes need the input or output mode set?

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    17682

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    Execute the following in vim (in vimrc or otherwise):

let &t_SI = "\<Esc>[5 q"
let &t_SR = "\<Esc>[3 q"
let &t_EI = "\<Esc>[1 q"

Now switch between normal and insert mode. Instead of the cursor being set, you'll see [5 q / etc printed to the screen.

  • What's wrong / what should be happening instead:
    The escapes should change the cursor, not write to the screen.
Originally created by @parkovski on GitHub (Jun 1, 2018). Since I'm doing all my secondary buffer issues... Using the cursor change sequences in Windows vim doesn't work. They do work in Linux vim and in the regular PowerShell prompt (Windows). Just realized this may just be vim not setting `ENABLE_VIRTUAL_TERMINAL_INPUT`. Not sure though, since this is a printed sequence, and true color works - do the cursor escapes need the input or output mode set? * Your Windows build number: (Type `ver` at a Windows Command Prompt) 17682 * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Execute the following in vim (in vimrc or otherwise): ``` let &t_SI = "\<Esc>[5 q" let &t_SR = "\<Esc>[3 q" let &t_EI = "\<Esc>[1 q" ``` Now switch between normal and insert mode. Instead of the cursor being set, you'll see ` [5 q` / etc printed to the screen. * What's wrong / what should be happening instead: The escapes should change the cursor, not write to the screen.
claunia added the Resolution-Fix-Available label 2026-01-30 21:48:10 +00:00
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 Resolution-Fix-Available
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#293
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?