Description of problem: /usr/share/vim/vim72/filetype.vim lists /etc/apache2/*.conf in the config around line 114 instead of the proper RHEL path of /etc/httpd/conf.d/*.conf The standard configs are spelled out by file name as well, but if you add a local file name like for a vhost definition file, the highlighting is broken. Version-Release number of selected component (if applicable): vim-enhanced-7.2.411-1.4.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.yum install vim-enhanced 2.vim /etc/httpd/conf.d/my_custom_file.conf Actual results: Custom File has no syntax highlighting. Expected results: All custom files created in /etc/httpd/conf.d/ should default to httpd syntax highlighting. Additional info: The reference to /etc/apache2/ should be changed to match the F12 and F14 style
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
This couldn't have been rolled into the vim-enhanced-7.2.411-1.6 update? It's an easy/trivial fix.
Can this be addressed please? It's going to celebrate a birthday soon.
Okay, we're into 2012 now. Please can we resolve this? It's an incredibly trivial fix....
The fix is not the problem here, this is about justifying a complete QA cycle for such a minor issue.
That sounds quite a bit like the internal process is broken if fixing a typo requires a complete qa cycle. How about an uprev then to 7.3, which includes better ruby code handling (that also fixes this typo). This can be tied directly to two incubator projects rh has running. Katello, and foreman are both heavily ruby and would benefit from an uprev of vim to include better ruby handlers.
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. http://rhn.redhat.com/errata/RHBA-2012-0454.html