New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Underscores missing with certain fonts, such as the default "Monospace Regular" font #2386
Comments
(Copied from #2466) I just got the
The only uncommented lines in my filetypes.common are now:
With this setting and DejaVu Sans Mono Book size 12, underscores are visible. Using |
a very quick way to fix this issue in Geany :
then restart geany. |
@mqu thanks. Of course since the problem is specific to the font its also possible to just select a different font in the GUI. |
Posting to a closed issue, as I don't want to open yet another issue for this. My setup: geany 1.36 (built on Mar 22 2020 with GTK 3.24.14, GLib 2.64.1) on Ubuntu 20.04.2 I can confirm the problem, not only with Default Monospace font (set to DejaVuSansMono.ttf), but also with quite a few other fixed-type fonts on my system. Considering the number of people being affected by this (myself included), would you guys consider changing the default |
@dregrad, We don't collect statistics about the number of Geany installs, but Github stats show about 10 clones per day but that doesn't count the number of installs from distro repositories. So we can't compare the number of people who have problems with the number who use Geany. But the number who report problems is I think less than 10 and therefore only likely to be a small proportion of users. Increasing the default line height setting adds useless spacing between lines for everyone, and that reduces the number of lines, for example for me line spacing of Also To summarise if we changed the default setting:
It seems to me that says the current situation works best for the greatest number of users and the default setting should not change. Perhaps the Ubuntu package should set |
As an aside, I also switched to (a slashed-zero variant of) Hack but stuck with
in Geany because it gives me vertical spacing consistent with that in |
@bencaradocdavies so long as you put that in your user |
@elextr thanks for taking the time to write such a detailed reply - I was not expecting that much. I understand your position and I'm fine with it, considering that there are 2 simple workarounds (switch to a different font or change filetypes.common settings). That said, for argument's sake, regardless of stats I would say that the number of people complaining is not equivalent to the actual number of affected ones. My point is that I'm running a fairly standard Ubuntu LTS setup which is arguably one of the most popular Linux distros out there, so your Very unlucky few estimate is possibly quite larger than you seem to believe, even if only a dozen people have actually come here to tell you about it. But anyway, this is your software and I respect your decision; I agree that the fix may be better applied in the Ubuntu package, but to be honest it's not worth my while to pursue this; I will use the workaround. Thanks for Geany and your support. |
@dregad to put your mind at ease, as far as I know the very unlucky few where |
Obviously i am one of the "very unlucky few" because the problem persisted in most fonts(including the above recommended "Deja-Vu Sans Mono Book"), with all of the recommended BTW, I do not have high resolution settings or fancy 4k/8k monitors, Just a totally standard setup with the most recent Ubuntu-distro... |
@jvollme please paste your filetypes.common where you set |
@jvollme please check that you have an uncommented
line in your filetypes.common, without which
|
-Most other fonts render underscores appropriately
-Changing font size/zoom will cause underscores to appear depending on the setting, even with Monospace Regular font
Geany version: 1.36-1
Using GTK+ v3.24.12 and GLib v2.62.2 runtime libraries.
Using the latest version of Manjaro Linux XFCE.
The text was updated successfully, but these errors were encountered: