4

My vim is very slow to switch tabs (:tabnext) when i've fullscreened my terminal (1920x1200).

Does anyone have a fix for this? Is it a vim issue, or is it my setup? Redrawing a black terminal (gnome-terminal) with a bit of text shouldn't be that hard.

Joernsn
  • 2,319
  • 4
  • 25
  • 33

1 Answers1

4

It is probably the gnome-terminal problem. Vim with my fullscreen (1920x1080) rxvt-unicode (urxvtc) terminals works just fine.

ZyX
  • 52,536
  • 7
  • 114
  • 135
  • 1
    Correct. Switched to urxvt and used http://www.saltycrane.com/blog/2009/11/how-make-urxvt-look-gnome-terminal/ to make the transition easier. :) – Joernsn May 20 '10 at 12:19
  • Can you clarify what "the gnome-terminal problem" is? – LondonRob Oct 24 '14 at 13:52
  • @LondonRob No idea. But when Vim switches to the next tab it redraws entire screen which puts higher then usual load. – ZyX Oct 30 '14 at 22:48
  • @Zyx but redrawing a single screen of console window shouldn't take a noticeable amount of time should it? – LondonRob Oct 31 '14 at 11:57
  • @LondonRob Have you ever worked with `` non-framebuffer terminal? This depends purely on implementation. I know that vte-based terminals are sometimes reported as slow and I know that Vim has to redraw the entire screen when switching tabs. I can’t say that it’s exactly what culprit is, but it seems to be the most likely problem, especially given the fact that tabs were introduced in vim-7.0 when Vim was usually used in faster terminal emulators (so less requirements were put onto code drawing efficiency). You can write a “Hello World” which eats 100% CPU for a few minutes if you want. – ZyX Oct 31 '14 at 18:17
  • @LondonRob I am wrong: slow `` I saw in GRML, and GRML uses framebuffer. – ZyX Oct 31 '14 at 18:18