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

After maximizing terminal after git log --oneline, terminal tab hangs upon trying to quit #18753

New Issue
Closed
opened 2026-01-31 06:23:24 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:23:24 +00:00
Owner
Copy Link

Originally created by @rzhao271 on GitHub (Oct 24, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.0

Other Software

git version 2.35.1.windows.2

Steps to reproduce

  1. Make sure the terminal isn't maximized.
  2. Run git log --oneline in a git repo.
  3. Maximize the terminal.
  4. Press the q key to quit from the pager.

Expected Behavior

I expect the prompt to show up again, so that I can input the next command.

Actual Behavior

The terminal tab doesn't seem to respond. It doesn't crash, though.

Originally created by @rzhao271 on GitHub (Oct 24, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.0 ### Other Software git version 2.35.1.windows.2 ### Steps to reproduce 1. Make sure the terminal isn't maximized. 2. Run `git log --oneline` in a git repo. 3. Maximize the terminal. 4. Press the `q` key to quit from the pager. ### Expected Behavior I expect the prompt to show up again, so that I can input the next command. ### Actual Behavior The terminal tab doesn't seem to respond. It doesn't crash, though.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:23:24 +00:00
claunia commented 2026-01-31 06:23:25 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 26, 2022):

Thanks for the feedback! I'm gonna mark this as /dup #11903 unless proven otherwise

@carlos-zamora commented on GitHub (Oct 26, 2022): Thanks for the feedback! I'm gonna mark this as /dup #11903 unless proven otherwise
claunia commented 2026-01-31 06:23:26 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 26, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 26, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 06:23:26 +00:00
Author
Owner
Copy Link

@rzhao271 commented on GitHub (Oct 26, 2022):

Thanks for the issue ref. I took a look in the task manager and it seems that killing less.exe, which comes up as part of the git log command, brings back the prompt. But, I'm unable to repro the issue using Git Bash.
The CPU and memory usage seem normal as well. It's just that in step 4 above, I'm unable to quit from less after pressing q. Other keypresses don't work either after step 4, and I have to create a new tab to continue working.

Screenshot showing the process tree. There are some processes like Git for Windows, less, pwsh, OpenConsole, and Windows Terminal

@rzhao271 commented on GitHub (Oct 26, 2022): Thanks for the issue ref. I took a look in the task manager and it seems that killing `less.exe`, which comes up as part of the git log command, brings back the prompt. But, I'm unable to repro the issue using Git Bash. The CPU and memory usage seem normal as well. It's just that in step 4 above, I'm unable to quit from less after pressing q. Other keypresses don't work either after step 4, and I have to create a new tab to continue working. ![Screenshot showing the process tree. There are some processes like Git for Windows, less, pwsh, OpenConsole, and Windows Terminal](https://user-images.githubusercontent.com/7199958/198152064-a78fa11e-940c-4bfd-ada6-e25a3df9f9c0.png)
claunia commented 2026-01-31 06:23:26 +00:00
Author
Owner
Copy Link

@NikoAri commented on GitHub (Jun 30, 2023):

Confirmed that killing Less.exe process solves this problem.

@NikoAri commented on GitHub (Jun 30, 2023): Confirmed that killing `Less.exe` process solves this problem.
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 Issue-Bug 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#18753
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?