[sorry for the second mail, I forgot to include the mailing list] Marc Lehmann wrote: > ... > Incidentally, what exactly are you measuring, and how? I used the "time" bash-builtin to let urxvt run and quit allmost immediatly: $ time urxvt -e false
I ran this with setting all the previously mentioned XIM environment-variables and starting a IME-daemon, and without. > ... > anyways, the best you can do is find out what takes so long on your > system, strace -tttTT or wireshark might be of help. Using strace did only lead me to some readmsg-call to the X-socket. That took most of the time. I didn't get wireshark running yet to maybe decode the msg. Anyhow, it seems I need to either set either Urxvt.preeditmode to Root or Urxvt.imfont to something. That works for me, no more noticeable delays. Before that, I had both unset (or default). 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. I also ran only that piece of code, but couldn't replicate the delay. But before crawling into that scary X font stuff too deep, I'll better just set Urxvt.imfont to fixed or whatever. :) Thanks, Andreas Müller _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
