Running "V commands" changes the font of console in windows.

[SakthiMahendran]

While using V commands it changes the font of the Command Prompt in windows.

V version:
0.3.0
OS:
Windows 10

What did you do?
Ran some V commands.

What did you expect to see?
Execution of those commands.

What did you see instead?
Executed but the console font is changed.

Edit: This only happens with "Windows Command Prompt" not with PowerShell.

[JalonSolov]

I have never seen this happen. Can you give specific examples?

[ylluminate]

In addition to the examples you ran to reproduce, could you please share screenshots / screencast @SakthiMahendran?

[SakthiMahendran]

In addition to the examples you ran to reproduce, could you please share screenshots / screencast @SakthiMahendran?

Here is the screenshot....

Before:

After:

There is a change in the font and also in the console window size.

What I guess is that the "v.exe" makes this changes to draw some fancy text while we run it without CLI arguments but it also makes this changes while we run some v commands (running with CLI arguments).

[SakthiMahendran]

In addition to the examples you ran to reproduce, could you please share screenshots / screencast @SakthiMahendran?
Here is the screenshot...

Before

I have never seen this happen. Can you give specific examples?

[hungrybluedev]

Can you try with PowerShell ISE and see if this persists? Or better yet, try Windows Terminal.

[JalonSolov]

Which terminal are you using? I don't recognize that one.

[SakthiMahendran]

Which terminal are you using? I don't recognize that one.

Command Prompt

[SakthiMahendran]

Can you try with PowerShell ISE and see if this persists? Or better yet, try Windows Terminal.

This is not happening with PowerShell

[ylluminate]

With Windows Terminal as @hungrybluedev requested, you will find that you can start cmd.exe with it as well and therewith you can then test if this occurs there as well since it handles rendering differently. The idea, I believe, is to see if the issue is dependent for you upon using straight cmd.exe vs it within Windows Terminal...

[SakthiMahendran]

With Windows Terminal as @hungrybluedev requested, you will find that you can start cmd.exe with it as well and therewith you can then test if this occurs there as well since it handles rendering differently. The idea, I believe, is to see if the issue is dependent for you upon using straight cmd.exe vs it within Windows Terminal...

Unfortunately due to some technical issues I can't use "Windows Terminal" : (

[SakthiMahendran]

Update: Now I am seeing this happening with flutter too while running flutter commands.