Overview

In February 2026, I switched to Fedora Linux and, with some time on my hands after breaking my arm, decided to build a Vim/Neovim setup tailored for coding. My initial focus was on LaTeX, inspired by my lecturer Joe, who often used Vim in workshops for notes and examples.
I began by adapting his Vim configuration, adding a LaTeX compiler and linter, and using Zathura as a PDF viewer after following a Medium article I had found. However, as is common among many users, I wanted something more flexible and personalised.
My goal was to create a lightweight environment with minimal distraction, where I could focus on writing code without the overhead of a full IDE. I had previously moved to VS Code, but I wanted an even simpler workflow.
I initially explored LazyVim-based setups, but I found them to be arguably less efficient than VS Code for my needs, so I started from scratch. I followed several blogs and tutorials, which helped me build a solid understanding of how Neovim and its Lua-based plugins worked together.
Eventually, I combined ideas from these resources, along with another lecturer, Warwick's setup, to guide me through the parts that were less clear. Over time, I refined the configuration to better suit my workflow.
More recently, I have been focusing on further customisation, particularly window layouts and keybindings, to improve efficiency when using Neovim. Keybindings have been a major area of focus, especially the transition from a standard Vim configuration to a more streamlined workflow using the Which-Key plugin.

Blog Links

will put blog links i used to help me here