Bug 458508 - vim-common changelog.vim ftplugin is broken in fedora 9
Summary: vim-common changelog.vim ftplugin is broken in fedora 9
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-09 01:07 UTC by Alex Murray
Modified: 2009-07-14 14:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 14:18:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
patch to changelog.vim to fix the bug (422 bytes, patch)
2008-08-09 01:07 UTC, Alex Murray
no flags Details | Diff

Description Alex Murray 2008-08-09 01:07:03 UTC
Created attachment 313859 [details]
patch to changelog.vim to fix the bug

Description of problem: When trying to use the changelog.vim ftplugin, the following error is received when trying to insert a new changelog entry (\o):

Error detected while processing function <SNR>24_new_changelog_entry:       
line   12:
E121: Undefined variable: g:changelog_date_end_entry_search
E116: Invalid arguments for function search(g:changelog_date_end_entry_search, '
W') > 0
E15: Invalid expression: search(g:changelog_date_end_entry_search, 'W') > 0
line   19:
E121: Undefined variable: p
E116: Invalid arguments for function append
line   20:
E121: Undefined variable: p
E116: Invalid arguments for function cursor

This occurs due to a mis-spelled variable name in changelog.vim - it is a simple 1 line change to fix it - will provide a patch.

Version-Release number of selected component (if applicable):
vim-common-7.1.291-1.fc9.i386

How reproducible: every time


Steps to Reproduce:
1. Open a ChangeLog file in vim - changelog.vim ftplugin will be automatically loaded
2. Try inserting a new entry by typing \o in command mode
3. Above error occurs
  
Actual results:


Expected results: No error


Additional info: The attached patch for changelog.vim fixes the problem and has already been committed upstream - see debian changelog for the same fix:
http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/2007-May/003928.html

Comment 1 Bug Zapper 2009-06-10 02:24:45 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-07-14 14:18:38 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.