FS#23924 - [vim-runtime] Bug in htmlcomplete.vim

Attached to Project: Arch Linux
Opened by I Said Socks (socks) - Monday, 25 April 2011, 03:11 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 21 August 2011, 12:59 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I know this sort of bug should be reported directly to upstream. But I honestly didn't find a bug tracker for vim. So I decided to post it here.

Description:
When editin an HTML file in vim, omni completion produces error on id attribute, if non-existent css file is included. Error message:

Error detected while processing function htmlcomplete#CompleteTags:
line 304:
E121: Undefined variable: classlines

I've also included the one-line patch needed to fix the bug, see attachment.

Additional info:
* vim-runtime 7.3.138-1

Steps to reproduce:

Edit an HTML file in vim. e.g.
vim --noplugin index.html
Include a stylesheet that's not a file, e.g.
<link rel="stylesheet" href="/css/404.css" type="text/css" media="screen" charset="utf-8" />
In insert mode, type <div id=" followed by CTRL-X_CTRL-O
The error message is produced.

P.S. I also use the vim-autocomplpop package from AUR, which automatically request for completions and display them in a popup menu. With this bug, it's very painful to use, since I get interrupted by error immediately when I type anything after id=".
This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 21 August 2011, 12:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  vim-runtime 7.3.266-1
Comment by Thomas Dziedzic (tomd123) - Monday, 25 April 2011, 13:38 GMT
"I know this sort of bug should be reported directly to upstream. But I honestly didn't find a bug tracker for vim. So I decided to post it here."

Here you go: http://www.vim.org/maillist.php#vim-dev
Comment by I Said Socks (socks) - Monday, 25 April 2011, 16:58 GMT
Thanks, mailed the bug/patch.

Poor thing, it doesn't even have a bug tracker.

Loading...