> [sorry for the second mail, I forgot to include the mailing list] Reminds me, my direct replies to you bounce.
On Fri, May 29, 2015 at 01:20:02PM +0200, Andreas Müller <[email protected]> wrote: > I used the "time" bash-builtin to let urxvt run and quit allmost > immediatly: > $ time urxvt -e false that should be good enough. > 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. 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. > > But before crawling into that scary X font stuff too deep, I'll better > just set Urxvt.imfont to fixed or whatever. :) If fixed works for you (it's latin1 only), that should be fine. 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. If you just use xim to get your compose key working or something similar, Root would work perfectly well, of course. Only OverTheSpot and OffTheSpot need a separate xim font because the input method opens a window in these cases. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\ _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
