First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 82789
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Vim Maintainers <vim@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jim Cole <gentoo@yggdrasill.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 82789 depends on: Show dependency tree
Bug 82789 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-02-21 03:12 0000
There are syntax errors in vimfiles/ftdetect/gentoo.vim
(gentoo-syntax-20041227) that derail correct handling of XML files. One result
of this problem is that marks for jumping to the previous location in an XML
file are not processed correctly when a file is reopened. Instead the cursor
always jumps to the default position.

Reproducible: Always
Steps to Reproduce:
1. Open a generic XML file (with .xml extension).
2. Move to some location in the middle of the file.
3. Close the file.
4. Reopen the file.

Actual Results:  
The cursor was positioned at the top of the file.

Expected Results:  
The cursor should have been located at its previous position somewhere in the
middle of the file.

The problem appears to be in the handling of the guidexml filetype at the
bottom
of the gentoo.vim file in the ftdetect directory. This code is lacking both a
final command separator and the closing 'endif'.

This problem did not occur until moving to gentoo-syntax-20041227.

------- Comment #1 From Aaron Walker (RETIRED) 2005-02-21 05:58:20 0000 -------
HEH! no wonder newmetadata.vim wouldn't work...

Fixed upstream.

------- Comment #2 From Ciaran McCreesh 2005-02-21 08:25:52 0000 -------
Woah, how the heck did we miss that?

20050211-r1 includes the fix...

First Last Prev Next    No search results available      Search page      Enter new bug