dotfiles-nvim
hotpot.nvim
dotfiles-nvim | hotpot.nvim | |
---|---|---|
11 | 16 | |
12 | 332 | |
- | - | |
3.3 | 9.3 | |
5 months ago | about 1 month ago | |
Clojure | Fennel | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles-nvim
-
Introducing dotfyle.com: discover and share neovim configs
Well it certainly doesn't know what to do with my nvim dotfiles since I use fennel for it all
- vimscript over lua
-
lazy.nvim and Aniseed for config environment
Yes, the init.fnl is here
-
Which structure of neovim config files do you prefer? (Diagrams incluced)
Dotfiles themselves if it helps get the layout across
-
Swapping to Fennel
I use fennel for all my Neovim stuff (besides whatever plugins I contribute to ofc). Obligatory dotfiles
-
Share your neovim dashboard. (dashboard-nvim, startify, etc.)
Config in fennel
-
Fennel configs - What have your experiences been? What library are you using and why?
Configs if interested
-
Can You Share Your nvim-fzf Key Bindings?
Example from me: fzf command customized previewer source previewer
-
Nvim config in fennel?
Here's my dotfiles if it helps at all. Written with Aniseed
-
Introducing Kreative, a end-user focused GUI and terminal colorscheme generator
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
hotpot.nvim
-
Configuring Neovim with Fennel
hotpot.nvim
-
A config using fennel .
There are some plugins out there that provide the Lua glue code (e.g. hotpot.nvim), but you will still have to depend on Fennel. I have not tried any of these plugins, so I have no idea how well they work. Neovim is not Emacs, and Lua is a fine language by itself, so that's what I prefer to stick with. And Vim script of course, it may be bad for plugins, but it's actually quite nice for configuration.
-
Swapping to Fennel
Hotpot: this is mostly just a Fennel compiler, but it is quite nice at that
-
[help] How to write nvim plugins with Fennel?
Another method would be to use hotpot: https://github.com/rktjmp/hotpot.nvim. It's much simpler with what it does, doesn't include the macros and helper functions but you might prefer it. Here's an example: https://github.com/rktjmp/paperplanes.nvim
-
LSP for Fennel?
While there isn't an lsp, https://github.com/rktjmp/hotpot.nvim can give you diagnostics and https://github.com/Olical/conjure can give you cmp completions
- Nvim config in fennel?
- Hotter Hotpot: bytecode cache beta branch
-
Best way of using fennel in neovim? Aniseed vs. Hotpot vs. Manually compiling?
I see there are 3 approaches Using aniseed: https://github.com/Olical/aniseed Using hotpot: https://github.com/rktjmp/hotpot.nvim Using plain fennel: https://git.sr.ht/~hauleth/dotfiles/tree/master/item/vim/.config/nvim/init.lua (this is just the one I found, lmk if theres a better version of this)
-
home-manager: How to run a command (remove a directory in ~/.cache/) when a package is upgraded or profile is generated?
Hey y'all, I'm running into this issue. The solution is to remove the directory ~/.cache/nvim/hotpot. I would like to automate this when I upgrade my home environment packages as the issue seems to happen after a home-manager switch --flake --recreate-lock-file operation.
-
Fennel + Neovim and the fallacy of choice
Here's a macro I wrote ages ago for my settings. Some might turn their noses up at doing this, because really you're just making a potentially leaky if not dysfunctional abstraction over nvim's actual API, but, well I did it for fun 🤷♂️.
What are some alternatives?
kat.nvim - NeoVim specifc port of kat.vim, a warm blue theme, written in Fennel with Aniseed
aniseed - Neovim configuration and plugins in Fennel (Lisp compiled to Lua)
tangerine.nvim - 🍊 Sweet Fennel integration for Neovim
lush.nvim - Create Neovim themes with real-time feedback, export anywhere.
nvim-config-bistro - Using fennel to cook up a tasty Lua config ready to be consumed with a "fork"
lazy.nvim - 💤 A modern plugin manager for Neovim
conjure - Interactive evaluation for Neovim (Clojure, Fennel, Janet, Racket, Hy, MIT Scheme, Guile, Python and more!)
kreative - A colorscheme creation tool for Neovim, written in Fennel with Aniseed
cajus-nvim - Basic config to transform your NVIM in a powerful Clojure IDE using fennel, clojure-lsp and conjure.
neovim-dotfiles - luong komorebi neovim lua configurations