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

After using split screen, vim cannot return to the beginning of the line (through the command gg) #18340

New Issue
Closed
opened 2026-01-31 06:10:52 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:10:52 +00:00
Owner
Copy Link

Originally created by @qjpoo on GitHub (Aug 30, 2022).

Windows Terminal version

1.14.2281.0

Windows build number

10.0.19044.0

Other Software

vim : version 7.4.629
os: CentOS Linux release 7.9.2009 (Core)

Steps to reproduce

1. open ssh connection, vim /etc/passwd
image

2. Use the custom shortcut alt + v to split the screen vertically
image

3. return ssh windows, use the gg command in the vim editor, but cannot return to the beginning of the line
image

Expected Behavior

After using split screen, vim can return to the beginning of the line (through the command gg)

Actual Behavior

The actual displayed content does not match the vim line number.

Originally created by @qjpoo on GitHub (Aug 30, 2022). ### Windows Terminal version 1.14.2281.0 ### Windows build number 10.0.19044.0 ### Other Software vim : version 7.4.629 os: CentOS Linux release 7.9.2009 (Core) ### Steps to reproduce **1. open ssh connection, vim /etc/passwd** ![image](https://user-images.githubusercontent.com/19181044/187373155-5664696d-7a79-4565-805d-ae2437f3034a.png) **2. Use the custom shortcut alt + v to split the screen vertically** ![image](https://user-images.githubusercontent.com/19181044/187373546-64bd6630-66df-4ae7-91fe-4ba75ac806d8.png) **3. return ssh windows, use the gg command in the vim editor, but cannot return to the beginning of the line** ![image](https://user-images.githubusercontent.com/19181044/187374029-3beeac12-2e52-4a3f-b9d0-311a4853dcf5.png) ### Expected Behavior After using split screen, vim can return to the beginning of the line (through the command gg) ### Actual Behavior The actual displayed content does not match the vim line number.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:10:52 +00:00
claunia commented 2026-01-31 06:10:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 30, 2022):

Curious - It's like vim never got the SIGWINCH to resize the window - you can see how the lines haven't been redrawn at all. Which ssh are you using/? ssh.exe that ships with Windows? ssh from a WSL distro? Or some other ssh? And which version of ssh?

CentOS has definitely given us plenty of issues in the past.

@zadjii-msft commented on GitHub (Aug 30, 2022): Curious - It's like vim never got the SIGWINCH to resize the window - you can see how the lines haven't been redrawn at all. Which `ssh` are you using/? `ssh.exe` that ships with Windows? `ssh` from a WSL distro? Or some other `ssh`? And which version of `ssh`? CentOS has definitely given us plenty of issues in the past.
claunia commented 2026-01-31 06:10:54 +00:00
Author
Owner
Copy Link

@qjpoo commented on GitHub (Aug 30, 2022):

Curious - It's like vim never got the SIGWINCH to resize the window - you can see how the lines haven't been redrawn at all. Which ssh are you using/? ssh.exe that ships with Windows? ssh from a WSL distro? Or some other ssh? And which version of ssh?

CentOS has definitely given us plenty of issues in the past.

yes, Win10 built-in ssh.exe

C:\Users\Administrator> ssh -V
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

image

@qjpoo commented on GitHub (Aug 30, 2022): > Curious - It's like vim never got the SIGWINCH to resize the window - you can see how the lines haven't been redrawn at all. Which `ssh` are you using/? `ssh.exe` that ships with Windows? `ssh` from a WSL distro? Or some other `ssh`? And which version of `ssh`? > > CentOS has definitely given us plenty of issues in the past. yes, Win10 built-in ssh.exe C:\Users\Administrator> ssh -V OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2 ![image](https://user-images.githubusercontent.com/19181044/187490060-efe3bd98-377a-41e6-a003-34e31fd621f3.png)
claunia commented 2026-01-31 06:10:54 +00:00
Author
Owner
Copy Link

@qjpoo commented on GitHub (Aug 30, 2022):

I tried to use the ssh.exe that comes with git bash. It is possible to use the vim editor command gg to return to the beginning of the line
Thanks for your guide !

image

@qjpoo commented on GitHub (Aug 30, 2022): I tried to use the ssh.exe that comes with git bash. It is possible to use the vim editor command gg to return to the beginning of the line Thanks for your guide ! ![image](https://user-images.githubusercontent.com/19181044/187491114-e295df22-e7a4-4145-ac5a-5049bdf58214.png)
claunia commented 2026-01-31 06:10:54 +00:00
Author
Owner
Copy Link

@qjpoo commented on GitHub (Aug 31, 2022):

solved this problem

@qjpoo commented on GitHub (Aug 31, 2022): solved this problem
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-Attention Needs-Tag-Fix Needs-Triage
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#18340
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?