You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2022. It is now read-only.
Resizing using Windows Terminalv1.0.1401.0 with any shell causes very odd behavior. The Terminal does not resize, and the buffer becomes bugged.
using this issue for keeping in sync with microsoft/terminal#5843microsoft/terminal#5094. although it might be possible this is not directly related as I experience slightly different effects than described in the issue.
The text was updated successfully, but these errors were encountered:
The code works for Powershell 7-preview (powershell.exe) and Command Prompt (cmd.exe).
Correction: GetCurrentConsoleFont(...) returns an "invalid" font in Windows Terminal. The font has an id of 0 and a size of 0x16px which causes this line to exit early.
If that line is commented out the resizing happens, which is when the buffer bugs out.
According to microsoft/terminal#6395 (comment) getting the font size is not possible with the Windows Terminal by design. This means I cannot detect the size of the terminal. Because CMD/Powershell (unsure if I am using the terminology right?) cannot set the window size to something smaller than the minimum size I cannot ensure the resizing will go through.
However, it may become possible to resize the window later on using ANSI escape codes. If I can detect it the terminal is a Windows Terminal, I could provide a Windows Terminal specific interface Output which uses ANSI-codes instead.
But this is not possible yet. Not sure what to do.
Resizing using Windows Terminal
v1.0.1401.0
with any shell causes very odd behavior. The Terminal does not resize, and the buffer becomes bugged.using this issue for keeping in sync with
microsoft/terminal#5843microsoft/terminal#5094. although it might be possible this is not directly related as I experience slightly different effects than described in the issue.The text was updated successfully, but these errors were encountered: