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

vi display is garbled #162

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

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @raymod2 on April 12, 2017 16:32

  • A brief description

When editing a file in bash using vi the screen becomes garbled. This appears to happen when you first open a bash window. If you change the window height vi starts working correctly until you open a new bash window.

  • Expected results

The screen displays the file correctly.

  • Actual results (with terminal output if applicable)

The screen is garbled.

  • Your Windows build number

Version 1703 (OS Build 15063.0)

  • Steps / All commands required to reproduce the error from a brand new installation

Open a bash window. Right-click the title bar and select properties. Click the "Layout" tab and set "Height" to 40 in the "Window Size" size section. Click OK. Close the bash window. Open a new bash window (it should have a height of 40). Now open a vi instance. For example, type 'sudo visudo'. The first thing you will notice is that line 1 is not visible. Only lines 2 through 30 are displayed. If you press the up arrow key to scroll to line 1 nothing will happen. As you try to edit the file things get worse. Press 'o' to insert a new line. Now line 1 appears but it is labeled line 3. The new line you have created is labeled line 4 (but it should be line 2). The rest of the lines also have incorrect line numbers. Start entering text (type "foo"). The 'f' appears in the top line (now labeled line 4) and the "oo" appears in the second line (now labeled line 5) but interspersed with text from another line. As you can see everything is hopelessly garbled.

vi_garbled

  • Strace of the failing command

  • Required packages and commands to install

See our contributing instructions for assistance.

Copied from original issue: Microsoft/WSL#1895

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @raymod2 on April 12, 2017 16:32_ * A brief description When editing a file in bash using vi the screen becomes garbled. This appears to happen when you first open a bash window. If you change the window height vi starts working correctly until you open a new bash window. * Expected results The screen displays the file correctly. * Actual results (with terminal output if applicable) The screen is garbled. * Your Windows build number Version 1703 (OS Build 15063.0) * Steps / All commands required to reproduce the error from a brand new installation Open a bash window. Right-click the title bar and select properties. Click the "Layout" tab and set "Height" to 40 in the "Window Size" size section. Click OK. Close the bash window. Open a new bash window (it should have a height of 40). Now open a vi instance. For example, type 'sudo visudo'. The first thing you will notice is that line 1 is not visible. Only lines 2 through 30 are displayed. If you press the up arrow key to scroll to line 1 nothing will happen. As you try to edit the file things get worse. Press 'o' to insert a new line. Now line 1 appears but it is labeled line 3. The new line you have created is labeled line 4 (but it should be line 2). The rest of the lines also have incorrect line numbers. Start entering text (type "foo"). The 'f' appears in the top line (now labeled line 4) and the "oo" appears in the second line (now labeled line 5) but interspersed with text from another line. As you can see everything is hopelessly garbled. ![vi_garbled](https://cloud.githubusercontent.com/assets/3221147/24968690/49b8e04a-1f6b-11e7-9550-b4f2987890cc.png) * Strace of the failing command * Required packages and commands to install See [our contributing instructions](/CONTRIBUTING.md) for assistance. _Copied from original issue: Microsoft/WSL#1895_
claunia added the Product-Conhost label 2026-01-30 21:44:18 +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 Product-Conhost
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#162
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?