dotfiles-nvim VS hibiscus.nvim

Well it certainly doesn't know what to do with my nvim dotfiles since I use fennel for it all

Yes, the init.fnl is here

Dotfiles themselves if it helps get the layout across

I use fennel for all my Neovim stuff (besides whatever plugins I contribute to ofc). Obligatory dotfiles

Config in fennel

Configs if interested

Example from me: fzf command customized previewer source previewer

Here's my dotfiles if it helps at all. Written with Aniseed

That's where Kreative comes into play. Built off the backbone of kat.nvim, Kreative is designed to be as end user focused as possible. Absolutely no code knowledge is needed, simply create an appropriate file in /colors in your config for the colors you want, and Kreative will handle the rest when you set your colorscheme to it. An expanded file should only be 16 lines of Lua, most of that expanded table values. Just look at this example, 19 lines even with expansion and empty lines! Just input 8 colors, and you're off

local function bootstrap(url, ref) local name = url:gsub(".*/", "") local path = vim.fn.stdpath [[data]] .. "/lazy/" .. name if vim.fn.isdirectory(path) == 0 then print(name .. ": installing in data dir...") vim.fn.system { "git", "clone", url, path } if ref then vim.fn.system { "git", "-C", path, "checkout", ref } end vim.cmd [[redraw]] print(name .. ": finished installing") end vim.opt.runtimepath:prepend(path) end bootstrap("https://github.com/udayvir-singh/tangerine.nvim") -- Optional and only needed if you also want the macros bootstrap("https://github.com/udayvir-singh/hibiscus.nvim") require 'tangerine'.setup { target = vim.fn.stdpath [[data]] .. "/tangerine", -- compile files in &rtp rtpdirs = { "ftplugin", }, compiler = { -- disable popup showing compiled files verbose = false, -- compile every time changes are made to fennel files or on entering vim hooks = { "onsave", "oninit" } }, }

I can recommend using Fennel with Tangerine (integration) and Hibiscus (macros). My config here for inspiration.

For ease of use, you can use conjure for evaluating the code, cmp-conjure for nvim completions, hibiscus.nvim and nyoom.nvim macros for macros, and you can also use nyoom.nvim as a base config.

Hibiscus.nvim:

local function bootstrap (name, url, path) if vim.fn.isdirectory(path) == 0 then print(name .. ": installing in data dir...") vim.fn.system {"git", "clone", "--depth", "1", url, path} vim.cmd [[redraw]] print(name .. ": finished installing") end end bootstrap ( "tangerine.nvim", "https://github.com/udayvir-singh/tangerine.nvim", vim.fn.stdpath "data" .. "/site/pack/packer/start/tangerine.nvim" ) bootstrap ( "hibiscus.nvim", "https://github.com/udayvir-singh/hibiscus.nvim", vim.fn.stdpath "data" .. "/site/pack/packer/start/hibiscus.nvim" ) require'tangerine'.setup{ compiler = { verbose = false, hooks = { "onsave", "oninit" } } }

Fennel with hibiscus:

But, you can use another plugin of mine Hibiscus which contains bulk of zest and aniseed macros.