A personal experiment to solve a Sudoku in C language. In this first part I am setting up my development environment.

Introduction to a Neovim flake for hosting multiple Neovim editions with inheritance. Instead of having one large configuration for multiple tasks, we can create multiple editions focused on specific tasks. With inheritance, we can reuse configurations from one edition in another. In this article, I will provide a step-by-step guide with beginner-friendly explanations on how to create your own flake.

This is a follow-up post to How to create your own Neovim flake. Thanks to the help of Sam Willis, the mystery of the non-functioning symlinkjoin has been clarified, and a workaround has been found. Sam also assisted me in using flake-utils, which enabled me to successfully build Neovim on Nix-on-Droid.

In this blog post, I will guide you through the process of setting up Neovim as a Nix Flake, allowing you to keep your editor configuration in sync across multiple machines. We'll start by initializing the flake. We'll add Vim script configuration, organizing Vim scripts in separate files and transforming them into config files in the Nix store. I will guide you through adding plugins, Lua scripts, and runtime dependencies to Neovim using Nix. By the end of this blog post, you will be able to configure your own development environment in a more manageable way.