public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Thomas Dickey <dickey@his.com>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: Missing charsets in String to FontSet conversion
Date: Tue, 03 Aug 2010 09:01:00 -0000 [thread overview]
Message-ID: <20100803045917.V3933@mail101.his.com> (raw)
In-Reply-To: <4C57DA24.8090205@ece.cmu.edu>
On Tue, 3 Aug 2010, Ryan Johnson wrote:
> Hi all,
>
> 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.
This topic came up last year, iirc the issue was this:
http://invisible-island.net/xterm/xterm.faq.html#slow_menus
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
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 9:01 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 [this message]
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
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=20100803045917.V3933@mail101.his.com \
--to=dickey@his.com \
--cc=cygwin-xfree@cygwin.com \
/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).