Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1112441

Summary: [RFE] update vim syntax file for git with new keywords
Product: Red Hat Enterprise Linux 6 Reporter: Evgueni Souleimanov <esoule>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED ERRATA QA Contact: Filip Holec <fholec>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: dkutalek, psplicha, rvokal, tlavigne
Target Milestone: rcKeywords: EasyFix, FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:27:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch that changes the whitespace inside syntax files to match vim-7.4
none
patch that brings new keywords into vim syntax file for git, from vim-7.4
none
modifications to vim.spec to integrate new patches to syntax files none

Description Evgueni Souleimanov 2014-06-24 00:57:29 UTC
Description of problem:

New git versions have new keywords in interactive rebase: fixup, reword, exec. Current git syntax file in vim does not highlight them.

Version-Release number of selected component (if applicable):

vim-enhanced-7.2.411-1.8.el6

How reproducible:


Steps to Reproduce:
1. git rebase --interactive COMMIT_ID
2. type "fixup" or "reword" instead of "pick", or add a line with "exec" keyword
3.

Actual results:

Keywords are not highlighted

Expected results:

Keywords are highlighted

Additional info:

vim-7.4 has updated syntax files for git. Patches to bring them to vim-7.2 are attached.

Comment 1 Evgueni Souleimanov 2014-06-24 00:58:33 UTC
Created attachment 911607 [details]
patch that changes the whitespace inside syntax files to match vim-7.4

Comment 2 Evgueni Souleimanov 2014-06-24 00:59:20 UTC
Created attachment 911608 [details]
patch that brings new keywords into vim syntax file for git, from vim-7.4

Comment 3 Evgueni Souleimanov 2014-06-24 01:02:54 UTC
Created attachment 911609 [details]
modifications to vim.spec to integrate new patches to syntax files

Comment 11 errata-xmlrpc 2015-07-22 06:27:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1310.html