1
0
Fork
You've already forked vimulti
0
Split your (Neo)vim config and use specialized instance for each use case!
  • Clojure 100%
2026年07月06日 11:42:28 +08:00
.gitignore gitignore: ignore local cache and nREPL port 2026年07月04日 10:58:30 +08:00
bb.edn set up project bb.edn 2026年07月04日 11:49:58 +08:00
README.md add README.md 2026年07月04日 12:05:29 +08:00
vimulti.clj fix: unable to get current branch 2026年07月06日 11:42:28 +08:00
vimulti.edn support local config 2026年07月06日 11:13:43 +08:00

Vimulti

I'm crazy and I maintain multiple Neovim configurations. Most of the time I code in a pleasant language where a simple setup can do the job right. Sometimes I have to code in, well, Java, but I refuse to install anything like Intellij IDEA. So I forked my own configuration and made a Java edition.

Vimulti does one simple thing. Suppose your Neovim configuration is a Git repository, and you have different versions of it on different branches. You run vimulti <branch> ..., and this happens:

  1. Your repository is switched to that branch.
  2. Your editor opens up, using that configuration.
  3. You :wq, and the branch is switched back.

Setup

  1. Make sure you have Babashka installed.
  2. git clone https://codeberg.org/eltrac/vimulti.git
  3. Add alias vimulti="bb /path/to/vimulti/vimulti.clj" to your .zshrc or something like that
  4. Add more aliases of certain versions, e.g. alias vimj="vimulti java-edition"

Roadmap

  • Switch configurations across repositories
  • Use configuration from a remote git repository URL
  • Install script