From 54e6ebb279230640abd76b0dea4b8dab19713e77 Mon Sep 17 00:00:00 2001 From: "Avinash H. Duduskar" Date: Wed, 4 Dec 2019 21:59:38 +0530 Subject: [PATCH] Added work-around hint for triple-equal-to (===) sign rendering issue. --- Troubleshooting.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 6e83d99..633a2f1 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -32,7 +32,8 @@ Issues: [#812](https://github.com/tonsky/FiraCode/issues/812), [#811](https://gi Known problem, can’t be easily fixed. -* Uneven spacing in `===` and `!==` at certain font sizes, esp. on Windows [#405](https://github.com/tonsky/FiraCode/issues/405) [#243](https://github.com/tonsky/FiraCode/issues/243) [#119](https://github.com/tonsky/FiraCode/issues/119) [#114](https://github.com/tonsky/FiraCode/issues/114) +* Uneven spacing in `===` and `!==` at certain font sizes, esp. on Windows [#405](https://github.com/tonsky/FiraCode/issues/405) [#243](https://github.com/tonsky/FiraCode/issues/243) [#119](https://github.com/tonsky/FiraCode/issues/119) [#114](https://github.com/tonsky/FiraCode/issues/114). The issue with `===` could be worked around by increasing/decreasing the font size by 0.5, so go from 12 to 12.5 or from 13.5 to 13.0 and test. + * Different height of `[]` at certain font sizes [#332](https://github.com/tonsky/FiraCode/issues/332) [#251](https://github.com/tonsky/FiraCode/issues/251)