iofq/nvim.nix
1
0
Fork 0
mirror of https://github.com/iofq/nvim.nix.git synced 2026-01-23 08:55:16 -06:00
Code Issues Projects Releases 1 Packages Wiki Activity Actions
Neovim config that runs on nixOS but doesn't sacrifice portability
65 commits 4 branches 1 tag 710 KiB
Find a file
iofq c3854e2b93
Merge pull request #9 from iofq/update_flake_lock_action 
chore: update flake.lock
2024-04-01 19:07:51 +00:00
.github/workflows test workflow 2024-01-28 20:01:43 -06:00
config rice from work 2024-02-16 19:08:46 -06:00
.gitignore fix rose-pine italics 2024-01-29 01:21:56 -06:00
filewatch.py rice from work 2024-02-16 19:08:46 -06:00
flake.lock chore: update flake.lock 2024-04-01 10:14:12 +00:00
flake.nix rice from work 2024-02-16 19:08:46 -06:00
plugins.nix rice from work 2024-02-16 19:08:46 -06:00
README.md Remove Dockerfile, add README 2024-01-28 20:36:53 -06:00

README.md

nvim.nix - personal Neovim config that runs on nixOS but doesn't sacrifice portability

Usage

nix run "github:iofq/nvim.nix" #full

Or, grab an AppImage from the Releases page.

What the hell?

This is a flake to build a Neovim package that includes my custom Lua config and dependencies. It then is bundled via CI into an AppImage.

Why the hell though?

I use these AppImages because I develop in a number of airgapped environments that make traditional dotfile management a nightmare. Downloading a single AppImage and copying it around is a more suckless way of managing this.