I am fiddling with Windows 10 new command prompt. I am with code page 936 (GBK).
I say "new" because I see in the Properties of
cmd that there's a check to
run legacy command prompt (need restart), by default unchecked, so I guess this one I am using is "newer".
The question is, searching the web only gives me some ways to add a font in registry to make legacy cmd to recognise it and show in "Properties"/"Default values" settings, like this:
It mentions to add a font entry to the shown location in:
to make Windows aware of this font. I note that the fonts already listed there are the same ones that I can see in legacy cmd. In normal cmd I see more fonts.
Note that in the picture I opened a legacy cmd prompt, with some Terminal fonts, and in the Properties setting dialog, the fonts from which I can choose are Consolas and Lucida Console, same as in the registry.
And, if I switch to normal cmd, there are two cases:
- If I choose to edit "Properties", I see less fonts and the change works.
- If I choose to edit "Default values", I see more fonts but the change does not take effect.
I can choose between
Yahei Consolas Hybrid and other fonts here, and cmd respects my settings and change the font immediately.
In Default values:
You can see more monospaced fonts here, like
Dejavu Sans Mono,
Monaco and so on, but you cannot make cmd change to these fonts.
I don't know the difference here, but it just doesn't make sense. Some settings that cannot be respected should not exist, not to mention the confusion caused: "Properties" and "Default values" are identical.
What I want, is to change the font in normal cmd to be Monaco, or Dejavu Sans Mono. If not possible, in legacy cmd.
And by the way, if someone can clarify the difference between "Properties" and "Default values", it would be great.