diff options
| author | eltrac <hi@eltr.ac> | 2026-07-04 12:05:29 +0800 |
|---|---|---|
| committer | eltrac <hi@eltr.ac> | 2026-07-04 12:05:29 +0800 |
| commit | fec4db6af6373e4bc0807681f4dded3d9f6e0cb1 (patch) | |
| tree | 97457a6fbd7ad9422a4b847ef9623b88ee357dd9 | |
| parent | 9b999105546b39172ce70269d8441a02e01c2b08 (diff) | |
add README.md
| -rw-r--r-- | README.md | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/README.md b/README.md new file mode 100644 index 0000000..495a897 --- /dev/null +++ b/README.md @@ -0,0 +1,23 @@ +## 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](https://babashka.org/) 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 + |