FS#8461 - [vim 7.1.135] matchparen plugin causes major slow down

Attached to Project: Arch Linux
Opened by Flankk (Flankk) - Tuesday, 30 October 2007, 20:04 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 09 May 2008, 17:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
In Vim, the matchparen plugin is used to match and highligh brackets and parenthesis, even in "normal" mode. Due to the sloppyness in which this plugin is written, it causes a major slowdown while scrolling when editing source code files which include many code blocks. On my machine, Vim CPU usage shoots up to 98% while scrolling with this plugin enabled and only 20% when disabled.

Additional info:
* Vim 7.1.135
* /usr/share/vim/plugin/matchparen.vim

Steps to reproduce:

* Scroll through a large source code file on a lower spec system.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 09 May 2008, 17:11 GMT
Reason for closing:  None
Additional comments about closing:  Upstream issue
Comment by Tobias Kieslich (tobias) - Wednesday, 31 October 2007, 23:52 GMT
As much as I can understand your frustration, I can't see how this possibly can be a packaging issue ...
Comment by Flankk (Flankk) - Monday, 05 November 2007, 23:29 GMT
I am not frustrated at all. All I had to do is disable the plugin and now I have no problems. You can't see how this is a packaging issue? Buggy plugins should not be bundled with the vim package. If I want plugins, they should be installable from seperate packages. If you still don't understand, this would be akin to a package dev including 30 of their favorite plugins in the core firefox package which are enabled by default.
Comment by Tobias Kieslich (tobias) - Wednesday, 13 February 2008, 03:35 GMT
I don't bundle things explicitly with vim, I fetch the current runtime, that the vim people keep uptodate. So pulling in vim from our package base gives you the same, what you would get when you keep vim uptodate by it's very own means of updating because we do use the official aap recipie. If that plugin is buggy, then I agree it should not be part of vims official updates. However that turns it into an upstream issue.

Loading...