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

Over SSH, vim configuration for cursor shape is not respected #12567

New Issue
Closed
opened 2026-01-31 03:18:58 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:18:58 +00:00
Owner
Copy Link

Originally created by @Melandel on GitHub (Feb 13, 2021).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.804]
Windows Terminal version: 1.5.10411.0

Steps to reproduce

  • Open a powershell tab inside Windows Terminal
  • ssh another Windows machine
    • that has the latest vim version
    • and the following vim configuration content:
      let &t_ti.=" \e[1 q"
  let &t_SI.=" \e[5 q"
  let &t_EI.=" \e[1 q"
  let &t_te.=" \e[0 q"
  • run vim over ssh on that machine

Expected behavior

  • The vim configuration for cursor shape is respected, ie:
    • The cursor has a blinking box shape in Normal mode
    • The cursor has a blinking bar shape in Insert mode

Actual behavior

  • The vim configuration for cursor shape is not respected
  • Instead, the cursor always has the shape defined in local Windows Terminal's settings file

Additional note

  • The vim configuration is correctly respected if I use vim without ssh
Originally created by @Melandel on GitHub (Feb 13, 2021). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.804] Windows Terminal version: 1.5.10411.0 ``` # Steps to reproduce * Open a powershell tab inside Windows Terminal * `ssh` another Windows machine * that has the latest vim version * and the following vim configuration content: ``` let &t_ti.=" \e[1 q" let &t_SI.=" \e[5 q" let &t_EI.=" \e[1 q" let &t_te.=" \e[0 q" ``` * run `vim` over ssh on that machine # Expected behavior * The vim configuration for cursor shape **is** respected, ie: * The cursor has a blinking box shape in Normal mode * The cursor has a blinking bar shape in Insert mode # Actual behavior * The vim configuration for cursor shape is **not** respected * Instead, the cursor always has the shape defined in local Windows Terminal's settings file # Additional note * The vim configuration is correctly respected if I use vim without ssh
claunia commented 2026-01-31 03:19:00 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Feb 19, 2021):

What specific SSH client are you using? If you're using the SSH client provided by Windows itself, you may need to switch to a newer version at https://github.com/powershell/Win32-OpenSSH

@skyline75489 commented on GitHub (Feb 19, 2021): What specific SSH client are you using? If you're using the SSH client provided by Windows itself, you may need to switch to a newer version at https://github.com/powershell/Win32-OpenSSH
claunia commented 2026-01-31 03:19:00 +00:00
Author
Owner
Copy Link

@Melandel commented on GitHub (Feb 19, 2021):

  • The SSH client I'm reproducing the issue with: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
  • The SSH client downloaded from your link: OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2

Using the latter, I can still reproduce the issue

  • I also updated SSH on the server from OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 to OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2

I can still reproduce the issue with an updated OpenSSL on both client and server, after rebooting both.

@Melandel commented on GitHub (Feb 19, 2021): * The SSH client I'm reproducing the issue with: `OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5` * The SSH client downloaded from your link: `OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2` Using the latter, I can still reproduce the issue * I also updated SSH on the server from `OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5` to `OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2` I can still reproduce the issue with an updated OpenSSL on both client and server, after rebooting both.
claunia commented 2026-01-31 03:19:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 26, 2021):

Weird. This definitely doesn't repro in WSL locally, so I'm guessing that this is definitely a openssh issue. I don't have a remote machine handy to ssh into to confirm unfortunately. I'd file a bug upstream on https://github.com/PowerShell/Win32-OpenSSH/issues, to see if they can verify.

@zadjii-msft commented on GitHub (Feb 26, 2021): Weird. This definitely doesn't repro in WSL locally, so I'm guessing that this is definitely a openssh issue. I don't have a remote machine handy to ssh into to confirm unfortunately. I'd file a bug upstream on https://github.com/PowerShell/Win32-OpenSSH/issues, to see if they can verify.
claunia commented 2026-01-31 03:19:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 2, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 2, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity Resolution-External
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#12567
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?