starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal Tab does not allow to type after resize #17003

New Issue
Closed
opened 2026-01-31 05:29:34 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:29:34 +00:00
Owner
Copy Link

Originally created by @buehler on GitHub (Mar 14, 2022).

Windows Terminal version

1.11.3471.1

Windows build number

10.0.22000.0

Other Software

  • git bash: git version 2.35.1.windows.2 (loaded via terminal json)
  • git bash was installed in terminal via git installer
  • installed ZSH inside git bash (zsh --version: zsh 5.8 (x86_64-pc-msys))
  • oh-my-zsh

Steps to reproduce

  1. Open a terminal with the git bash zsh tab
  2. Test out writing something
  3. Resize the terminal (or make it full screen and back)
  4. Try to type again

Terminal

Expected Behavior

It should be able to use my keyboard after resizing the terminal :)

Actual Behavior

I cannot type anything.

It only works when I start the terminal, then resize the window and then type. If I resize the window after I typed something, I cannot type anything after resizing the window.

Originally created by @buehler on GitHub (Mar 14, 2022). ### Windows Terminal version 1.11.3471.1 ### Windows build number 10.0.22000.0 ### Other Software - git bash: git version 2.35.1.windows.2 (loaded via terminal json) - git bash was installed in terminal via git installer - installed ZSH inside git bash (zsh --version: zsh 5.8 (x86_64-pc-msys)) - oh-my-zsh ### Steps to reproduce 1. Open a terminal with the git bash zsh tab 2. Test out writing something 3. Resize the terminal (or make it full screen and back) 4. Try to type again ![Terminal](https://user-images.githubusercontent.com/1067213/158156553-31759b11-475b-45d2-a265-e7d1c9ec2ed1.gif) ### Expected Behavior It should be able to use my keyboard after resizing the terminal :) ### Actual Behavior I cannot type anything. It *only* works when I start the terminal, then resize the window and then type. If I resize the window after I typed something, I cannot type anything after resizing the window.
claunia commented 2026-01-31 05:29:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 14, 2022):

curious. Does this repro for other shells(cmd, powershell)? Do you have anything like X Mouse Button or WizMouse installed? Do you have PowerToys installed?

@zadjii-msft commented on GitHub (Mar 14, 2022): curious. Does this repro for other shells(cmd, powershell)? Do you have anything like X Mouse Button or WizMouse installed? Do you have PowerToys installed?
claunia commented 2026-01-31 05:29:36 +00:00
Author
Owner
Copy Link

@buehler commented on GitHub (Mar 14, 2022):

Hey @zadjii-msft

Just tested:

  • with powershell: it works as intended
  • with git bash only (ZSH deactivated): works as intended

darn. :-(

I know... it is "not your problem" now :-) but do you have any insights into what the problem might be?

@buehler commented on GitHub (Mar 14, 2022): Hey @zadjii-msft Just tested: - with powershell: it works as intended - with git bash only (ZSH deactivated): works as intended darn. :-( I know... it is "not your problem" now :-) but do you have any insights into what the problem might be?
claunia commented 2026-01-31 05:29:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 14, 2022):

Honestly, no 😕

Maybe they've got a bug in how they handle resizes that gets the shell into a bad state?

It may have to do with your prompt - you've got that path on the right side of the window - perhaps that's confusing the shell. Maybe try disabling the prompt customization, see if that helps?

I'm gonna close this out since this seems like a bug that needs to be moved upstream to zsh (or even oh-my-zsh), but feel free to link the thread back to this one, so others who run into this can follow up as well.

@zadjii-msft commented on GitHub (Mar 14, 2022): Honestly, no 😕 Maybe they've got a bug in how they handle resizes that gets the shell into a bad state? It may have to do with your prompt - you've got that path on the right side of the window - perhaps that's confusing the shell. Maybe try disabling the prompt customization, see if that helps? I'm gonna close this out since this seems like a bug that needs to be moved upstream to `zsh` (or even `oh-my-zsh`), but feel free to link the thread back to this one, so others who run into this can follow up as well.
claunia commented 2026-01-31 05:29:36 +00:00
Author
Owner
Copy Link

@buehler commented on GitHub (Mar 15, 2022):

@zadjii-msft
Just to keep you in the loop: effectively, it is an error of "oh my zsh". There is a local function git_prompt_info that is causing the error as referenced in the issue (https://github.com/ohmyzsh/ohmyzsh/issues/9953)

Thank you for the help!

@buehler commented on GitHub (Mar 15, 2022): @zadjii-msft Just to keep you in the loop: effectively, it is an error of "oh my zsh". There is a local function `git_prompt_info` that is causing the error as referenced in the issue (https://github.com/ohmyzsh/ohmyzsh/issues/9953) Thank you for the help!
claunia commented 2026-01-31 05:29:36 +00:00
Author
Owner
Copy Link

@nofacer commented on GitHub (Dec 19, 2022):

They says it's not from them https://github.com/ohmyzsh/ohmyzsh/issues/9953

@nofacer commented on GitHub (Dec 19, 2022): They says it's not from them https://github.com/ohmyzsh/ohmyzsh/issues/9953
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-Triage Product-Terminal Resolution-External
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#17003
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?