github github
star 166
alert-circle 2
open issues
users 7
git-branch 24



15 hours ago



Stars GitHub Issues Forks License

These are your father's parentheses.
Elegant weapons for a more... civilized age.
— xkcd/297

This config was a response to new configs that pop up, with very abstracted and complex codebases, such as NvChad. They try to be a one-size-fits-all config. NvChad and LunarVim both try to fit as much overall functionality as possible and needlessly lazy load everything, when it really isn't needed. Complex codebases lead to less freedom for end-user extensibility. Try forking NvChad and making your own configuration out of it. Everything is tied to the userConfig, and you rely on the maintainer of said code to implement features.

Nyoom.nvim provides a solution to these problems by providing only the necessary code in order to make a functioning configuration. The end goal of nyoom.nvim is to be used as a base config for users to extend and add upon, leading to a more unique editing experience. Its relatively small and simple, offers the bare minimum needed plugins to have a powerful config, and is suited to my needs, but can just as easily be suited to yours!

I recommend not to clone and directly install this config, but to fork it, inspect the code, and adjust it to your liking. The best neovim configuration is what you make, and this config is only supposed to provide you the tools to do so.



The only dependencies are neovim-nightly and git.


Install the following dependencies:

  • neovim-nightly (or neovim stable)
  • rust/cargo (to build parinfer-rust)
  • ripgrep (optional, for telescope)
  • nodejs (optional, for copilot)
  • fennel + fnlfmt (not required, but recommended)
  • font with nerdfont icons
    git clone --depth 1 ~/.config/nvim 
    If you're using hotpot (default), enter neovim, exit neovim, enter it again, then run :PackerSync. (The restart is nessecary for neovim to load the newly compiled code). If you're using tangerine, run :FnlCompile!, then run :PackerSync

Using nix:

Requires nix version > 21.11, with experimental features flakes and nix-commands enabled

git clone --depth 1 && cd nyoom.nvim
nix develop

Then run nvim as usual, and :PackerSync to update/install plugins


Nyoom.nvim is designed against the mantras of doom-emacs: (shamelessly copy pasted)

  • Gotta go fast. Startup and run-time performance are priorities.
  • Close to metal. There's less between you and vanilla neovim by design. That's less to grok and less to work around when you tinker.
  • Opinionated, but not stubborn. Nyoom (and Doom) are about reasonable defaults and curated opinions, but use as little or as much of it as you like.
  • Your system, your rules. You know better. At least, Nyoom hopes so! There are no external dependencies (apart from rust), and never will be.

It also aligns with many of Doom's features:

  • Minimalistic good looks inspired by modern editors.
  • A modular organizational structure for separating concerns in your config.
  • A standard library designed to simplify your fennel bike shedding.
  • A declarative package management system (inspired by use-package, powered by Packer.nvim). Install packages from anywhere, and pin them to any commit.
  • A Space(vim)-esque keybinding scheme, centered around leader and localleader prefix keys (SPC and SPCm).
  • Project search (and replace) utilities, powered by ripgrep, and telescope.

However, it also disagrees with some of those ideals

  • Packages are not pinned to commits by default. Unlike Doom, this configuration includes fewer than 20 packages by default and breaking changes are usually few and far between. Everything is rolling release, and if a breaking change does occur I will push a fix within a day (pinky promise!). Of course, you are free to pin packages yourself (and use :PackerSnapshot).


  • David Guevara For getting me into fennel, and for some of his beautiful macros. Without him Nyoom wouldn't exist!
  • Oliver Caldwell For his excellent work on Aniseed, Conjure, and making fennel feel like a first class language in neovim


v0.3.4 - Released 5/22/2022

  • Colorscheme: Automatically changes based on vim.opt.background. Light palette added
  • Macros: Added event/command macros. Minor adjustments to packer macros
  • Bindings: Small fix for normal-mode bindings
  • Loading: Fixes to bootstrapping and loading order. Defer lsp/lspinstaller. Add option to use tangerine.nvim
  • Lsp: Add nvim-lsp-installer. Cleanups
  • Packer: Automatically compile & require compiled file from within pack.fnl.

v0.3.3 - Released 5/14/2022

  • Colorscheme: Rewrite in fennel + macros using nvim api
  • Macros: Rewrite of options macros. Replace keymap macros with which-key
  • Bindings: Conjure/hotpot/fennel compilation and evalulation. Use Which-Key
  • Treesitter/Loading: Fixes for ts-rainbow, telescope.nvim
  • Lsp: Add lsp-signature, improve loading and fix fidget
  • Packer: Cleaned up implementation

v0.3.2 - Released 5/08/2022

  • removed nvim-parinfer and wrote fennel version based on ffi + parinfer-rust. (sidenote: I love how easy neovim makes this, back when I started vim learning enough vimscript to do this was a pipe dream. Long live lua! (and fennel))
  • WIP Treesitter + matchparen speed improvements
  • Properly configured nvimtree
  • Nvim-bufferline integrations
  • Minor defs/fillchars/lsp/cmp updates
  • Macro updates and optimizations

v0.3.1 - Released 5/03/2022

  • More fennel! Init is rewritten in fennel (update: This caused the config to load after runtime files, which meant that filetype.lua stopped working. I've sinced reverted back to init.lua for now), and lua dependencies (md5 lib) were removed.
  • Refactored the entire config. New directory structure, parted out macros, and cleaned up code.
  • Statusline has been added! Thin and light global statusline to align with nyoom's philosphies.
  • Lsp/Cmp configs have been re-done. Lsp is now much quicker to load and is a much cleaner implementation. Cmp is much quicker, integrates properly with copilot, and everything was reworked from the ground up.
  • Improved highlighting macros: Highlights are now applied via nvim_set_hl.
  • Improved startuptime by 20-30ms: decreased lazy loading and optimized code.
  • Improved keybinding support: macros for buffer-local mappings and which-key documentation have been added. Nyoom default bindings are now documented within which-key
  • Improved treesitter integration. Textobjects and support for conjure evaluation using treesitter have been added.


Fast loading and package management using Nyoom! macros and Packer.nvim

Lispy editing using conjure parinfer-rust

Lightweight statusline written in fennel

Note-taking and Getting Things Done with neorg

Syntax highlighting and Error checking with Neovim's builtin LSP, lspconfig, trouble.nvim and nvim-treesitter.


Quick Completion and Wildmenu powered by nvim-cmp and copilot.lua

Pretty notifications and focused editing using TrueZen and nvim-notify

Informative Keybinds, Native Fuzzy Finding, and fast file history using nvim-telescope, telescope-fzf-native.nvim, telescope-frecency.nvim, sqlite.lua and which-key.nvim

Themeing with nvim-base16 and base16-carbon-dark

Magit-like commits with Neogit

Why fennel?

Fennel is a programming language that brings together the speed, simplicity, and reach of Lua with the flexibility of a lisp syntax and macro system. Macros are how lisps accomplish metaprogramming. You’ll see a lot of people treat lisp macros with a kind of mystical reverence. While several other languages have macro systems, the power of macros in lisps stem from allowance of lisps to you to write programs using the same notation you use for data structures. Remember: code is data, and we just need to manipulate data.

While people largely over exaggerate the usefulness of macros, there are a few places where macros shine, and configurations are one of them. Utilizing macros, we can essentially create our own syntax. For example, lets take a look at the set! macro I've used. set! is used for vim.opt options. For example, (set! mouse :a) expands to vim.opt["mouse"]="a". If a string or number isn't passed to set!, it will assume true. e.g. (set! list) will expand to vim.opt["list"]=true. Similarly if the option starts with no, it will assume false e.g. (set! noru) will expand to vim.opt["ru"]=false.

With the macros provided, you can configure neovim just as easily, or dare I say easier than you can with Lua or vimscript, while retaining the performance benefits of LuaJIT.

All the magic happens in the fnl/ folder. Some files to check out:

  • init.fnl: Same as your init.lua would be, just in fennel! Disables some plugins and loads the core config
  • pack/: This is where all your plugins go. The pack.fnl file is in charge of configuring packer, installing, as well as loading plugins
  • core/defs.fnl: This is where neovim settings go.
  • core/maps.fnl: This is where mappings go.
  • macros/: In lisps, macros allow the user to define arbitrary functions that convert certain Lisp forms into different forms before evaluating or compiling them. This folder contains all the macros that I (and a few others, thanks David and Kat!) have written to help you out on your neovim journey. I don't recommend touching this file unless you know what you're doing

Learning Fennel

For most people, chances are you haven't even heard of fennel before. So where should you start?

  1. Read through the Documentation
  2. Install fennel yourself! (Skip the part where it goes over adding fennel support to your editor, that's what this project is for :p)
  3. Learn lua first. I recommend reading through the Neovim lua guide as well.
  4. Learn fennel
  5. Go over the Style guide.
  6. Learn macros.

If you have trouble configuring neovim to your needs, check out Antifennel to see how lua code compiles back to fennel! However, the generated code isn't always the cleanest, so its recommend you use it as a last resort. If you need any help, feel free to reach out to me via email or discord, and be sure to join the Conjure Discord too!

When Fiddling with Fennel Code

While fiddling with the config, you can check if the things are not broken yet:

  1. evaluate form you just written (<localleader>er, by default <space>mer)
  2. evaluate buffer (<localleader>eb, by default <space>meb)
  3. start another neovim with a vim command: :!neovim --headless +PlugSync


If you have an issue with a plugin in Nyoom.nvim, first you should report it to Nyoom.nvim to see if it's an issue with it. Please don't bother package maintainers with issues that are caused by my configs, and vice versa. I'm new to fennel, so don't hesitate to let me know my lisp-fu sucks!