On Mon, Mar 20, 2017 at 06:17:42PM +0100, Sven Joachim wrote: > On 2017-03-20 13:05 -0400, G. Branden Robinson wrote: > > On Mon, Mar 20, 2017 at 05:58:27PM +0100, Sven Joachim wrote: > >> On 2017-03-18 16:37 -0400, Branden Robinson wrote: > >> > but "xfd -fa FreeMono-14" works fine, so I figured > >> > I would start with xterm. > >> > >> …I cannot reproduce your problem. See the attached screenshot, where > >> the underscore is rendered just fine. > > > > Your screenshot does not depict the FreeMono font; your screenshot has > > serifs all over the glyphs; FreeMono (or at least the font resolved by > > the name "FreeMono" on my system) is a sans-serif font. > > Which font would that be, and which package do I need to install to get > it? I am a total noob when it comes to fonts.
I apologize; the name FreeMono is a bit of a red herring. I carried the name over via a dotfile from a different machine. If you run the xfd command shown above, it identifies the "matching" font[1] as DejaVu Sans Mono-14 ...which I'm betting comes from the following file: /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf in the following package: fonts-dejavu-core Does this help you repro the problem? I'll retitle the bug separately. I haven't talked to the control bot in years and half-expect to suffer an impedance mismatch. I fear I may even be forced to use "kthxbye". :-| Thanks for the prompt follow-up! [1] On my Debian Stretch system installed freshly as of Friday, 17 March, "matching" is a generous term. "xfd -fa X-14" also brings up DejaVu Sans Mono-14. Frustratingly, "fc-list $pattern" as documented in the fc-list(1) manpage seems to be useless, returning no matches no matter what $pattern is. But that's a bug for a different package... Regards, Branden