Vim 8.0保存.php文件耗时过长，求排查配置或插件问题

Hey there, let's break down why saving .php files is taking 5-10 seconds in your Vim 8.0 setup while other file types work fine. Based on the plugins you listed, here are the most likely suspects and how to troubleshoot them step by step:

1. Syntastic #

Syntastic runs code linting automatically when you save files, and for PHP, it typically calls php -l (the built-in PHP syntax checker) under the hood. If your PHP project is large, has complex dependencies, or the linter is taking time to process big files, this can easily add seconds to your save time.

• How to test: Temporarily toggle off Syntastic with :SyntasticToggleMode, then save a PHP file. If the speed improves, you know this is the issue.
• Fixes:
  • Disable auto-check on save and run linting manually instead: let g:syntastic_check_on_save = 0
  • Exclude heavy directories like vendor/ from checks: let g:syntastic_php_exclude_files = ['vendor/**']

2. php.vim #

This plugin handles PHP syntax highlighting, indentation, and folding. For large PHP files, its syntax parsing logic can get resource-heavy, especially if folding is enabled. When you save, Vim might re-parse the syntax to update highlighting, which can slow things down.

• How to test: Temporarily set the filetype to plain text with :set filetype=plaintext, then save. If the save is faster, php.vim is likely the culprit.
• Fixes:
  • Update php.vim to the latest version (newer versions often have performance fixes)
  • Disable syntax folding to reduce parsing load: let g:php_syntax_folding = 0

3. YouCompleteMe (YCM) #

While YCM is mainly for code completion, it runs background code analysis and indexing. When you save a PHP file, it might trigger a re-index of parts of your project. If your project is large (especially with a bloated vendor/ directory), this indexing can hog resources and delay saves.

• How to test: Toggle YCM off with :YcmToggle, then save a PHP file. If speed picks up, YCM is involved.
• Fixes:
  • Configure YCM to exclude unnecessary directories like vendor/ in your .ycm_extra_conf.py file (add flags to ignore those paths)
  • Disable auto-triggered re-indexing if you don't need real-time updates for PHP.

4. EditorConfig #

EditorConfig applies formatting rules from .editorconfig files when you save. If your project has nested directories with multiple .editorconfig files, or the rules are complex (like auto-indent for large files), applying these rules on save can cause delays.

• How to test: Disable editorconfig-vim temporarily with :let g:editorconfig_enabled = 0, then save. If faster, this is the issue.
• Fixes:
  • Simplify your .editorconfig rules for PHP files
  • Ensure you're only applying rules where necessary, avoiding over-nested configurations.

5. Vim Core Configurations #

Don't overlook Vim's own settings that can affect save speed, especially for large files:

• Backup/swap files: Vim creates backup and swap files by default. For large PHP files, writing these can take time. Test by turning them off: set nobackup nowritebackup noswapfile
• Autowrite: If autowrite or autowriteall is enabled, Vim might be saving buffers in the background alongside your explicit save, causing delays. Test with set noautowrite

A quick pro tip: To narrow down the issue faster, start Vim without any plugins using vim -u NONE, then save a PHP file. If it's fast, you know the problem is definitely in one of your plugins—then re-enable them one by one to find the exact culprit.

内容的提问来源于stack exchange，提问作者Ephapox