Bug 1045815

Summary: vi and its family should not read ~/.vimrc
Product: [Fedora] Fedora Reporter: kealthou
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: karsten, lemenkov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 10:02:03 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:

Description kealthou 2013-12-22 09:18:51 UTC
Description of problem:
If there is "set foldmethod=marker" in $HOME/.vimrc, view can't interpret it, and it outputs an error message. I'm not sure whether view should interpret it, or view, which is a symlink of vi, should ignore $HOME/.vimrc. In terms of system-wide configurations, vim and vi have its own one and don't share them with each other, /etc/vimrc and /etc/virc respectively. I think the same naturally goes to user configurations.

Version-Release number of selected component (if applicable):
vim-minimal-7.4.027-3.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. echo "set foldmethod=marker" >> ~/.vimrc
2. view

There are many other options and commands that view don't understand. If you have your own .vimrc already, just running view is most likely enough to see error messages.

Actual results:
Error detected while processing /home/kei/.vimrc:
line    1:
E518: Unknown option: foldmethod=marker
Press ENTER or type command to continue

Expected results:
No error messages appear.

Comment 1 Peter Lemenkov 2014-04-07 10:12:12 UTC
This issue is still exists in Fedora 20.

work ~: rpm -qa "vim*"
vim-enhanced-7.4.179-1.fc20.x86_64
vim-common-7.4.179-1.fc20.x86_64
vim-minimal-7.4.179-1.fc20.x86_64
vim-filesystem-7.4.179-1.fc20.x86_64
work ~:

Comment 2 Fedora End Of Life 2015-01-09 20:56:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 3 Fedora End Of Life 2015-05-29 10:06:28 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 4 kealthou 2015-06-04 14:56:04 UTC
To make it specific, I changed the summary.

Comment 5 Karsten Hopp 2016-04-13 10:02:03 UTC
This will be fixed in 7.4.1718-2