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
I try to change the code to move the white space right before the filename to the position right after the icon. And then the icon shows properly in Windows Terminal. But I am not sure whether it will have influence on other functions.
The text was updated successfully, but these errors were encountered:
Hi @LimbicSys, tbh I'm not sure entirely what to do here since this works on both linux and macos, or rather I haven't gotten any issues and I run it in both. I think the issue is more related to how specific terminal emulators handle drawing certain characters as your example show it works in vscode's terminal but not in the windows one.
I try to change the code to move the white space right before the filename to the position right after the icon
If you got a PR working for you can you raise it for me to have a look. The plugin keeps track of the size of buffer and it's content so changing the content might cause the size to be miscalculated, but it sounds like you've just reshuffled some spaces. Anyway if you PR what work's for you I'll test it to make sure nothing else breaks and if not will merge it.
Yeah, this is an issue with Windows Terminal itself. I'm pretty sure it is because it draws the characters strictly from left to right, but do not quote me on that. There might be some hacky workarounds like using the non-breaking space character 0x00A0, but I'm not sure that would be applicable here. I was able to use a hack like that when mixing double-width characters and winblend.
vs code's terminal
Windows Terminal
I try to change the code to move the white space right before the filename to the position right after the icon. And then the icon shows properly in Windows Terminal. But I am not sure whether it will have influence on other functions.
The text was updated successfully, but these errors were encountered: