Sergei Skuratovich

The shape of = ligatures was designed consistent with U+2264 (lessequal) and U+2265 (greaterequal) glyphs in parent font. All two-symbol wide ligatures was made having the same width deliberately. IMHO,...

Could you provide a screenshot? "Incorrectly antialiased or something" sounds like it has some problems with hinting.

I just added a few glyphs to DejaVu Sans Mono. There is no light variant of this font in DejaVu Fonts repository.

Added rules, which prevents partial conversion of >>= and

I don't like how solid line looks in this cases: i--, --i. But '--' needs to be a ligature with less space between minus signs in order to match '++'...

Thank you for feedback. I think it is too early to integrate this font to upstream. This font has some bugs which I don't know how to fix: 1. KDE...

@fabiangreffrath Could you provide an example of such fontconfig or link to info how to do that. It would be great to keep ligatures detached from parent font (no need...

@fabiangreffrath Thank you! The correct rule is: ``` DejaVu Sans Code DejaVu Sans Mono ``` I have tried the ligatures only font and face some problems: 1. I have to...

I agree that optional and positional arguments should be grouped. But suggested group order looks unusual for me. IMHO auto-generated help should follow some widely used standard, for example, POSIX...

Here is not-a-minimal example that repoduces the issue with the same memory usage structure (JsonNodePath, SchemaLocation, JsonSchema on the top). Schemas are availabe in this [github repository](https://github.com/Netcracker/qubership-integration-schemas/tree/ea618c29f8921000c43f44e9415b0c98ad75ce47/src/main/resources/qip-model), document sample that...