No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
If Vim is misbehaving there are some steps that you can follow: |
If Vim is misbehaving there are some steps that you can follow: |
||
| + | =Generic troubleshooting= |
||
| − | |||
==Discard Vim executable== |
==Discard Vim executable== |
||
| − | Run vim -N -u NONE and see if the problem persists. |
+ | Run <tt>vim -N -u NONE</tt> and see if the problem persists. |
| − | * The problem persists. That means the problem could be on the Vim executable. [[#Verify enabled features| |
+ | * The problem persists. That means the problem could be on the Vim executable. [[#Verify enabled features|Verify enabled features]]. |
| − | * The problem went away. [[#Discard vimrc| |
+ | * The problem went away. It is time to [[#Discard vimrc|discard the vimrc]]. |
==Verify enabled features== |
==Verify enabled features== |
||
| Line 14: | Line 14: | ||
==Discard vimrc== |
==Discard vimrc== |
||
| − | Run vim -N --noplugin and see if the problem persists. |
+ | Run <tt>vim -N --noplugin</tt> and see if the problem persists. |
| − | |||
* The problem persists. The reason of your pain is your vimrc. |
* The problem persists. The reason of your pain is your vimrc. |
||
| − | * The problem went away. [[#Discard plugins| |
+ | * The problem went away. The next step is to [[#Discard plugins|discard the plugins]]. |
==Discard plugins== |
==Discard plugins== |
||
| Line 24: | Line 23: | ||
* The problem persists. It looks like the issue is related to a plugin. |
* The problem persists. It looks like the issue is related to a plugin. |
||
* The problem went away. It seems like Vim is running in compatible mode, verify that with :verbose set cp? to also see where it's being set. |
* The problem went away. It seems like Vim is running in compatible mode, verify that with :verbose set cp? to also see where it's being set. |
||
| + | |||
| + | =Specific troubleshooting= |
||
| + | ==Plugins== |
||
| + | ==VIMRC== |
||
| + | ==Mappings== |
||
| + | ==Options== |
||
Revision as of 23:18, 6 September 2011
If Vim is misbehaving there are some steps that you can follow:
Generic troubleshooting
Discard Vim executable
Run vim -N -u NONE and see if the problem persists.
- The problem persists. That means the problem could be on the Vim executable. Verify enabled features.
- The problem went away. It is time to discard the vimrc.
Verify enabled features
Check the feature you need was enabled when Vim was built. Use the :version command to see if said feature is enabled.
- Some/any needed features are disabled. Build Vim with desired feature enabled or use your package manager to install it.
- All needed features are enabled. What to do here?
Discard vimrc
Run vim -N --noplugin and see if the problem persists.
- The problem persists. The reason of your pain is your vimrc.
- The problem went away. The next step is to discard the plugins.
Discard plugins
Run vim -N -u NORC and see if the problem persists.
- The problem persists. It looks like the issue is related to a plugin.
- The problem went away. It seems like Vim is running in compatible mode, verify that with :verbose set cp? to also see where it's being set.