On Thu, May 28, 2015 at 03:41:33PM +0200, Andreas Müller
<[email protected]> wrote:
> A sole "time urxvt -e false" will go from 100ms up to 350ms, which is a
> noticable lag. urxvtc starts almost instantly without IM but takes
XIM is a client/server architecture, it does take some time, and it can
depend (and does depend, mostly) on the speed of the input method, so it
isn't surprising that it takes longer.
For example, if I use kinput2, the difference between not using it
and using it is 0.036s vs. 0.042s for a complete startup + exit of a
standalone instance (and 0.017s vs. 0.009s without perl), while xterm
takes 0.049s for the latter.
Incidentally, what exactly are you measuring, and how?
> xterm takes constanly about 130ms, with or without an IM.
xterms xim support must be very minimal, if it exists at all in my copy
- I couldn't get xterm to work at all with kinput2, and unlike urxvt, it
doesn't support onthespot editing, so altogether it does a lot less, which
might explain the difference.
anyways, the best you can do is find out what takes so long on your
system, strace -tttTT or wireshark might be of help.
> XMODIFIERS="@im=fcitx"
That is all that would be needed (but specifying fcitx it multiple times
shouldn't hurt).
--
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
