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.

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

'window-width' line broken with ASCII 196 and hack in PowerShell #246

Open
OtterKring opened this issue Apr 11, 2017 · 2 comments
Open

'window-width' line broken with ASCII 196 and hack in PowerShell #246

OtterKring opened this issue Apr 11, 2017 · 2 comments
Labels

Comments

@OtterKring
Copy link

OtterKring commented Apr 11, 2017

https://twitter.com/OtterKring/status/848869779268132864

When I draw a horizontal line across the whole window in powershell (Windows 10) with the hack font, it works when using dashes (creates a dashed line), but breaks in mid-window to a second line when using ASCII character 196.
Check my tweet for details. It works correctly with e.g. Lucida Console or Consolas font.

@OtterKring OtterKring changed the title 'window-width 'window-width' line broken with ASCII 196 and hack in PowerShell Apr 11, 2017
@mrmckeb
Copy link

mrmckeb commented Apr 17, 2017

I'm seeing this issue too, @chrissimpkins. I raised it as an issue against the Bash project for Windows - screenshot can be found there.
microsoft/WSL#1936

@chrissimpkins
Copy link
Member

Following the linked report on Windows bash repo. Current information from microsoft/WSL#1936 (comment) is:

This looks like it's the same as #1879, but more specifically it's the bug in #1907. Basically, for some fonts, we can't get the size of all unicode characters correctly, and that can lead so strange rendering issues. Just as an example, running tmux and trying to make a vertical split ( " or split-window -v) with the Hack typeface will most definitely look wrong.

I'll leave this open as one extra node in the large graph of issues related to that bug. I don't think we have a fix planned for that anytime soon, it's a pretty tricky bug that one is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants