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
Describe the bug
Virtual terminals on Windows 10 incorrectly calculate the length of bordered text, causing the header and footer to be shorter than expected.
Screenshots
When running inside a virtual terminal launched from IntelliJ, or forcibly launched from the Jar with the session(terminal = VirtualTerminal.create()) option, it renders with incorrect length calculated for the header and footer.
Desktop (please complete the following information):
OS: Windows 10 64bit
Java 17
Kotlin 1.9.0
Kotter 1.1.1
IntelliJ
Gradle 8.2
** Additional Notes:**
I included the text from Powershell as it formatted and displayed correctly, however I couldn't get the text copied out of the virtual terminal (is that possible?), so included only screenshots. I can include screenshots of the correct Powershell 7 behavior if requested.
The text was updated successfully, but these errors were encountered:
Describe the bug
Virtual terminals on Windows 10 incorrectly calculate the length of bordered text, causing the header and footer to be shorter than expected.
To Reproduce
build.gradle.kts
Main.KT
Expected behavior
After bundling the above application into a jar and executing it on Powershell 7.4.1, I see the below
Screenshots
When running inside a virtual terminal launched from IntelliJ, or forcibly launched from the Jar with the
session(terminal = VirtualTerminal.create())
option, it renders with incorrect length calculated for the header and footer.Desktop (please complete the following information):
** Additional Notes:**
I included the text from Powershell as it formatted and displayed correctly, however I couldn't get the text copied out of the virtual terminal (is that possible?), so included only screenshots. I can include screenshots of the correct Powershell 7 behavior if requested.
The text was updated successfully, but these errors were encountered: