public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ryan Johnson <ryanjohn@ece.cmu.edu>
To: cygwin-xfree@cygwin.com
Cc: Jon TURNEY <jon.turney@dronecode.org.uk>
Subject: Re: Missing charsets in String to FontSet conversion
Date: Tue, 03 Aug 2010 15:21:00 -0000 [thread overview]
Message-ID: <4C5833EA.6020002@ece.cmu.edu> (raw)
In-Reply-To: <4C581B24.6050705@dronecode.org.uk>
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/
next prev parent reply other threads:[~2010-08-03 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 8:58 Ryan Johnson
2010-08-03 9:01 ` Thomas Dickey
2010-08-03 13:35 ` Jon TURNEY
2010-08-03 13:46 ` Andy Koppe
2010-08-03 21:31 ` Thomas Dickey
2010-08-03 15:21 ` Ryan Johnson [this message]
2010-08-09 20:12 ` Jon TURNEY
2010-08-09 21:20 ` Ryan Johnson
2010-08-03 15:32 ` Ryan Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5833EA.6020002@ece.cmu.edu \
--to=ryanjohn@ece.cmu.edu \
--cc=cygwin-xfree@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).