The new ebuild for dmenu 4.6 just is..xxxx.... It does not use Xft anymore and messes with fonts. dmenu_run -b -fn "-*-fixed-bold-*-*-*-18-*-*-*-*-*-*-*" -nb "#0E4D40" -nf "#ffffff" -> Had bold font, now the font just is ..xxxxx...
Seems it is because i was not using Xft, and fontspec worked. With the new dmenu it does not work. It was right to have use-flags for specifying whether to use Xft or not.
I could not understand the bug report completely. Could you describe the problem more precisely? Is there a reason, why we should assume that the problem is in the gentoo ebuild and not in the source code from upstream?
Hi, it seems, that XLFD are not supported anymore. But that would be needed to check via a changelog, if available or asking the author. If you would like, i may do it. Meanwhile i have fixed the issue by using a xft font specification, which matches the same appearance.
I have no idea what this bug report is about.
Well, dmenu allows to specify which font to use. There are two main font-systems which use font-specifications in their own format: Xft and X11 XLFD I used XLFD font specs like so: dmenu_run -b -fn "-*-fixed-bold-*-*-*-18-*-*-*-*-*-*-*" -nb "#0E4D40" -nf "#ffffff" Which is not working properly with the dmenu-4.6 ebuild. It´s possible, that it´s a change from upstream. Now i fixed it by using a Xft font specification like so: dmenu_run -b -fn "fixed:style=bold:pixelsize=18" -nb "#0E4D40" -nf "#ffffff"
Xft is no longer optional in 4.6.