Missing charsets in String to FontSet conversion

[Jon TURNEY]

On 03/08/2010 10:00, Thomas Dickey wrote:
> On Tue, 3 Aug 2010, Ryan Johnson wrote:
>> At some point an annoyance appeared with my xterm windows: The first time I
>> use [ctrl]+mouse click in any window, that xterm becomes unresponsive for
>> about 5 seconds with the CPU pegged to 100%. After the five seconds is up,
>> whatever shell spawned the xterm receives the following message:
>>> Warning: Missing charsets in String to FontSet conversion
>>
>> After that all works normally (until I open the next xterm window).
>>
>> Is there a way to diagnose what the problem is? I don't know what FontSet
>> string the error even refers to, let alone which parts of that string were
>> invalid. In any case, it really shouldn't take five seconds of hard CPU
>> crunching to detect and report an invalid input string.

There's some more discussion at
http://sourceware.org/bugzilla/show_bug.cgi?id=10948

Installing the fonts font-isas-misc, font-jis-misc and font-daewoo-misc should 
also work around the problem, which can also be seen with other applications, 
as that ensures that at least one font exists for every charset.

I agree that the error message sucks and should tell you the charsets which 
are missing and what string it was attempting to convert.

> This topic came up last year, iirc the issue was this:
>
> http://invisible-island.net/xterm/xterm.faq.html#slow_menus

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/