Ligatures in regex

[cskujbus]

Regular expressions look a bit awkward with ligatures. Somehow the Iosevka font handles them correctly like on the picture (left: PP8.30, right: Iosevka29.04). Is it possible to do something in case of regular expressions?

[fabrizioschiavi]

Probably you need to use the PragmataPro versions without Liga to fix this. Please let me know if your request is more complex.

[svipas]

@fabrizioschiavi I checked other fonts like Iosevka and they detect and disable ligatures in certain patterns. I believe they do that for cases like this so you could read regex properly. Current workaround would be to disable ligatures if you need to read regex which contains ligatures, but I would love to see something like with Iosevka, Fira Code, etc. in the future.

You can install these fonts and try yourself you will see what they do, also, they are open source maybe you can take parts they are using to disable ligatures in such scenarios.

Also, depends on how complex is this to achieve, maybe it isn't worth it from your side.

[fabrizioschiavi]

@svipas thanks for this precious suggestion!
Could you or someone else let me know a list of regex patterns to disable, please?
Are you sure Iosevka and Fira Code included all this patterns?

[svipas]

I found out commit in Iosevka: be5invis/Iosevka@a52d8e7

If you go into otl/gsub-ligation.ptl you will see Disable regular expression lookaheads

---

In Fira Code I also found:

• Disabled ligatures after regexp lookahead/lookbehinds (?<=< (?<=> (?<==> (?<=| (?<== (?=:= (?=!= (?== (?=== (?==> (?=> (?=>> (?=<< (?=/= (?!! (?!!. (?!= (?!== (?<!! (?<!!. (?<!= (?<!== (?<!--

This commit: tonsky/FiraCode@2ca064a

[fabrizioschiavi]

@svipas you are always a great supporter of this project!
Thank you for your help!