Cette page est affichée en anglais. Une traduction française est en cours.
ConfigsMay 20, 2026·3 min de lecture

SpaceVim — Community-Driven Modular Vim Distribution

A modular Vim and Neovim distribution that bundles curated plugins, language layers, and a polished UI out of the box, letting developers start with a full IDE-like experience and customize through simple configuration layers.

Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Needs Confirmation · 64/100Policy : confirmer
Surface agent
Tout agent MCP/CLI
Type
Skill
Installation
Single
Confiance
Confiance : Established
Point d'entrée
SpaceVim
Commande CLI universelle
npx tokrepo install 853588cb-53e1-11f1-9bc6-00163e2b0d79

Introduction

SpaceVim is a community-driven Vim distribution inspired by Spacemacs. It provides a pre-configured set of plugins organized into togglable layers, a consistent keybinding system led by the Space key as leader, and a polished status line and start screen. The goal is to give developers a productive Vim-based IDE without manually assembling dozens of plugins.

What SpaceVim Does

  • Organizes plugins into over 100 named layers (e.g., lang#python, git, fuzzy-finder) that can be enabled in a TOML config
  • Provides a mnemonic Space-key-driven keybinding system for discoverability
  • Includes a built-in plugin manager that handles installation, updates, and lazy loading
  • Ships with a tabline, statusline, file tree, and start screen ready to use
  • Supports both Vim and Neovim with a unified configuration format

Architecture Overview

SpaceVim uses a custom Vimscript-based layer system. Each layer defines a set of plugins, keybindings, and configuration functions. The bootstrap process reads ~/.SpaceVim.d/init.toml, resolves layer dependencies, and loads plugins via dein.vim or vim-plug. Layers can declare hooks for before and after loading, allowing complex initialization chains. The UI is rendered using custom Vimscript for the statusline and tabline.

Self-Hosting & Configuration

  • Run the install script or clone the repository to ~/.SpaceVim
  • Create ~/.SpaceVim.d/init.toml to enable layers and set options
  • Enable a language layer with [[layers]] name = "lang#python" syntax
  • Customize keybindings, colorscheme, and font in the [options] section of the TOML file
  • Update SpaceVim and all plugins with :SPUpdate from inside Vim

Key Features

  • 100+ curated layers covering languages, tools, completion, linting, and UI
  • Space-key mnemonic keybindings with a discoverable guide buffer
  • Unified configuration through a single TOML file
  • Built-in file tree, fuzzy finder, and terminal integration
  • Cross-compatible with Vim 8+ and Neovim 0.5+

Comparison with Similar Tools

  • LazyVim — Neovim-only Lua-based distribution; SpaceVim supports both Vim and Neovim
  • NvChad — Focused on speed and minimal defaults; SpaceVim ships more features out of the box
  • AstroNvim — Neovim-specific with a Lua config; SpaceVim uses TOML and Vimscript
  • LunarVim — Opinionated Neovim IDE layer; SpaceVim offers more granular layer control
  • Spacemacs — The Emacs counterpart; SpaceVim brings the same Space-key philosophy to Vim

FAQ

Q: Does SpaceVim replace my existing Vim configuration? A: The install script backs up your existing vimrc. SpaceVim uses its own config directory (~/.SpaceVim.d/) and does not modify your original files.

Q: Can I use my own plugins alongside SpaceVim layers? A: Yes. Add custom plugins in your init.toml under [[custom_plugins]] and they will be managed by the built-in plugin manager.

Q: Is SpaceVim suitable for Neovim with Lua-based plugins? A: SpaceVim works with Neovim but its layer system is Vimscript-based. For a Lua-native approach, consider NvChad or LazyVim.

Q: How do I switch the colorscheme? A: Set colorscheme = "gruvbox" (or any installed scheme) under [options] in your init.toml.

Sources

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires