Hello, is it possible to make kerning on by default like it’s done for many other fonts?
For example, in VSCode, if the setting "editor.fontLigatures" is not set, the kerning would be off. So things like mm would look a bit off. In VSCode terminal there is no way to activate ligatures at all, so kerning would be off. Same is true for iTerm.app.

I tried to download custom build with ss05 on, but still no effect.

I customized my download to enable ligatures for the set of equal signs as well as for the arrows, but only arrows are actually working. I've tested this in multiple terminals (WezTerm, Kitty) and it's the same. I downloaded the version from the website this morning. Font book tells me it's version 1.134.

I've even tried to manually enable them by setting the the stylistic sets explicitly thinking maybe they just were baked in, but that also did not work. I then tried to download the font without the equal ligatures from the website thinking maybe the toggle was reversed by accident—nope, didn't work.

I've used lots of fonts with ligatures in the past and know how to enable settings such as call and ssNN features, so I don't believe this is user error, but I've exhausted my knowledge of how to troubleshoot this further.

I didn't want to join the other issue with dumb name, so I made my own for this.

Anyway, the website is really cool, but I think the black on gray or gray on black does not have enough contrast between them.

I am the type that needs high-contrast themes to read things easier, or my eyes tire out fast. I like the aesthetic you are going for, but for contrast issues, maybe white-on-black and black-on-white would work better?

Again your website, I'm not here to demand anything, could have a "high-contrast" toggle button maybe :) Just a thought!

Hey, I don't know if this is a font thing or app thing, but felt like asking..

I like using this font everywhere, basically. It's great, helps me read things.

However, seems in non-monospace fields, the underlining behaves a bit oddly. Like it's a bit squashed on top of the text?

In the screenshot, above text is in Konsole, KDE terminal app.
The text below is in Nheko, a Qt chat application for Matrix.

Seems the bug is also apparent in Kate, KDE code editor:

It seems the gap between underline and the text is gone in some applications.

I am using the otf fonts from the dev packages, only things I've customized are alt-g and square-dots.

I don't know if this is a font thing or linux thing or Qt thing... But all apps I screenshotted use Qt, so I am not sure.

My system info:

Operating System: Arch Linux 
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

Is there anything I could help to do to track this down? Again, I really love this font, it made my reading experience much easier everywhere, and having the ability to use single-storey-g is great.

Alternatively, non-monospace version of this font for use in system wide applications that do not expect to use monospace fonts would be great! I think that may fix the issue, but not sure.

In macOS’s Font Book app, if you look in the Fixed Width collection, Commit Mono is not listed. Is the fact that Commit Mono is monospace a missing piece of metadata? (I don't know anything about how font files work or what information they store about themselves, but other monospace fonts I've installed have correctly ended up in the Fixed Width collection.)

I click on the customize download link in section 8 and the console shows the following error and doesn't download any files.

Uncaught TypeError: e.key is undefined
    keyDown https://commitmono.com/src/js/nav.js:195
    onclick https://commitmono.com/:1
nav.js:195:13

Commit Mono renders the characters ◑ and ◐ as the same character, ◐.

Input:

julia> collect("◑ ◐")
3-element Vector{Char}:
 '◑': Unicode U+25D1 (category So: Symbol, other)
 ' ': ASCII/Unicode U+0020 (category Zs: Separator, space)
 '◐': Unicode U+25D0 (category So: Symbol, other)

Rendered:

Is there a .woff2 version of the font available?
No, but you can use an online conversion tool like this one from Font Squirrel.

(From here)

When I download the zip, there is a .woff2 included, CommitMono VariableFont.woff2.

This is in release 1.137. See attached screenshot.

I have a -spaced version installed with different spacing setting (go figure) and I can only reference the font in VSCode (in NP++ all variants show as italic) by adding the weight at the end of the name, also that makes the editor not map to the italic variants

Also, somehow I have two versions of the font, one without a version and one with the version, in VSCode only the one with the version works

But in IntelliJ all 3 show up but the versioned on only has extra light weight, the non-versioned one looks fine

I remember 137 or 138 showing up properly for the non-versioned one, looks like a recent issue. This is only on Windows, not sure how it behaves on other OSes

Pressing - zooms in rather than out, and pressing + (or =) does nothing. *reads nav.js* Ohh, zoom out is bound to /! It would be nice if the keypad +/- worked too, if only so that us US layout users will be less likely to complain. 😅

(Both the font and website are great BTW)

The ital axis is notoriously tricky to work with in browsers (depending on the browser, it requires font-synthesis: 1 and/or font-variation-settings: "ital" 1). It'd be handy to have the ital = 1 version of the variable font split out into a separate file for ease of use in browsers.

Not too important but I think it's good idea to support Vietnamese language.

You can get the idea/character from https://vietnamesetypography.com/ or JetBrains/JetBrainsMono#14

Thanks for good font to code anw 👍

After almost a decade of using Source Code Pro and trying almost every mono-spaced font out there, I switched to Commit Mono. I use it as default now. Thank you!

This is a request to add a ligature for pipe operator used in e.g. Elixir: |>

• Elixir
• Elm
• JavaScript proposal

Example:

Eigil,
thank you for making the font, it's beautiful

first time i have to make the donation because you deserve

so i open the issue from your suggestion from the mail

current i interrupts the reading flow

for example

it would be great if we have something like first 2s here (sorry for bad drawing with mouse 😅)

take your time, just a suggestion

Hinted TrueType fonts look better on Windows than unhinted OpenType. Would it be possible to provide an [automatically?] hinted TrueType version of the font's main variant set (Regular, Italic, Bold, BoldItalic)?

For example, in "café", the "e" looks like it's been rendered in a different font / size:

I realise there may not be much you can do about this, and I may get used to it, but right now it's jarring.

The 400 font weight, the “normal” weight, is quite thin. Commit Mono’s site advises to use the 450 or 500 weights.

This strikes me as odd. Shouldn't the default weight “just work”? Having to pick the font weight to get a reasonable weight is inconvenient and in some cases impossible (e.g., VS Code lets you choose the font, but not the weight, of the text in the git commit message text field).

I think 400 should be made thicker so that it's suitable as the default weight (probably what 475 is now), with the other weights adjusted accordingly.

Maybe is related: #10

Add these to the character set 𝔸 𝔹 ℂ 𝔻 𝔼 𝔽 𝔾 ℍ 𝕀 𝕁 𝕂 𝕃 𝕄 ℕ 𝕆 ℙ ℚ ℝ 𝕊 𝕋 𝕌 𝕍 𝕎 𝕏 𝕐 ℤ 𝕒 𝕓 𝕔 𝕕 𝕖 𝕗 𝕘 𝕙 𝕚 𝕛 𝕜 𝕝 𝕞 𝕟 𝕠 𝕡 𝕢 𝕣 𝕤 𝕥 𝕦 𝕧 𝕨 𝕩 𝕪 𝕫

Hey,

I found an interesting issue that is reproducible on the commitmono.com page.

• Go to Customize

• Select C++ as example

• Toggle Smart case

• Observe 1][0]: Both [ and ] are raised.

• Observe argv[1];: Only ] is raised, leading to inconsistency.

So it seems Smart case doesn't react properly when bordered by letters.

Cheers!

Postico app uses the following dialog for picking a font

Somehow “Commit Mono” didn’t make it there, I’m wondering if there is some flag that got to be set to explicitly make it “fixed width” category.

It's awesome that Commit Mono has character variants and stylistic sets, so that you don't need to use the website to customize a download. It'd be even better if they were documented on the website, and if it were indicated that customizations only affect the single-font download.

Hey,

great font! One little detail tho, it would be great if the downloadable archive for the customized font included a (text) document detailing the settings that were used to generate it. For reference, or in case you want to change a setting later on.

Thanks!

Not sure if this is just because VSC doesn't support smart kerning fonts.

Looks great in Adobe Illustrator.

Thanks for designing and maintaining such a font, it has quickly become one of my favourite monospaced fonts.

My request is that Commit Mono demands quote design similar to how Apple made theirs in SF Mono. I can see how circle or square flavoured quotes be a tool to break the dullness of the typeface but I think it would be great to have an option.

Commit Mono:

SF Mono:

It’s a very nice font! Would be amazing to have cyrillic characters one day

I would like to use this font on websites, and it would be easy if they are available through Google Fonts. There appear to be instructions at https://github.com/google/fonts/blob/main/CONTRIBUTING.md.

In the latest version, line height seems to be totally messed up.

macOS Terminal.app

Line height = 1:

Line height = 1.5 looks fine, but is the max line height that Terminal.app can do.

VSCode editor

Line height = 1

Line height = 1.5:

VSCode terminal

Line height = 1:

Line height = 2:

While it's cute that we can customize the font on the website before installation, in the long term, developers will want to be able to consume the font and install updated releases from package managers.

If I download the zip file on the web site (I can't give you the URL as it's buried in javascript), it won't decompress properly:

$ unzip CommitMono.zip
Archive:  CommitMono.zip
  inflating: CommitMono-450-Regular.otf
  inflating: CommitMono-450-Italic.otf
  error:  invalid compressed data to inflate
  inflating: CommitMono-700-Regular.otf
  inflating: CommitMono-700-Italic.otf
  error:  invalid compressed data to inflate
  inflating: installation.txt
  inflating: license.txt

The zip on the GitHub releases page works fine.

Hey there,

I'm noticing double quotes (") looking bad in my text editor. Both strokes look to have different blackness, which at small sizes looks weird and makes my brain struggle to focus on the character (are there one two or three quotes? :D).

Screenshot (end of last line):

when zooming in you can see that the right line has less black. Ideally both lines should have the same blackness.

5pt @ 189dpi, freetype 2.13, Sub-pixel anti-aliasing with Slight hinting (I think). Settings:

{"weight":450,"italic":false,"alternates":{"cv01":false,"cv02":true,"cv03":false,"cv04":true,"cv05":false,"cv06":true,"cv07":false,"cv08":false,"cv09":true},"features":{"ss01":false,"ss02":false,"ss03":true,"ss04":true,"ss05":true},"letterSpacing":-5,"lineHeight":0.95,"fontName":"Custom"}

Thanks!

First of all: thank you for creating this awesome font! 🙏

I have downloaded the font with "Smart Kerning" enabled, however it doesn't seem to do anything in Emacs. How is this implemented? Are there any special ligatures that need to be enabled for this to work?

>= and <= are rendering strangely in Visual Studio 2022 on Windows. The font has been customized with both ligatures and arrows. Visual Studio Code seems to display correctly.

The code sample

var y = travelTime.Month >= 11 || travelTime.Month <= 12;
var x = 1 <= 3;

Visual Studio 2022

VS Code

If I customize the font, and then hit the "Download custom for dev" link, it gives me an X. Checking the console logs, this appears to be due to a missing function or the like.

Enabling cv03 on appears to break some ligatures.

Input:

---- ----
⤓⤓⤓⤓ ⤓⤓⤓⤓
.... ....

Rendered (font weight ≠ 475):

Rendered (font weight = 475):

Here is how it is rendered in Iosevka:

Add these characters in the next release

┌┬┐╔╦╗
├┼┤╠╬╣
└┴┘╚╩╝

Commit Mono renders as:

It would be nice to tighten up those vertical gaps (without needing to decrease line height).

Examples of other fonts:

• PT Mono
  
• Courier New
  
• Iosevka
  

Hi, first off, fantastic work on the font. I really like both the philosophy and the end product.

I've noticed that some apps render the regular font (I tried anything between 400 and 500) in bold.

For example, here is the rendering in kitty terminal:

And here it is in Foot:

It's also not necessarily consistent within a single app...

I have honestly no idea if this is in any way related to the font itself, but it doesn't happen to other fonts, so I'm wondering if there's some setting in the font that may be causing it... Or alternatively, if anyone has an idea what I might try tweaking on my side.

I downloaded the "dev" fonts from the website.

I'm on Fedora 38 and Wayland compositor (if that means anything to anyone and makes any different).

Thanks again for a great font!

I have noticed that some terminal emulators (notably kitty and wezterm) don't include surrounding spaces when determining glyph substitutions, so the programming ligatures (ss02) are never triggered. Another related issue is when some sequence occurs at the end of a line.

Would it be possible to have an alternate stylistic set that doesn't require the surrounding spaces for the glyph substitution to occurs?

Hi; firstly, I would like to praise you for the font you produced, certainly the best one I've come across, both due to its consistency/quality and effort in the customization of it.
The suggestion I have in mind is: add a variant to the lowercase "L" character in the customization possibilities, here is the variant format I'm referring to:

The lowercase pqdb are mirrors of each other. This makes it harder for dyslexics to pick up differences between the d and b.

I downloaded Commit Mono (thank you for making this, it's my new favorite font!) with the alternative (single-story) g, as so:

However, it doesn't work consistently. It seems to be triggered via a ligature-like behavior, where it only shows up in certain pairings, rather than replacing the character in the downloaded font, which is seemingly done with the dotted 0, and the 6 and 9 characters. In some cases (e.g. Sublime Text), it never works. In others (e.g. Chrome), it works unexpectedly, for example:

Can the g be changed to behave like the 0, 6, and 9 characters please? Thank you.

This may be related to #25.

I've heard there might be problems in this software. I need someone to post screenshots of how the font looks.

The otf version of the font font looks hazy on 1366x768 displays. Please consider releasing a hinted ttf version.

First of all, thanks for creating/sharing such a high-quality dedicated work!❣️

Here is some quirky behavior I found in macOS.

Configuration

Desired Outcome

This is what I want and it seems working fine in the site.

And quicklook of downloaded files:

Problem

However, when I install this customized fonts, only italic 'g' is not showing correctly in Font Book.app.

Here is what happen in actual use:

I checked only VSC, Adobe Ai, and Figma.
In those apps display wrong 'g' both regular and italic.
Tried uninstall and reinstall the fonts and restart mac/app.

P.S.
Not quite sure what the "Alt. Slanted 'ag'" option does, but I wish I could have separate options for 'a' and 'g'!