Bug 1118044 - Vim does not recognize custom directories in RUNTIMEPATH (rtp)
Summary: Vim does not recognize custom directories in RUNTIMEPATH (rtp)
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 20
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-09 21:55 UTC by David Levner
Modified: 2015-06-29 21:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 21:32:21 UTC
Type: Bug

Attachments (Terms of Use)
A slightly more complete filetype.vim than the one described in the bug description. (128 bytes, text/plain)
2014-07-09 21:55 UTC, David Levner
no flags Details

Description David Levner 2014-07-09 21:55:02 UTC
Created attachment 916957 [details]
A slightly more complete filetype.vim than the one described in the bug description.

Description of problem:

I added a directory to my RUNTIMEPATH but vim ignores the change.

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


How reproducible:

Every time

Steps to Reproduce:
1. Add a directory to RUNTIMEPATH by appending the line 'set runtimepath+=~/programs/vim' to ~/.vimrc. The directory ~/programs/vim should already exist. You can use any directory that is not already in RUNTIMEPATH.

2. Create a file named filetype.vim in the additional RUNTIMEPATH directory.

3. In the new file filetype.vim, insert the following lines:

augroup autodetect
  au! BufRead,BufNewFile *.ish setfiletype perl
augroup END

4. Run 'vim any.ish' from a shell command line.

5. Type ':echo &filetype' in vim.

Actual results:


Expected results:


Additional info: 

I suspect this problem is caused by the somewhat out-of-date version of vim on Fedora 20, 7.4.179. On a BSD system that I use which has vim 7.4.205, the problem does not occur. Could a more recent version of vim be made available for Fedora 20 via yum update?

There are work-arounds with vim 7.4.179, but I prefer a clean solution.

Comment 1 Fedora End Of Life 2015-05-29 12:20:12 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 2 Fedora End Of Life 2015-06-29 21:32:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

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.