Font settings not working for WSL apps that draw over the entire screen #263

@dacapoday commented on GitHub (May 19, 2018):

same with you

@dacapoday commented on GitHub (May 19, 2018): same with you

claunia commented

@pcmaniac23 commented on GitHub (Jun 2, 2018):

I have the same issue.

Also the window size changes, not just the font.
e.g. when I am in shell, the height x width might be, say, 40 x 150. But when I go into an application (vim, man pages...etc) that gets displayed over the entire terminal window, the Window's size gets changed to another size (I suspect it goes back to default Cmd window size). The font also gets changed back to the default font for the Cmd window.

It feels like as if when I go into an application from the Shell, settings such as size and font gets changed back to default, however the color settings stays (thank goodness)

@pcmaniac23 commented on GitHub (Jun 2, 2018): I have the same issue. Also the window size changes, not just the font. e.g. when I am in shell, the height x width might be, say, 40 x 150. But when I go into an application (vim, man pages...etc) that gets displayed over the entire terminal window, the Window's size gets changed to another size (I suspect it goes back to default Cmd window size). The font also gets changed back to the default font for the Cmd window. It feels like as if when I go into an application from the Shell, settings such as size and font gets changed back to default, however the color settings stays (thank goodness)

claunia commented

@mikelu commented on GitHub (Jul 5, 2018):

having the same issue.

workaround is changing TERM=xterm-256color to TERM=xterm-color in registry DefaultEnvironment

@mikelu commented on GitHub (Jul 5, 2018): having the same issue. workaround is changing TERM=xterm-256color to TERM=xterm-color in registry DefaultEnvironment

claunia commented

@Tantalus13A98B5F commented on GitHub (Jul 6, 2018):

Same here. Microsoft Windows [Version 10.0.17134.112]. The font also changes when the window is loading or quitting. Both setting the default values and properties still cannot work.

@Tantalus13A98B5F commented on GitHub (Jul 6, 2018): Same here. Microsoft Windows [Version 10.0.17134.112]. The font also changes when the window is loading or quitting. Both setting the default values and properties still cannot work.

claunia commented

@ghost commented on GitHub (Oct 8, 2018):

Same here. By the way, is this issue about WSL? or just an issue that I can solve with the application setting?

@ghost commented on GitHub (Oct 8, 2018): Same here. By the way, is this issue about WSL? or just an issue that I can solve with the application setting?

claunia commented

@ghost commented on GitHub (Oct 11, 2018):

Same here on Windows [Version 10.0.17134.345].
I changed default font to Ubuntu Mono but it gets reverted to its original setting when I run applications like vim or man.

@ghost commented on GitHub (Oct 11, 2018): Same here on Windows [Version 10.0.17134.345]. I changed default font to Ubuntu Mono but it gets reverted to its original setting when I run applications like vim or man.

claunia commented

@zadjii-msft commented on GitHub (Oct 11, 2018):

Filed a bug internally to investigate. I think I know why this might be happening, for whatever reason the alt-buffer used by tmux and vim (et al) either isn't getting the font setting or the codepage setting. My guess is it's not getting the codepage, and then it's re-calculating the font it should use, and defaulting to the default codepage instead of the utf-8 codepage.

@zadjii-msft commented on GitHub (Oct 11, 2018): Filed a bug internally to investigate. I think I know why this might be happening, for whatever reason the alt-buffer used by tmux and vim (et al) either isn't getting the font setting or the codepage setting. My guess is it's not getting the codepage, and then it's re-calculating the font it should use, and defaulting to the default codepage instead of the utf-8 codepage.

claunia commented

@windtoostrong commented on GitHub (Nov 27, 2018):

not sure if it's the same problem with my WSL. I've configured my console default font successfully, but i can't change my vim font setting, no change even with :set guifont=Consolas\ h12 inside vim.

@windtoostrong commented on GitHub (Nov 27, 2018): not sure if it's the same problem with my WSL. I've configured my console default font successfully, but i can't change my vim font setting, no change even with :set guifont=Consolas\ h12 inside vim.

claunia commented

@DHowett-MSFT commented on GitHub (Nov 27, 2018):

@windtoostrong

If you're using vim in the console, guifont doesn't do anything (and cannot do anything.)
If you're using gvim/xvim, you need to say Consolas:h12 (: instead of .)

@DHowett-MSFT commented on GitHub (Nov 27, 2018): @windtoostrong If you're using vim in the console, `guifont` doesn't do anything (and cannot do anything.) If you're using gvim/xvim, you need to say `Consolas:h12` (`:` instead of ` `.)

claunia commented

@windtoostrong commented on GitHub (Nov 28, 2018):

It's vim in the console, it just go with my console configuration. Don't know why Consolas doesn't seem to work for me. I switched to use Microsoft Yahei Mono, my vim and console now shares the same font and works fine.

@windtoostrong commented on GitHub (Nov 28, 2018): It's vim in the console, it just go with my console configuration. Don't know why Consolas doesn't seem to work for me. I switched to use Microsoft Yahei Mono, my vim and console now shares the same font and works fine.

claunia commented

@lnyng commented on GitHub (Dec 9, 2018):

I also have this problem. I found a workaround by using Inziu IosevkaCC SC from http://typeof.net/Iosevka/.

@lnyng commented on GitHub (Dec 9, 2018): I also have this problem. I found a workaround by using Inziu IosevkaCC SC from http://typeof.net/Iosevka/.

claunia commented

@zadjii-msft commented on GitHub (Jan 4, 2019):

I've tried reproing this internally for a bit now and I can't get this behavior to repro. I've tried on a VM with MS Gothic as the default font, and I can't get the alt buffer to revert back to the default font in any scenario.

It's entirely possible that this was fixed in RS5 (the November 2018 Update). There was also a decent amount of code delta in that area since RS5, which could have also mitigated the issue. Without being able to repro it, I won't be able to track the fix down.

If someone can confirm that this is still occurring on a recent Insider's build, I'll reopen the investigation, but until then I'm marking it as not repro.

@zadjii-msft commented on GitHub (Jan 4, 2019): I've tried reproing this internally for a bit now and I can't get this behavior to repro. I've tried on a VM with MS Gothic as the default font, and I can't get the alt buffer to revert back to the default font in any scenario. It's entirely possible that this was fixed in RS5 (the November 2018 Update). There was also a decent amount of code delta in that area since RS5, which could have also mitigated the issue. Without being able to repro it, I won't be able to track the fix down. If someone can confirm that this is still occurring on a recent Insider's build, I'll reopen the investigation, but until then I'm marking it as not repro.

claunia commented

@goomario commented on GitHub (Jan 10, 2019):

I also encountered a problem with resetting fonts. It is recommended to use Xshell with ssh to temporarily replace the default console.

@goomario commented on GitHub (Jan 10, 2019): I also encountered a problem with resetting fonts. It is recommended to use **Xshell** with ssh to temporarily replace the default console.

claunia commented

@sfengyuan commented on GitHub (Feb 14, 2019):

It works!

Like @zadjii-msft said, the problem is Windows can not change the cmd.exe code page permanently, WSL/Bash use utf8 code page which different from cmd.exe usually, so we need to find a font that both supports utf8 and your current default code page of cmd.exe.

The font that @lnyng pointed out works for me.

@sfengyuan commented on GitHub (Feb 14, 2019): **It works!** Like @zadjii-msft said, the problem is Windows can not change the cmd.exe code page permanently, WSL/Bash use utf8 code page which different from cmd.exe usually, so we need to find a font that both supports utf8 and your current default code page of cmd.exe. The font that @lnyng pointed out works for me.

claunia commented

@musma21 commented on GitHub (Feb 17, 2019):

Not sure if this bug has been fixed already, anyway, in my case, just changing the code page of command prompt works :

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage]
"ACP"="1252"
"MACCP"="10000"
"OEMCP"="437"

@musma21 commented on GitHub (Feb 17, 2019): Not sure if this bug has been fixed already, anyway, in my case, just changing the code page of command prompt works : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage] "ACP"="1252" "MACCP"="10000" "OEMCP"="437"

claunia commented

@jindingi commented on GitHub (Feb 28, 2019):

Not sure if this bug has been fixed already, anyway, in my case, just changing the code page of command prompt works :

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage]
"ACP"="1252"
"MACCP"="10000"
"OEMCP"="437"

that works for my vim, thanks!

@jindingi commented on GitHub (Feb 28, 2019): > > > Not sure if this bug has been fixed already, anyway, in my case, just changing the code page of command prompt works : > > Windows Registry Editor Version 5.00 > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage] > "ACP"="1252" > "MACCP"="10000" > "OEMCP"="437" that works for my vim, thanks!

claunia commented