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 break down when I use python input() function. #20811

New Issue
Closed
opened 2026-01-31 07:24:39 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 07:24:39 +00:00
Owner
Copy Link

Originally created by @c2ray on GitHub (Nov 14, 2023).

Windows Terminal version

Lastest

Windows build number

22H2

Other Software

python3

Steps to reproduce

https://github.com/microsoft/terminal/assets/55729509/2d370f4e-b987-40fa-a1f2-7f4f74930893

Expected Behavior

No response

Actual Behavior

It breaks down when I type something to python input() in windows terminal. It must be the keyword class.

Originally created by @c2ray on GitHub (Nov 14, 2023). ### Windows Terminal version Lastest ### Windows build number 22H2 ### Other Software python3 ### Steps to reproduce https://github.com/microsoft/terminal/assets/55729509/2d370f4e-b987-40fa-a1f2-7f4f74930893 ### Expected Behavior _No response_ ### Actual Behavior It breaks down when I type something to python input() in windows terminal. It must be the keyword `class`.
claunia commented 2026-01-31 07:24:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 14, 2023):

Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback

@zadjii-msft commented on GitHub (Nov 14, 2023): Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback
claunia commented 2026-01-31 07:24:41 +00:00
Author
Owner
Copy Link

@c2ray commented on GitHub (Nov 14, 2023):

Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback

Submited feedback already.

@c2ray commented on GitHub (Nov 14, 2023): > Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback Submited feedback already.
claunia commented 2026-01-31 07:24:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 14, 2023):

Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕

@zadjii-msft commented on GitHub (Nov 14, 2023): Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕
claunia commented 2026-01-31 07:24:41 +00:00
Author
Owner
Copy Link

@c2ray commented on GitHub (Nov 15, 2023):

Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕

Here's the link, https://aka.ms/AAnl6wm.

@c2ray commented on GitHub (Nov 15, 2023): > Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕 Here's the link, https://aka.ms/AAnl6wm.
claunia commented 2026-01-31 07:24:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 15, 2023):

Notes:

  • 19045.3086.vb_release
  • "Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels.
  • RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, { "Tag": "IsTextInputManagementServiceRunning=false" }
  • {
   "version": 7,
   "providerName": "Microsoft.Windows.Terminal.Win32Host",
   "hresult": "2147943809",
   "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp",
   "lineNumber": "703",
   "module": "WindowsTerminal.exe",
   "failureType": "2",
   "message": "",
   "threadId": "12652",
   "callContext": "",
   "originatingContextId": "0",
   "originatingContextName": "",
   "originatingContextMessage": "",
   "currentContextId": "0",
   "currentContextName": "",
   "currentContextMessage": ""
}
    Okay that's just a ERROR_HOTKEY_ALREADY_REGISTERED that's nothing
  • There are three crashes and they're only conhost so that's useless.
  • The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate.

You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷

@zadjii-msft commented on GitHub (Nov 15, 2023): Notes: * 19045.3086.vb_release * "Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels. * RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, `{ "Tag": "IsTextInputManagementServiceRunning=false" }` * ``` { "version": 7, "providerName": "Microsoft.Windows.Terminal.Win32Host", "hresult": "2147943809", "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp", "lineNumber": "703", "module": "WindowsTerminal.exe", "failureType": "2", "message": "", "threadId": "12652", "callContext": "", "originatingContextId": "0", "originatingContextName": "", "originatingContextMessage": "", "currentContextId": "0", "currentContextName": "", "currentContextMessage": "" } ``` Okay that's just a `ERROR_HOTKEY_ALREADY_REGISTERED` that's nothing * There are three crashes and they're only conhost so that's useless. * The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate. You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷
claunia commented 2026-01-31 07:24:42 +00:00
Author
Owner
Copy Link

@c2ray commented on GitHub (Nov 16, 2023):

Notes:

  • 19045.3086.vb_release

  • "Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels.

  • RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, { "Tag": "IsTextInputManagementServiceRunning=false" }

  • {
   "version": 7,
   "providerName": "Microsoft.Windows.Terminal.Win32Host",
   "hresult": "2147943809",
   "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp",
   "lineNumber": "703",
   "module": "WindowsTerminal.exe",
   "failureType": "2",
   "message": "",
   "threadId": "12652",
   "callContext": "",
   "originatingContextId": "0",
   "originatingContextName": "",
   "originatingContextMessage": "",
   "currentContextId": "0",
   "currentContextName": "",
   "currentContextMessage": ""
}

    Okay that's just a that's nothingERROR_HOTKEY_ALREADY_REGISTERED

  • There are three crashes and they're only conhost so that's useless.

  • The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate.

You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷

I updated my windows terminal to 1.18.3181.0. It still appears.

@c2ray commented on GitHub (Nov 16, 2023): > Notes: > > * 19045.3086.vb_release > * "Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels. > * RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, `{ "Tag": "IsTextInputManagementServiceRunning=false" }` > * ``` > { > "version": 7, > "providerName": "Microsoft.Windows.Terminal.Win32Host", > "hresult": "2147943809", > "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp", > "lineNumber": "703", > "module": "WindowsTerminal.exe", > "failureType": "2", > "message": "", > "threadId": "12652", > "callContext": "", > "originatingContextId": "0", > "originatingContextName": "", > "originatingContextMessage": "", > "currentContextId": "0", > "currentContextName": "", > "currentContextMessage": "" > } > ``` > > > > > > > > > > > > Okay that's just a that's nothing`ERROR_HOTKEY_ALREADY_REGISTERED` > * There are three crashes and they're only conhost so that's useless. > * The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate. > > You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷 I updated my windows terminal to 1.18.3181.0. It still appears.
claunia commented 2026-01-31 07:24:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 18, 2024):

We just published a major update to our IME implementation in the nightly Canary branch. It was rewritten from the ground up and has tons of improvements! If you're interested in trying it out, you can get it here: https://aka.ms/terminal-canary-installer
If you already have the Canary build installed, you can use this link to force an update.

If you encounter any issues or have any suggestions, or if you simply like/dislike the changes, please let us know! Thank you for bearing with us. 😊

@lhecker commented on GitHub (Apr 18, 2024): We just published a major update to our IME implementation in the nightly Canary branch. It was rewritten from the ground up and has tons of improvements! If you're interested in trying it out, you can get it here: https://aka.ms/terminal-canary-installer If you already have the Canary build installed, you can use this link to force an update. If you encounter any issues or have any suggestions, or if you simply like/dislike the changes, please let us know! Thank you for bearing with us. 😊
claunia commented 2026-01-31 07:24:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 22, 2024):

Please try Windows Terminal Preview v1.21 or later. As mentioned above, there's a new IME implementation. If the issue still occurs, let us know! Otherwise, the bot will close this issue in about a week. 🙂

@lhecker commented on GitHub (Aug 22, 2024): Please try Windows Terminal Preview v1.21 or later. As mentioned above, there's a new IME implementation. If the issue still occurs, let us know! Otherwise, the bot will close this issue in about a week. 🙂
claunia commented 2026-01-31 07:24:42 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 26, 2024):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 26, 2024): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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-Author-Feedback No-Recent-Activity Priority-1 Product-Terminal Severity-Crash
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#20811
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?