On Fri, Mar 13, 2015 at 08:25:25AM +0100, Martin Seidl <[email protected]> wrote:
> Which matches Gvim colors to console vim colors. My issue is when
> closing vim with :q it takes 5 or 6 seconds before I'm back to the
> terminal, and during those 5 or 6 seconds the colors change on the
> terminal. The text is still there. Once vim is closed, all the colors
> are normal. If I open xterm with the same vimrc it shuts down
> immediately. If debugged it by disabling various plugins and found that
> csexact was the culprit. So, I opened this issue with csexact:
I didn't look very deeply into this, and I am not a vim-scripter, so my
analysis of csexact might be wrong, but...
Csextract changes the colour palette to the xterm standard palette on
exit, which indeed takes a while on urxvt, and also overriding whatever
colours were configured for urxvt.
It doesn't seem to do that on xterm, which could easily explain why urxvt
is slower - it has to do a lot more work.
This seems to be essentially pointless, as it neither restores the
original colours nor seems to result in useful behaviour, so, while slow,
I don't quite see a reason why this should be sped up (useful behaviour
should be fast, useless behaviour doesn't need to be fast).
To put it differently, csexact seems to have code that essentially
says "be fast on xterm, and do lots of extra pointless work on other
terminals".
The easiest fix would be not to change the colour palette to xterm
standard on exit (remove code from TermResetColors_Defaults).
--
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
