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

Terminal will auto repeat my last input #5777

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

Originally created by @xjr7670 on GitHub (Jan 5, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Microsoft Windows [Version 10.0.18363.535]
Windows Terminal version (if applicable):
Version: 0.7.3451.0

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

when I input something within the terminal, no matter it is command line or coding with VIM editor in WSL, it will all occur this problem.

For example, I want to key down "cat -n 10 myfilename" in the wsl command line, sometimes when I finished key down the letter "n", I want to continue to write "a", but at this time, The terminal will auto repeating the letter "n" for many many times. I was not able to do anything unless just press the X button to close that window.

I have recorded a video to show this problem

ezgif com-video-to-gif

But this will not occur in the system's cmd which opens with "win+r" then write down "cmd" or PowerShell and so on. Only occur in terminal
image

The system version which I use is:
image

I cannot search for anything with this problem. Appreciate to get some help

Originally created by @xjr7670 on GitHub (Jan 5, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Microsoft Windows [Version 10.0.18363.535] Windows Terminal version (if applicable): Version: 0.7.3451.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> when I input something within the terminal, no matter it is command line or coding with VIM editor in WSL, it will all occur this problem. For example, I want to key down "cat -n 10 myfilename" in the wsl command line, **sometimes** when I finished key down the letter "n", I want to continue to write "a", but at this time, The terminal will auto repeating the letter "n" for many many times. I was not able to do anything unless just press the X button to close that window. I have recorded a video to show this problem ![ezgif com-video-to-gif](https://user-images.githubusercontent.com/7731794/71775906-2b4fce00-2fc3-11ea-83bb-26d4f67d4a6d.gif) But this will not occur in the system's cmd which opens with "win+r" then write down "cmd" or PowerShell and so on. Only occur in terminal ![image](https://user-images.githubusercontent.com/7731794/71775851-88974f80-2fc2-11ea-8a59-6a21ba21bdbf.png) The system version which I use is: ![image](https://user-images.githubusercontent.com/7731794/71775925-605c2080-2fc3-11ea-9292-22b057f603fd.png) I cannot search for anything with this problem. Appreciate to get some help
claunia commented 2026-01-31 00:21:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 5, 2020):

This seems like #3706, but your example indicates that it happens for normal input?

@DHowett-MSFT commented on GitHub (Jan 5, 2020): This seems like #3706, but your example indicates that it happens for normal input?
claunia commented 2026-01-31 00:21:22 +00:00
Author
Owner
Copy Link

@xjr7670 commented on GitHub (Jan 5, 2020):

This seems like #3706, but your example indicates that it happens for normal input?

Yes, absolutely normal. I see that issue #3706 was caused by the Chinese character. Or it may occur by the Chinese input software? I am using the Microsoft Wubi from the system. But this problem occurred when I was in English input status.

@xjr7670 commented on GitHub (Jan 5, 2020): > This seems like #3706, but your example indicates that it happens for normal input? Yes, absolutely normal. I see that issue #3706 was caused by the Chinese character. Or it may occur by the Chinese input software? I am using the Microsoft Wubi from the system. But this problem occurred when I was in English input status.
claunia commented 2026-01-31 00:21:22 +00:00
Author
Owner
Copy Link

@clairernovotny commented on GitHub (Jan 5, 2020):

I started seeing this to on the latest nightlies.

See screenshot. This appears to be a display issue as the commands execute successfully. Here I'm typing "git <enter>" "git checkout <enter>"

2020-01-05_11-10-55

The latest store version is fine for me.

@clairernovotny commented on GitHub (Jan 5, 2020): I started seeing this to on the latest nightlies. See screenshot. This appears to be a display issue as the commands execute successfully. Here I'm typing "git `<enter>`" "git checkout `<enter>`" ![2020-01-05_11-10-55](https://user-images.githubusercontent.com/1427284/71782791-2c293580-2fac-11ea-8b9f-79cbb64edc6b.gif) The latest store version is fine for me.
claunia commented 2026-01-31 00:21:22 +00:00
Author
Owner
Copy Link

@djdv commented on GitHub (Jan 5, 2020):

I'm experiencing the same as @onovotny
Building from current master (d711d731d7) results in this behaviour.
I reverted to 4daf1d7f9c (just because it was the last usable version I built) and don't see that issue, so it may be within that commit range.

@djdv commented on GitHub (Jan 5, 2020): I'm experiencing the same as @onovotny Building from current master (d711d731d7d00259b2e0fe5847928c9f1c1121ed) results in this behaviour. I reverted to 4daf1d7f9c36eb2129c277e89255d44670db0537 (just because it was the last usable version I built) and don't see that issue, so it may be within that commit range.
claunia commented 2026-01-31 00:21:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 5, 2020):

Yeah, this is #4107 (PR #4113)

@DHowett-MSFT commented on GitHub (Jan 5, 2020): Yeah, this is #4107 (PR #4113)
claunia commented 2026-01-31 00:21:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 6, 2020):

@xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea.

Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue.

@DHowett-MSFT commented on GitHub (Jan 6, 2020): @xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea. Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue.
claunia commented 2026-01-31 00:21:23 +00:00
Author
Owner
Copy Link

@xjr7670 commented on GitHub (Jan 7, 2020):

@xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea.

Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue.

In addition to the input software, there is a software called DLP. Which is used to monitoring every computer's internet I/O traffic inside our company to prevent information leakage.

After installed DLP, it will auto output some error info to the shell window, especially within the powershell
image
image

I can offer something about DLP if you need it. For example the log file or something else.

@xjr7670 commented on GitHub (Jan 7, 2020): > @xjr7670 Are there any other interesting things about your machine that might help us figure this one out? Nobody here's got any idea. > > Just FYI - #4107 is a new regression after 0.7, so it is not the cause of this issue. In addition to the input software, there is a software called DLP. Which is used to monitoring every computer's internet I/O traffic inside our company to prevent information leakage. After installed DLP, it will auto output some error info to the shell window, especially within the powershell ![image](https://user-images.githubusercontent.com/7731794/71861506-8e5f7300-3131-11ea-97aa-66bebac8d8d3.png) ![image](https://user-images.githubusercontent.com/7731794/71861530-a33c0680-3131-11ea-84df-abd1bc6e1249.png) I can offer something about DLP if you need it. For example the log file or something else.
claunia commented 2026-01-31 00:21:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 11, 2020):

We have made some changes to the input stack recently. Is this still happening?

@DHowett-MSFT commented on GitHub (May 11, 2020): We have made some changes to the input stack recently. Is this still happening?
claunia commented 2026-01-31 00:21:23 +00:00
Author
Owner
Copy Link

@xjr7670 commented on GitHub (May 11, 2020):

It has not reappeared recently, it should have been repaired

image

@xjr7670 commented on GitHub (May 11, 2020): It has not reappeared recently, it should have been repaired ![image](https://user-images.githubusercontent.com/7731794/81557284-4d68bb00-93be-11ea-9fd4-df0c0121a5b5.png)
claunia commented 2026-01-31 00:21:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 12, 2020):

Thank you!

@DHowett-MSFT commented on GitHub (May 12, 2020): Thank you!
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 Area-Input Issue-Bug Needs-Attention Needs-Repro Needs-Tag-Fix Product-Terminal Resolution-No-Repro
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#5777
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?