caveman has quit [Remote host closed the connection]
caveman has joined #foot
vipulogmx has quit [Ping timeout: 246 seconds]
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has joined #foot
ayushnix has quit [Changing host]
uncomfy has joined #foot
xd1le has quit [Quit: xd1le]
Ordoviz has quit [Ping timeout: 272 seconds]
vipulogmx has joined #foot
Ordoviz has joined #foot
uncomfy has quit [Remote host closed the connection]
<WhyNotHugo>
I guess it counts as a monospace font. The package says "1000-em monospace".
<WhyNotHugo>
I doesn't provide any glyphs in the ASCII range; only in private range. It's configured as a fallback for monospace fonts, so when using any of these glyphs nerd fonts get picked up.
<WhyNotHugo>
It feels like an issue because the character being extra wide means it overlaps with the next character and I cannot read the next character.
<WhyNotHugo>
Indeed, they are monospace, and disucssions on the repo seem to indicate that they should never overextend.
<WhyNotHugo>
But I guess that it's unlikely to be a foot issue then...?
Ordoviz has quit [Quit: WeeChat 3.7]
<dnkl>
monospace fonts have different widths
<dnkl>
in other words, it's likely the nerd font is wider than your primary font
<dnkl>
foot logs its cell dimensions. You could compare the width of your primary font, with the nerd font (by using your nerd font as the primary font, and at the same size as your normal primary font)
<dnkl>
to fix/workaround, try setting the nerd font as an explicit fallback in foot.ini and reduce its size, compared to the primary font