Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

typeahead no longer works - commands entered while other commands processing in shell are not received #17587

Closed
ajkessel opened this issue Jul 18, 2024 · 3 comments
Closed

typeahead no longer works - commands entered while other commands processing in shell are not received #17587

ajkessel opened this issue Jul 18, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.

Comments

@ajkessel
Copy link

ajkessel commented Jul 18, 2024 •
edited
Loading

Windows Terminal version

1.21.240625002-preview

(also other recent builds)

Windows build number

10 22H2 (19045.4598)

Other Software

Ubuntu Lunar
bash

Steps to reproduce

Historically, when I entered commands while other commands were processing, they would get queued up at the next command prompt. This no longer appears to work. I don't think it's specific to the shell since I'm getting the same behavior in WSL/Ubuntu and cygwin.

Screen recording below.

Video_2024-07-18_151141.mp4

Expected Behavior

Commands typed while shell is processing should be processed next

Actual Behavior

Nothing
@ajkessel ajkessel added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 18, 2024
@carlos-zamora
Copy link
Member

Thanks for filing. Does this reproduce in the stable channel (version 1.20)?

@carlos-zamora carlos-zamora added Product-Terminal The new Windows Terminal. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 24, 2024
@ajkessel
Copy link
Author

Oddly enough, the problem no longer occurs. I am still on the same version of Terminal (1.21.240625002-preview) and same version of Windows. I can't think of what could possibly have changed on my system that would make this problem, which I've seen for a few weeks, suddenly disappear. I do regularly do Windows and Office 365 updates, but it would be strange for those to impact this behavior of Terminal. Anything you can think of that I should check to track this down?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 24, 2024
@carlos-zamora
Copy link
Member

Cool. Unforunately, no ideas on our end. We'll close it then, but if more people report this we'll be happy to reopen it later. Thanks!

@carlos-zamora carlos-zamora closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2024
@NicholasBrockman NicholasBrockman mentioned this issue Sep 25, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ajkessel @carlos-zamora