On Windows 11 with `CommitMono v1.143`, `CommitMono` cannot be used in VS Code, and `CommitMono 400 Regular` can.

[vagreargnatry]

Hello, I downloaded and installed CommitMono v1.143 from GitHub Release. I encountered a similar issue on my laptop as described in https://github.com/eigilnikolajsen/commit-mono/issues/68 and https://github.com/eigilnikolajsen/commit-mono/issues/70.

Unlike last time, this time there is a font ending with _0 appearing.

This time, in the control panel, only one font (Commit Mono 700 Bold) can be seen.

[eigilnikolajsen]

Are you sure you've uninstalled the old versions before installing new ones?

[vagreargnatry]

When installing the new version, I did not uninstall the old version. After uninstalling the fonts in the Windows settings, the fonts disappeared from the Windows settings, and the fonts with the _0 suffix in the folder also disappeared. However, the four without the _0 suffix were still there; I deleted them in the file manager. Later, I reinstalled v1.143, and the four fonts in the folder did not have the _0 suffix. Subsequently, with v1.143 already installed, I installed it again, and fonts without the _0 suffix no longer appeared. However, I still need to use CommitMono 400 Regular in VSCode.

[eigilnikolajsen]

Interesting, thank you.

[amnweb]

This is the first time I’ve installed this font (1.143), and I can confirm that CommitMono and CommitMono Regular do not work. Only CommitMono 400 Regular is functioning in VS Code.

BTW this is nice font, very similar to my favorite Source Code Pro

[eigilnikolajsen]

Can one of you please check now? I just updated the naming, so hopefully it's working again with just "CommitMono".

[amnweb]

Okay, I downloaded it from the site

"Download custom for dev" working as "CommitMono" "Download custom for design" working as "CommitMono 300","CommitMono 400" and etc.

[vagreargnatry]

I just downloaded Download (default settings) from the website and installed it without CommitMono installed. Filling in CommitMono in VS Code now takes effect, and filling in CommitMono 400 and CommitMono 400 Regular at this time will not work.

[agedburd]

Hi, I encountered this issue last night. I did a first time install on VS Code Windows 10 and Pop!_OS. Entering 'CommitMono' as the font family worked on Pop!_OS, but not on Windows 10. On Windows 10 I had to change the family name to 'CommitMono 425' (I downloaded 425 weight).

I managed to resolve the issue by using steps 3, 5, 6, 10-17 on this page (https://www.fonttutorials.com/how-to-name-font-family/). Please see attached for a zip including the original file I downloaded from commitmono.com and the version where I edited the metadata. Also included are before and after snips of the information I changed.

I don't really know anything about fonts, so hopefully I didn't break anything. However, everything matches up between loading the font on both OSes and it looks great.

P.S. Love the webpage.

before_and_after_fonts_and_snips.zip

[eigilnikolajsen]

@agedburd thank you so much for the research, that is going to come in handy for me. Really nice to include the files, it makes it trivial for me to see the differences. I'm planning a bigger overhaul, where I also move away from OpenTypeJS in the future - your comment here will assist that when it comes to naming. Thank you.

[kenmcd]

When installing the new version, I did not uninstall the old version. After uninstalling the fonts in the Windows settings, the fonts disappeared from the Windows settings, and the fonts with the _0 suffix in the folder also disappeared. However, the four without the _0 suffix were still there; I deleted them in the file manager. Later, I reinstalled v1.143, and the four fonts in the folder did not have the _0 suffix. Subsequently, with v1.143 already installed, I installed it again, and fonts without the _0 suffix no longer appeared. However, I still need to use CommitMono 400 Regular in VSCode.

When a font is in-use (and locked), Windows cannot overwrite the old font file so it adds a number suffix to the new font file name when you install a new version. Windows apps keep track of the valid fonts from the settings in Windows Registry - so it knows the new font is the one with the _0 suffix. But other applications may have issues with multiple font files. For example Affinity applications are confused by this and it messes-up their font cache.

Shut down applications using the fonts, and then make sure the files are actually gone from the Windows Fonts folder (or your User Fonts folder) - and then install the new versions.