-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Closed
Labels
Area-OutputRelated to output processing (inserting text into buffer, retrieving buffer text, etc.)Related to output processing (inserting text into buffer, retrieving buffer text, etc.)Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-2A description (P2)A description (P2)Product-ConptyFor console issues specifically related to conptyFor console issues specifically related to conpty
Milestone
Description
Environment
Windows build number: Version 10.0.18362.356
Steps to reproduce
- Open a bash shell in a conhost window.
- Press enter a few times until you reach the bottom of the viewport.
- Run
cmd.exeto switch to a cmd shell. - Run the
vercommand, just to get something in the command history. - Press
F7to view the history.
Expected behavior
I'd expect the history window to popup showing the ver command I'd just entered.
Actual behavior
The history window does open, but part of it is invisible. It appears to be cut off at the point where the console transitioned from the bash shell to the cmd shell.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area-OutputRelated to output processing (inserting text into buffer, retrieving buffer text, etc.)Related to output processing (inserting text into buffer, retrieving buffer text, etc.)Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-2A description (P2)A description (P2)Product-ConptyFor console issues specifically related to conptyFor console issues specifically related to conpty
