Instead of liuchengxu/vim-which-key, i'd strongly recommend using https://github.com/folke/which-key.nvim
Reasons:

• Written and configured in lua - Lua API means nicer API in fennel in addition to the performance gains
• Support for mapping keys to functions directly - no more <cmd>lua something()<cr> on the right side of mappings
• Support for showing the contents of registers and marks directly
• Folke is super active, and all of his plugins are amazing - Active and epic maintainers are always a plus

On a new Windows install, I installed neovim using scoop and put magic-kit's init.lua in the AppData folder so neovim can load it. It errors out with:

 C:\Users\gebruiker\AppData\Local\nvim-data\site\pack\packer\start\aniseed\plugin\aniseed.vim:
line   2:
Parse error in C:/Users/gebruiker/AppData/Local/nvim/fnl\magic\init.fnl:1
  Invalid string: "C:/Users/gebruiker/AppData/Local/nvim/fnl\magic\init.fnl"
(module magic.init
-----------------------------------------------------------------------^
Parse error in C:/Users/gebruiker/AppData/Local/nvim/fnl\magic\keybindings.fnl:1
  Invalid string: "C:/Users/gebruiker/AppData/Local/nvim/fnl\magic\keybindings.fnl"
(module magic.keybindings
------------------------------------------------------------------------------^
E5108: Error executing lua ...a\site\pack\packer\start\aniseed\lua\aniseed\compile.lua:131: Could not open file: C:/Users/gebruiker/AppData/Local/nvim/lua\magic\macros.fnl: No such file or directory

Looking at the string it has to do with path handling but I thought that was solved with: Olical/aniseed@ab8ef06

The existing config systems that packer exposes seem to always load things too late / async which means you can't set things before the plugins are loaded. We need a simple and obvious way to load plugin config as early as possible.

Hey, @Olical. I'm playing with this repo, it's very cool config to start from. However I've been experiencing constant screen flickering during cursor movements, disabling which-key setup (remove :mod) solves this completely. I wonder what is the real reason for this issue.

After cloning this repo (which is great by the way; thanks!) to make a brand new nvim config, I noticed that if I opened a .janet file I did get syntax highlighting but ConjureConnect wouldn't work.

After installing janet.vim everything worked correctly. Maybe it would be a good idea to add it as one of the pre-packaged plugins? Or add a note about it in the readme.