Marc Lehmann wrote: > > [sorry for the second mail, I forgot to include the mailing list] > > Reminds me, my direct replies to you bounce. I'm sorry, what do you mean? I got your mails and I don't have any blocking/bouncing rules in place but the Reverse-DNS/Dialin-IP/Spamhaus checks of my hoster. And I do not have access to the mail-logs but if you would provide the bounce-message, I'll look into it. > > > So I guess it's the XCreateFontSet() in src/main.C:1470. > > I timed that call with gettimeofday() and confirmed that call took > > most of the time. > > Thats indeed due to your input method then (and/or your settings, if you > or your distribution has provided any). > > Unless disabled (or not supported by the input method), urxvt will default > to onthespot editing, which will be using the normal font(set) that the > terminal uses. Ah, thanks, I unknowingly had it disabled because I disabled perl. OnTheSpot works like a charm now, and it's fast as well. > > Although while XCreateFontSet is a comparatively slow operation, it does > take really a long time on your system - it takes 0.02s here, and while > I don't have all of debians fonts installed, I have a lot of them for > testing purposes. > > > I also ran only that piece of code, but couldn't replicate the delay. It seems that it has to do with locale-settings. After using setlocale() with an UTF-8 locale in my test program I can reproduce the delay. And maybe my font collection maybe of course, although I tried to limit it. xfontsel shows about 1300 matches for "*" pattern, incidently it shows also starts with a delay with my utf8 locale, but not with the "C" locale.
Maybe has something to do with this old X bug: https://bugs.freedesktop.org/show_bug.cgi?id=4939 > An alternative could be OnTheSpot, which is usually much nicer to use, and > doesn't require a separate font at all, while supporting any character > urxvt supports in your configuration. Right, OnTheSpot was what I really wanted anyway. > Only OverTheSpot and OffTheSpot need a separate xim font because the input > method opens a window in these cases. Still, wouldn't the input method need some info where the cursor is for displaying the selection list (the match your input to e.g. kanji)? Because, that list is now under the window, it's OK though. Have a nice weekend, Andreas Müller _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
