On Tue, Oct 13, 2020 at 05:26:41PM +0000 I heard the voice of nia, and lo! it spake thus: > > My understanding is that ctwm does not use freetype or fontconfig at all, > it just takes XLFDs which only work with bitmap X11 serverside fonts?
Correct (hopefully not forever; it _is_ one of the things on my todo list. Of course, it looks like about half the world is currently also on the list keeping it company...) I don't use any explicitly unicode fonts, but I don't have a problem seeing all sorts of characters I can't type or draw in menus, titles, icon managers, etc. My font specifiers are pretty genericized: IconManagerFont "-adobe-helvetica-bold-r-normal--*-100-*-*-*" MenuFont "-misc-fixed-bold-r-normal--*-140-*-*-*" TitleFont "-misc-fixed-medium-r-normal--*-130-*-*-*" etc Unfortunately, my experience is figuring out what went wrong when XLFD's don't do what you expect is... fun. Let's go with fun. It's totally inaccurate, but it's a safe word, right? > Upgrading is blocked on the Firefox regression in newer versions. That is somewhat curious. I use FF every day, and haven't seen any behavior like that. All the focus related issue we've fixed are in releases. The _NET_FRAME_EXTENTS stuff is still unreleased in trunk, but I don't see how that could affect focus; AFAIK we only saw it in positioning of form filler dialogues, menus, etc. I'd be sure to try the compiled-in default config, just to be sure you haven't hit some odd interaction with your other options. The next place I'd start looking is at EWMH stuff, since that's a big post-3.8.2 way clients get to ask more things directly of us. Trying a 4.0.3 or trunk build with USE_EWMH disabled is a quick way to check that. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
