dotfiles_skeleton VS neovim

You can also use my dotfiles skeleton to see, if you have different demands. https://github.com/matu3ba/dotfiles_skeleton

Personally it would have helped me to start outright with version tracking and documenting common workflows with dotfiles, for examples starting with my skeleton https://github.com/matu3ba/dotfiles_skeleton

Setup dotfiles to quickly restore broken configs. One simple options is https://github.com/matu3ba/dotfiles_skeleton

My position is that shells should be as simple as possible and any computations and tooling besides simple arithmetic be externalized: https://github.com/matu3ba/dotfiles_skeleton/blob/main/POSIXunsafe

I would recommend for you to start simple and incrementally improve or change plugins you dont like with dotfiles. My relative minimal dotfiles missing JavaScript lsp, debugger etc](https://github.com/matu3ba/dotfiles).

I dont believe there is "a best way", since requirements for dotfiles differ. For simple replications my [dotfile skeleton](https://github.com/matu3ba/dotfiles_skeleton) using fd with ignorefiles worked fine for me.

For easy managing your dotfiles on Linux (did not test Mac) you can usw my dotfiles skeleton.

Guess then you need to minimise the config to track down the issue. Do you use dotfiles? You could use my skeleton to easily branch and reset etc.

Create dotfiles or something different for versioning You can use my https://github.com/matu3ba/dotfiles_skeleton

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.