mattn/emmet-vim

emmet for vim: http://emmet.io/

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 10th, 2026
Created on February 18th, 2010
Open Issues & Pull Requests: 132 (+0)
GitHub issues: Enabled
Number of forks: 414
Total Stargazers: 6,465 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 4.6 days
90th percentile: 11.8 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Emmet-vim is a Vim plugin that provides support for expanding abbreviations similar to Emmet.

The plugin solves the problem of writing repetitive HTML, CSS, and JavaScript markup by allowing developers to type shorthand abbreviations and expand them into full code structures. For example, typing "html:5" and pressing the trigger key generates a complete HTML5 document template. The expansion works by interpreting Emmet syntax, which uses a compact notation to describe nested elements, attributes, and content that can be rapidly converted into properly formatted markup.

Developers working primarily with HTML and CSS in Vim should consider this tool, particularly those who value keyboard-driven workflows and want to reduce boilerplate typing. The plugin can be configured to enable Emmet only in specific file types or modes rather than globally, and the default trigger key can be remapped. For developers who want to extend functionality beyond the built-in snippets, the tool supports custom snippet definitions through a JSON configuration file when the web-api dependency is installed. This allows teams to standardize their markup patterns across projects.

The project maintains steady engagement with bug fixes and feature requests addressed through pull requests and issues. Development activity shows consistent responsiveness to user-reported problems and compatibility concerns. The codebase remains actively maintained with updates addressing edge cases and Vim configuration compatibility issues.