From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13143 invoked by alias); 3 Aug 2010 15:21:25 -0000 Received: (qmail 13134 invoked by uid 22791); 3 Aug 2010 15:21:24 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from BACHE.ECE.CMU.EDU (HELO bache.ece.cmu.edu) (128.2.129.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Aug 2010 15:21:18 +0000 Received: from [128.178.77.144] (diaspc12.epfl.ch [128.178.77.144]) by bache.ece.cmu.edu (Postfix) with ESMTP id BD095111; Tue, 3 Aug 2010 11:21:16 -0400 (EDT) Message-ID: <4C5833EA.6020002@ece.cmu.edu> Date: Tue, 03 Aug 2010 15:21:00 -0000 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: Jon TURNEY Subject: Re: Missing charsets in String to FontSet conversion References: <4C57DA24.8090205@ece.cmu.edu> <20100803045917.V3933@mail101.his.com> <4C581B24.6050705@dronecode.org.uk> In-Reply-To: <4C581B24.6050705@dronecode.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2010-08/txt/msg00008.txt.bz2 On 8/3/2010 3:35 PM, Jon TURNEY wrote: > 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 The xterm FAQ's workaround (setting LANG=C) indeed works, but then I lose all of UTF-8, including some of the punctuation marks man pages and gcc errors like to use. As I mentioned before, I'd seen references to those fonts but wasn't sure it would actually help me. I just installed them and, sure enough, there's still some (fewer?) missing charsets. The delay dropped to only 2-3 seconds now though, so I guess that helps. Is there a way to diagnose which fonts/charsets are still missing? Regards, Ryan -- 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/