editorconfig/editorconfig-vim

EditorConfig plugin for Vim

View on GitHub ↗Jump to charts ↓

editorconfig/editorconfig-vim has 3k+ stars and 100+ forks on GitHub, is written in Vim Script, and was last pushed on Mar 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 8 minutes ago
Type:Plugin / ExtensionCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on October 13th, 2011
Open Issues & Pull Requests: 44 (+0)
GitHub issues: Enabled
Number of forks: 142
Total Stargazers: 3,169 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.4 hours
Mean response time: 33.7 days
90th percentile: 171.9 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,347 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Bug (4)
  • support (2)
  • Enhancement (1)
  • need info (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

editorconfig-vim is a Vim plugin that brings EditorConfig support to the editor.

EditorConfig is a specification for maintaining consistent coding styles across different editors and projects through a shared configuration file. The plugin reads .editorconfig files from your project and applies the defined settings automatically within Vim, eliminating the need to manually configure indentation, line endings, character encoding, and other style properties for each project you work on. This approach works by parsing the EditorConfig file hierarchy and applying properties like indent_style, indent_size, end_of_line, charset, and trim_trailing_whitespace directly to your Vim session.

The plugin suits developers working on teams or projects that already use EditorConfig, or those who want to enforce consistent formatting rules across multiple projects without maintaining separate Vim configuration files. It is particularly valuable in polyglot codebases where different file types need different formatting rules, since EditorConfig handles this through pattern matching in a single configuration file. If your project does not yet use EditorConfig, adopting the plugin requires first creating an .editorconfig file at your project root, but this investment pays dividends across all editors your team uses.

The project maintains a straightforward focus on the core plugin functionality without unnecessary complexity. Development activity shows consistent engagement with issues and pull requests, indicating that the maintainers respond to user reports and contributions. The codebase remains stable and well-integrated with Vim's plugin ecosystem, suggesting reliable long-term maintenance.