dotfiles_skeleton VS dotfiles

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

Mostly shell hackery and a bunch of more convenient selection, copy and paste functionality plus extensive documentation like the (supposedly) undocumented line selection operator g_ https://github.com/matu3ba/dotfiles/

I am relative satisfied with mine, although I still dont have a working solution for (vendored) project search and custom sources on keypress for completion is also missing (command completion breaks C-l/Tab for file completion): https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

My config consists mostly of documentation, where you can take a look. I have a plugin as git dir I do include for company stuff, because of network shenanigans packer can not handle. https://github.com/matu3ba/dotfiles

You can see my dotfiles here https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

Otherwise, you can check my setup, but I did not setup snippets yet https://github.com/matu3ba/dotfiles

Thats how it works. You could reduce the amount of plugins or document them for quick lookup. I do this extensively in my dotfiles https://github.com/matu3ba/dotfiles/blob/master/.config/nvim/lua/my_packer.lua

For my config I did write a pile of notes of the default keybindings because I found no good and dense note collection on (all) default keybindings and Vim+Neovim hardcodes them with only an annoying way to search exact the exact keybinding. https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

If you want a more minimal example for explanation, you can check my cmake template: https://github.com/matu3ba/dotfiles/blob/master/templates/CMakeList.txt

I find this cleaner to do in lua without vimscript calls, see here.