When people have issue where Vim is not working as expected the root cause can (often) be tracked back to
.vimrc (or an outdated / buggy plugin). As people often do not know which part of the rc file is at fault, they think they know, but are wrong, etc. I guess some way to include the users rc file could be looked at.
However, as these files can be rather big, it is in danger of cluttering up the question. Question is if there should / could be some sort of include feature. Typically either:
- Some way to add the file as an attachment. (Typically a line at bottom of question with a link to a paste-like site, or as direct attachment - (served as text file so that one can open directly in browser).
- Something like the collapsible code blocks on StackOverflow. “Click to view”
- Some other / better way ...
I am not sure how much this is going to be an issue. Depends largely on how many of these questions one get.
Without the config file one could end up with (a lot?) of questions where one have a wall of comments like; “Do you have this in your .vimrc”?, “Do you have that in you .vimrc”, and answers taking the form of “If you have this or that in your .vimrc or that and this is in wrong order or ... that could explain what you see.”
Would such a feature be in good? If so, then what format?
My thought was more in the lines of what mentioned by aharris88 plus various. But more thought on the topic, and a Q/A here – and a read-trough on questions posted thus far, I believe the issue is close to being unemployed.
Not saying it won't arise as a valid issue, but can't, thus far, see a valid reason for leaving this open. As such I accept the highest voted and leave it there.
To emphasize; read: How do I debug my vimrc file?