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

[WSL] Console output disappears after editting a file in Vim #502

New Issue
Closed
opened 2026-01-30 21:53:51 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 21:53:51 +00:00
Owner
Copy Link

Originally created by @nernst on GitHub (Jan 3, 2019).

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

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    When using Bash on Windows (WSL) with Ubuntu 18.04, sporadically when exiting Vim on a remote host via ssh, the console stops rendering new text. It doesn't happen all of the time, and it seems that re-entering vim, then exiting immediately solves the problem; no need to close & restart the shell.

What I've seen is that the cursor appears to be in the correct place, and it blinks as usual. The cursor moves in response to key presses. Key presses are sent, as when I'm in this state, I can type 'vim' and vim properly starts and renders. While I'm in vim, everything works as expected. When I exit vim (for the second time), it usually resets and the console works properly again.

  • What's wrong / what should be happening instead:
    I would expect that after quitting Vim, that the console would behave as normal. i.e. key presses are properly echo'd, the prompt is rendered, etc.
Originally created by @nernst on GitHub (Jan 3, 2019). * Your Windows build number: (Type `ver` at a Windows Command Prompt) Version 10.0.18305.1003 * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) When using Bash on Windows (WSL) with Ubuntu 18.04, sporadically when exiting Vim on a remote host via ssh, the console stops rendering new text. It doesn't happen all of the time, and it seems that re-entering vim, then exiting immediately solves the problem; no need to close & restart the shell. What I've seen is that the cursor appears to be in the correct place, and it blinks as usual. The cursor moves in response to key presses. Key presses are sent, as when I'm in this state, I can type 'vim' and vim properly starts and renders. While I'm in vim, everything works as expected. When I exit vim (for the second time), it usually resets and the console works properly again. * What's wrong / what should be happening instead: I would expect that after quitting Vim, that the console would behave as normal. i.e. key presses are properly echo'd, the prompt is rendered, etc.
claunia added the Resolution-Duplicate label 2026-01-30 21:53:51 +00:00
claunia commented 2026-01-30 21:53:51 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 3, 2019):

This looks like it might be #325.

@DHowett-MSFT commented on GitHub (Jan 3, 2019): This looks like it might be #325.
claunia commented 2026-01-30 21:53:52 +00:00
Author
Owner
Copy Link

@nernst commented on GitHub (Jan 3, 2019):

Agreed. I did look through open issues, but didn't see anything that matched. This is likely a duplicate.

@nernst commented on GitHub (Jan 3, 2019): Agreed. I did look through open issues, but didn't see anything that matched. This is likely a duplicate.
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-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#502
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?