Yes, I have decided to (try to) switch editor to NeoVim! My initial encounter with Vim occurred exactly 20 years ago during my first month at university. The computers were running Sun Solaris, and we were instructed to choose between Emacs and Vim for a task. Knowing nothing about either, I opted for Vim, only to find myself ensnared in the classic “how-do-I-exit-this-shit” frustration. After that experience, I swore off Vim and its modes entirely. A few years later Sublime Text became my steadfast companion, especially once I discovered the wonders of custom keybindings, around the time Sublime first debuted.
Why Vim and Neovim?
So, why am I now abandoning my trusted editor and delving into the unfamiliar realm of Vim, marked with warning signs akin to “Here be dragons” (though, truth be told, I do have a soft spot for dragons)? The answer lies in my penchant for learning new things and challenging myself. But, I must confess, a significant influence came from my brother, who has been nudging me towards NeoVim for nearly two years. He probably doesn’t realize the depth of trauma Vim once inflicted upon me.
Another key reason is ergonomics. I’m unsure how prevalent this motivation is among others making the switch, but Vim’s modal paradigm enables efficient editing with minimal hand movement and a mouse-free experience. After a summer plagued by RSI, limiting my computer use to mere minutes at a time, I made a concerted effort to reduce reliance on the mouse, even transitioning to a tiling window manager. And in less than a month, I’ll be switching to a 40% keyboard, further motivating me to optimize my workflow. Thus, it’s time to confront Vim once more, as the Swedes say, “take the bull by its horns.”
Many suggested I dip my toes into Vim mode within my familiar editor first, but that’s not my style. I need to fully immerse myself, or I risk succumbing to laziness and sticking to old habits. The steeper the learning curve, the more determined I become. And let me tell you, Vim mode’s curve is practically vertical!
Step 1: Vimtutor
Before venturing into Neovim, I diligently worked through vimtutor, a basic tutorial for Vim-style editing. It proved invaluable and I highly recommend it as the first step for anyone considering the switch to Vim.
Step 2: Choosing a starting configuration
Neovim emerged as the clear favorite among Vim users, leaving me with no doubt about my choice of editor. However, selecting a starting configuration posed a dilemma. While starting from scratch is an option, it’s generally not advisable.
Presently, three popular configurations/frameworks dominate the scene: nvChad, LazyVim, and Kickstart.
- nvChad: Offers a comprehensive, customizable setup with a modular design. It comes preconfigured with the most plugins and features.
- LazyVim: Provides a minimalistic, beginner-friendly approach, emphasizing simplicity and efficiency. It’s often recommended for newcomers or those seeking a streamlined setup.
- Kickstart: Offers a basic configuration with essential features and stability.
I initially installed Neovim with nvChad, but found it overwhelming. The basic tutorial left me feeling lost, a rare occurrence for someone who considers themselves tech-savvy. Feeling defeated, I abandoned the endeavor for the night.
Today, I gave it another shot. I scoured YouTube for tutorials aimed at my level — having completed vimtutor but little else. I shared my frustration with my brother, lamenting the gap between where Vim n00bs like myself begin and where content creators assume we are. They meticulously explain program installation, catering to various Linux distros (as if anyone using Linux wouldn’t already know how to install software on their own system), only to leap into advanced topics like Ex mode and leader keys. Meanwhile, I’m still grappling with the basics of insert mode versus append mode, let alone venturing into visual mode or grasping the concept of modes themselves.
Returning to the topic at hand, nvChad proved too advanced for my current understanding. I struggled to discern what was basic Vim, what was Neovim, and what was specific to nvChad. Thus, I’ve decided to backtrack a step, uninstall nvChad (if that’s even possible), and give LazyVim a try. But that’s a task for my next nocturnal session. It’s now 4 am, and I must bid farewell to this adventure and head to bed.
