panvimdoc VS neovim

Vim Doc to markdown! IDK who's doing that, but people prefer other way around markdown to vimdoc using https://github.com/kdheepak/panvimdoc

If someone wants similar functionality and they are okay with depending on pandoc instead, I have this repo that make be of relevance: https://github.com/kdheepak/panvimdoc. It also works as a github action, so you can add to a .github/workflows/docs.yml file and forget.

If you're using panvimdoc you can put and comments to exclude parts from the generated vimdoc. See my plugin's README.md

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.