vim-galore VS neovim

See also Vim galore and my Vim Reference Guide

Vim Galore GitHub page that is basically just a "easily read" page manual to get you up to speed, especially on the 'minimal-vimrc' part of the page that gets you started with the bare minimum, built-in Vim configs that improves your QOL while using it and it takes like... 5 minutes to get it set up.

Hey people, I recently got into Vim and found that it's indeed quite the odyssey. I found mhinz's guide to vim, vim-galore, very helpful. So, I figured that, since there's no version of vim-galore in Spanish, I might as well make one myself. And that's what I did, you can see it in here.

can i read this? https://github.com/mhinz/vim-galore Neovim has the same things right

This is a fine resource. For those who love vim already but want to really understand it this was shared by my team internally: https://github.com/mhinz/vim-galore

Here's a more comprehensive Vim resource: https://github.com/mhinz/vim-galore

vim-galore

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.