Analysis updated 2026-07-09 · repo last pushed 2017-09-12
Ensure your whole team uses the same indentation and formatting rules across different editors.
Automatically apply project-specific formatting conventions when opening files in Emacs.
Let open-source contributors follow your project's formatting rules without manual editor configuration.
| jxs/editorconfig-emacs | nohzafk/emacs-workspace-hud | emacs-evil/evil | |
|---|---|---|---|
| Stars | — | 17 | 3,763 |
| Language | Emacs Lisp | Emacs Lisp | Emacs Lisp |
| Last pushed | 2017-09-12 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | hard | easy |
| Complexity | 2/5 | 3/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Install the plugin via MELPA or manually load it, no external EditorConfig program is required due to the built-in fallback.
EditorConfig Emacs Plugin makes your Emacs editor automatically follow consistent formatting rules, like how many spaces to use for indentation, whether to use tabs or spaces, and whether to trim trailing whitespace, based on a simple configuration file checked into your project rather than your personal editor settings. This means a whole team can share the same formatting conventions without anyone needing to manually configure their editor for each project. The way it works is straightforward: a project includes a small file called .editorconfig that lists formatting preferences (like "indent with 4 spaces" or "use Unix-style line endings"). When you open a file in Emacs, this plugin reads that file and adjusts Emacs's settings accordingly for that buffer. The plugin can use an external EditorConfig program if you have it installed, but it also has a built-in fallback written in Emacs Lisp, so it works even without installing anything extra. It supports common rules like indent style, indent size, line endings, character encoding, trailing whitespace trimming, and maximum line length. This is useful for anyone working on a team where people use different editors but need consistent code formatting. For example, if one developer uses Emacs and another uses VS Code, both can read the same .editorconfig file and produce code that follows identical formatting rules. It's also handy for open-source maintainers who want contributors to follow project conventions without writing lengthy setup instructions. One notable detail: the plugin doesn't fully enforce every rule yet. For instance, it can stop Emacs from automatically adding a final newline to files, but it won't remove existing trailing newlines from files that should have none. There's also a customizable hook system that lets you override or extend settings for specific editing modes, useful when a particular Emacs mode has its own indentation behavior that doesn't play nicely with the defaults.
An Emacs plugin that automatically applies your project's shared formatting rules, like indentation style, line endings, and trailing whitespace, whenever you open a file, so your whole team stays consistent without manual setup.
Mainly Emacs Lisp. The stack also includes Emacs Lisp, EditorConfig.
Dormant — no commits in 2+ years (last push 2017-09-12).
You can use, modify, and distribute this software freely, including for commercial use, as long as you include the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.