Jorge Almeida <jjalme...@gmail.com> writes:

> On Mon, Dec 19, 2016 at 10:46 AM, lee <l...@yagibdah.de> wrote:
>
>>>
>> I'm using fvwm.  I was having trouble with xterm once when I still used
>> Fedora, and though I'm not sure, results might be different with
>> different WMs (I seem to remember something about that).
>
> I tried fvwm and there was no difference. Not a WM problem. Never
> thought it would be, really.
>
> It is a voodoo (i.e. fonts)  problem. Things work for me now, with -fp
> in the Xserver command line and /usr/share/fonts/Type1/ before
> /usr/share/fonts/misc/. I would prefer to understand what happens
> rather than blindly apply a fix, but anyway.

Does xterm use different fonts for the menu depending on in which order
the directories appear in the font path?


> [...]
>> perl -e 'print "$_\n" foreach(split(/,/, 
>> "/usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/OTF/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,built-ins"));'
>>  | xargs ls
>>
>> ... shows files in each directory, except 'built-ins', of course.
>>
>>
>> That brings up the question if there is some alternative to perls split
>> in coreutils or bash.  The split of coreutils appears to be supposed to
>> be doing something rather useless?
>>
> Well, let's use Perl, by all means :) BTW, what does the busybox version do?

Sure, yet it can't be the only way for doing this.

Reply via email to